Data as of Nov 11, 2026

178.249.4.0/22

4 residential-proxy exits · 30 days

PfalzConnect GmbH

Announcement
No RPKI
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
4
0.39% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

229 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.249.7.0/2403
178.249.4.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GonzoProxy
  • Infatica
  • KindProxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • Novada
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
178.249.5.0/24
since Jul 2023
AS197063ResidentialPfalzConnect GmbH
178.249.6.0/24
since Jul 2023
AS197063ResidentialPfalzConnect GmbH

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
178.249.0.0/212,048DE-PFALZCONNECT-20100514PfalzConnect GmbH (ORG-PG47-RIPE) · DEALLOCATED PAMay 14, 2010registry@pfalzconnect.de
└ 178.249.4.0/221,024PFALZCONNECT-NETPfalzConnect GmbHASSIGNED PAMay 30, 2010registry@pfalzconnect.de
via DE-PFALZCONNECT-20100514

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 178.249.0.0/21

178.249.0.0/21

Routing history

Pattern
Stable
First seen
Oct 2011
Current origin since
Oct 2011 · 15 yr
Origin networks
2
Last change of origin
Dec 2016
Recorded history

History

Handoffs
1