Data as of Nov 11, 2026

213.246.2.0/24

94 residential-proxy exits · 30 days

Public Telecommunication Corporation

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
94
37% of its addresses · 30 days
Providers
47
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

257 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • KindProxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • ResiProxies
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TalorData
  • ThunderProxy
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
213.246.0.0/198,192YE-PTC-20081120Public Telecommunication Corporation (ORG-PTC4-RIPE) · YEALLOCATED PADec 3, 2018abuse@yemen.net.ye
└ 213.246.0.0/212,048YEMEN-NET-ADSL-POOL33_1unknownASSIGNED PADec 3, 2018abuse@yemen.net.ye
via YE-PTC-20081120

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

Routing timeline

Who has announced 213.246.0.0/21

213.246.0.0/21

Routing history

Pattern
Stable
First seen
Nov 2008
Current origin since
Dec 2018 · 7.9 yr
Origin networks
2
Last change of origin
Dec 2018
Recorded history

History

Handoffs
1