BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
85.189.0.0/16
Announced exactly
- 85.189.0.0/16AS3257GTT Communications Inc.RPKI Not found85.189.0.0
- Registry
- RIPE NCC · United Kingdom · Dec 7, 2004
- Delegated block
- 85.189.0.0 – 85.189.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 85.189.3.0/24AS401560OneCable Network LLCRPKI Valid85.189.3.0
- 85.189.5.0/24AS21859Zenlayer IncRPKI Valid85.189.5.0
- 85.189.9.0/24AS216472High Speed For Internet Services L.L.CRPKI Valid85.189.9.0
- 85.189.10.0/24AS9457DREAMLINE CO.RPKI Valid85.189.10.0
- 85.189.11.0/24AS21859Zenlayer IncRPKI Valid85.189.11.0
- 85.189.13.0/24AS216472High Speed For Internet Services L.L.CRPKI Valid85.189.13.0
- 85.189.14.0/24AS6205HizliNet Teknoloji A.S.RPKI Valid85.189.14.0
- 85.189.16.0/24AS44803Webdock.io ApSRPKI Valid85.189.16.0
- 85.189.17.0/24AS30058FDCservers.netRPKI Valid85.189.17.0
- 85.189.28.0/24AS212238Datacamp LimitedRPKI Valid85.189.28.0
- 85.189.29.0/24AS36236NetActuate, IncRPKI Valid85.189.29.0
- 85.189.32.0/22AS54004Cablevision Lightpath LLCRPKI Valid85.189.32.0
- 85.189.36.0/24AS13537Mega Colocation, Inc.RPKI Valid85.189.36.0
- 85.189.37.0/24AS209181Zenex 5ive LimitedRPKI Valid85.189.37.0
- 85.189.40.0/23AS139659LUCIDACLOUD LIMITEDRPKI Valid85.189.40.0
- 85.189.40.0/24AS139659LUCIDACLOUD LIMITEDRPKI Valid85.189.40.0
- 85.189.41.0/24AS139659LUCIDACLOUD LIMITEDRPKI Valid85.189.41.0
- 85.189.56.0/24AS3257GTT Communications Inc.RPKI Not found85.189.56.0
- 85.189.60.0/24AS154711ANYLINK NET SDN. BHD.RPKI Valid85.189.60.0
- 85.189.72.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.72.0
- 85.189.74.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.74.0
- 85.189.76.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.76.0
- 85.189.78.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.78.0
- 85.189.82.0/24AS154711ANYLINK NET SDN. BHD.RPKI Valid85.189.82.0
- 85.189.98.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.98.0
- 85.189.99.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.99.0
- 85.189.100.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.100.0
- 85.189.101.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.101.0
- 85.189.104.0/22AS3257GTT Communications Inc.RPKI Not found85.189.104.0
- 85.189.110.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.110.0
- 85.189.111.0/24AS138915Kaopu Cloud HK LimitedRPKI Valid85.189.111.0
- 85.189.112.0/22AS3257GTT Communications Inc.RPKI Not found85.189.112.0
- 85.189.120.0/22AS3257GTT Communications Inc.RPKI Not found85.189.120.0
- 85.189.132.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.132.0
- 85.189.153.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.153.0
- 85.189.154.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.154.0
- 85.189.156.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.156.0
- 85.189.159.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.159.0
- 85.189.160.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.160.0
- 85.189.162.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.162.0
- 85.189.164.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.164.0
- 85.189.167.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.167.0
- 85.189.174.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.174.0
- 85.189.178.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.178.0
- 85.189.181.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.181.0
- 85.189.183.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.183.0
- 85.189.189.0/24AS2856British Telecommunications LimitedRPKI Valid85.189.189.0
- 85.189.190.0/23AS2856British Telecommunications LimitedRPKI Valid85.189.190.0
- 85.189.193.0/24AS3320Deutsche Telekom AGRPKI Valid85.189.193.0
- 85.189.194.0/24AS3320Deutsche Telekom AGRPKI Valid85.189.194.0
- 85.189.196.0/24AS20115Charter Communications LLCRPKI Valid85.189.196.0
- 85.189.198.0/23AS20115Charter Communications LLCRPKI Valid85.189.198.0
- 85.189.201.0/24AS20115Charter Communications LLCRPKI Valid85.189.201.0
- 85.189.202.0/24AS20115Charter Communications LLCRPKI Valid85.189.202.0
- 85.189.204.0/22AS8447A1 Telekom Austria AGRPKI Valid85.189.204.0
- 85.189.208.0/23AS20115Charter Communications LLCRPKI Valid85.189.208.0
- 85.189.210.0/24AS20115Charter Communications LLCRPKI Valid85.189.210.0
- 85.189.214.0/24AS20115Charter Communications LLCRPKI Valid85.189.214.0
- 85.189.216.0/22AS10753Level 3 Parent, LLCRPKI Valid85.189.216.0
- 85.189.220.0/24AS20115Charter Communications LLCRPKI Valid85.189.220.0
- 85.189.222.0/23AS20115Charter Communications LLCRPKI Valid85.189.222.0
- 85.189.229.0/24AS20115Charter Communications LLCRPKI Valid85.189.229.0
- 85.189.230.0/23AS20115Charter Communications LLCRPKI Valid85.189.230.0
- 85.189.232.0/24AS20115Charter Communications LLCRPKI Valid85.189.232.0
- 85.189.234.0/24AS20115Charter Communications LLCRPKI Valid85.189.234.0
- 85.189.236.0/23AS20115Charter Communications LLCRPKI Valid85.189.236.0
- 85.189.239.0/24AS20115Charter Communications LLCRPKI Valid85.189.239.0
- 85.189.240.0/23AS20115Charter Communications LLCRPKI Valid85.189.240.0
- 85.189.243.0/24AS20115Charter Communications LLCRPKI Valid85.189.243.0
- 85.189.245.0/24AS20115Charter Communications LLCRPKI Valid85.189.245.0
- 85.189.248.0/23AS20115Charter Communications LLCRPKI Valid85.189.248.0
- 85.189.252.0/24AS20115Charter Communications LLCRPKI Valid85.189.252.0
- 85.189.255.0/24AS20115Charter Communications LLCRPKI Valid85.189.255.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.