Data as of Nov 10, 2026

79.136.72.0/22

2 residential-proxy exits · 30 days

Bahnhof AB

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

Residential-proxy exits

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

Exits seen per day

138 observations

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • Shifter
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.136.0.0/17
since Oct 2007
AS8473Residential187
14 always on
Bahnhof AB

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
79.136.0.0/1732,768SE-BAHNHOF-20070927Bahnhof AB (ORG-BIA1-RIPE) · SEALLOCATED PASep 27, 2007abuse@bahnhof.net
└ 79.136.72.0/221,024BAHNHOF-DEunknownASSIGNED PAOct 3, 2014abuse@bahnhof.net
via SE-BAHNHOF-20070927

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1