Data as of Nov 15, 2026

145.255.56.0/21

15 residential-proxy exits · 30 days

Glentevejs Antennelaug

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

Residential-proxy exits

Proxy exits
15
0.73% of its addresses · 30 days
Spread
6 of 8
/24s with at least one exit
Providers
44
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

540 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • Ake.net
  • BlurPath
  • BuyingProxy
  • Byteful
  • CatProxies
  • DataImpulse
  • Datarama
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • IPMUSK
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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
145.255.56.0/212,048DK-GLENTEVEJS-20111122Glentevejs Antennelaug (ORG-GA174-RIPE) · DKALLOCATED PANov 22, 2011contact@glentenodense.dk
└ 145.255.56.0/23512GALCATV serviceASSIGNED PANov 22, 2011contact@glentenodense.dk
via DK-GLENTEVEJS-20111122
└ 145.255.58.0/24256GAL-ODENSECATV serviceASSIGNED PAApr 30, 2014contact@glentenodense.dk
via DK-GLENTEVEJS-20111122
└ 145.255.59.0/24256GAL-ODENSECATV serviceASSIGNED PAApr 30, 2014contact@glentenodense.dk
via DK-GLENTEVEJS-20111122
└ 145.255.60.0/24256GAL-ODENSECATV serviceASSIGNED PAApr 30, 2014contact@glentenodense.dk
via DK-GLENTEVEJS-20111122
└ 145.255.61.0/24256GAL-ODENSECATV serviceASSIGNED PAApr 30, 2014contact@glentenodense.dk
via DK-GLENTEVEJS-20111122

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 this prefix

Summary

Routing history

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

History

Handoffs
1