Data as of Nov 12, 2026

80.254.89.0/24

13 residential-proxy exits · 30 days

GO p.l.c.

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

Residential-proxy exits

Proxy exits
13
5.1% of its addresses · 30 days
Providers
48
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.9K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonode
  • GhostConnect
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
80.254.80.0/20
since Nov 2010
AS15735Residential153GO p.l.c.

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
80.254.80.0/204,096MT-GO-20051206GO p.l.c. (ORG-DL6-RIPE) · MTALLOCATED PADec 6, 2005abuse@go.com.mt
└ 80.254.88.0/212,048MT-GO-PLUS-RETAIL-DSLGo P.L.C.ASSIGNED PAFeb 22, 2017abuse@go.com.mt
via MT-GO-20051206

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
Nov 2007
Current origin since
Apr 2026 · 7 mo
Origin networks
2
Last change of origin
Apr 2019
Recorded history

History

Handoffs
1