LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

217.11.30.0/24

1 residential-proxy exit · 30 days

Afranet

Announcement
this exact prefix
RPKI valid
Announced by
AS25184
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
4
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

89 observations

Proxy providers listing exits

  • DataImpulse
  • EVOPROXY
  • Proxmint
  • Proxy4U

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
217.11.16.0/20
since May 2026
AS25184Hosting5Afranet

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
217.11.16.0/204,096IR-AFRANET-20021121Afranet (ORG-AA32-RIPE) · IRALLOCATED PANov 21, 2002abuse@afranet.com
└ 217.11.30.8/304Mohammad-YousefiunknownASSIGNED PASep 6, 2025abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.12/304tahghighat-mavad-madani-iranunknownASSIGNED PAJun 30, 2021abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.32/304Koopa-GostarunknownASSIGNED PADec 9, 2025abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.36/304Arses-Partak-ParsunknownASSIGNED PAFeb 15, 2026abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.40/298electronik-afratabunknownASSIGNED PAFeb 21, 2021abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.64/2732Azad-Uni-HashtgerdunknownASSIGNED PAAug 16, 2021abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.100/304Amadeh-LazizunknownASSIGNED PAJul 31, 2022abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.104/304hana-zhenunknownASSIGNED PAAug 27, 2022abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.112/304Tamin-Tablo-EshtehardunknownASSIGNED PAMar 9, 2022abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.116/304Ava-Katan-GheshmunknownASSIGNED PAMar 11, 2024abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.120/304Jahan-ShimiunknownASSIGNED PASep 30, 2023abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.128/304Sanaye-Bartar-AtiunknownASSIGNED PANov 26, 2022abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.136/304Rah-TebunknownASSIGNED PAJul 8, 2025abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.160/304Sanaye-Bartar-AtiunknownASSIGNED PAApr 20, 2024abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.164/304Tolidi-Va-Bazargani-JeyunknownASSIGNED PAOct 26, 2026abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.180/304Amade-LazizunknownASSIGNED PAAug 19, 2025abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.184/304ghaleb-sanati-iranunknownASSIGNED PAOct 8, 2025abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.208/298simorgh-houshmand-sharifunknownASSIGNED PAMar 14, 2022abuse@afranet.com
via IR-AFRANET-20021121
└ 217.11.30.248/298TCTUplink TCTASSIGNED PAJul 22, 2009abuse@afranet.com
via IR-AFRANET-20021121

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Feb 2018 · 8.7 yr
Origin networks
2
Last change of origin
Nov 2005
Recorded history

History

Handoffs
1