BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
212.180.0.0/17
Announced exactly
- 212.180.0.0/17AS3257GTT Communications Inc.RPKI Not found212.180.0.0
- Registry
- RIPE NCC · France · Jan 12, 1999
- Delegated block
- 212.180.0.0 – 212.180.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 212.180.3.0/24AS5511Orange S.A.RPKI Valid212.180.3.0
- 212.180.4.0/24AS5511Orange S.A.RPKI Valid212.180.4.0
- 212.180.5.0/24AS3257GTT Communications Inc.RPKI Not found212.180.5.0
- 212.180.6.0/23AS59711HZ Hosting LtdRPKI Valid212.180.6.0
- 212.180.9.0/24AS30058FDCservers.netRPKI Valid212.180.9.0
- 212.180.10.0/24AS59711HZ Hosting LtdRPKI Valid212.180.10.0
- 212.180.12.0/22AS5511Orange S.A.RPKI Valid212.180.12.0
- 212.180.16.0/22AS59711HZ Hosting LtdRPKI Valid212.180.16.0
- 212.180.20.0/23AS212238Datacamp LimitedRPKI Valid212.180.20.0
- 212.180.22.0/24AS5511Orange S.A.RPKI Valid212.180.22.0
- 212.180.24.0/23AS3320Deutsche Telekom AGRPKI Valid212.180.24.0
- 212.180.26.0/24AS5511Orange S.A.RPKI Valid212.180.26.0
- 212.180.29.0/24AS5511Orange S.A.RPKI Valid212.180.29.0
- 212.180.30.0/23AS212238Datacamp LimitedRPKI Valid212.180.30.0
- 212.180.32.0/22AS59711HZ Hosting LtdRPKI Valid212.180.32.0
- 212.180.37.0/24AS5511Orange S.A.RPKI Valid212.180.37.0
- 212.180.38.0/23AS212238Datacamp LimitedRPKI Valid212.180.38.0
- 212.180.40.0/24AS212238Datacamp LimitedRPKI Valid212.180.40.0
- 212.180.42.0/24AS3320Deutsche Telekom AGRPKI Valid212.180.42.0
- 212.180.44.0/24AS5511Orange S.A.RPKI Valid212.180.44.0
- 212.180.46.0/23AS5511Orange S.A.RPKI Valid212.180.46.0
- 212.180.50.0/24AS212238Datacamp LimitedRPKI Valid212.180.50.0
- 212.180.52.0/24AS59711HZ Hosting LtdRPKI Valid212.180.52.0
- 212.180.54.0/23AS212238Datacamp LimitedRPKI Valid212.180.54.0
- 212.180.60.0/22AS59711HZ Hosting LtdRPKI Valid212.180.60.0
- 212.180.64.0/20AS5511Orange S.A.RPKI Valid212.180.64.0
- 212.180.80.0/23AS212238Datacamp LimitedRPKI Valid212.180.80.0
- 212.180.83.0/24AS3257GTT Communications Inc.RPKI Not found212.180.83.0
- 212.180.84.0/24AS5511Orange S.A.RPKI Valid212.180.84.0
- 212.180.86.0/23AS30058FDCservers.netRPKI Valid212.180.86.0
- 212.180.88.0/22AS1257Tele2 Sverige ABRPKI Valid212.180.88.0
- 212.180.92.0/23AS212238Datacamp LimitedRPKI Valid212.180.92.0
- 212.180.94.0/24AS5511Orange S.A.RPKI Valid212.180.94.0
- 212.180.96.0/22AS5511Orange S.A.RPKI Valid212.180.96.0
- 212.180.101.0/24AS5511Orange S.A.RPKI Valid212.180.101.0
- 212.180.104.0/23AS59711HZ Hosting LtdRPKI Valid212.180.104.0
- 212.180.111.0/24AS5065Bunny CommunicationsRPKI Valid212.180.111.0
- 212.180.112.0/24AS5065Bunny CommunicationsRPKI Valid212.180.112.0
- 212.180.113.0/24AS5065Bunny CommunicationsRPKI Valid212.180.113.0
- 212.180.114.0/24AS5065Bunny CommunicationsRPKI Valid212.180.114.0
- 212.180.117.0/24AS5065Bunny CommunicationsRPKI Valid212.180.117.0
- 212.180.118.0/24AS5065Bunny CommunicationsRPKI Valid212.180.118.0
- 212.180.119.0/24AS5065Bunny CommunicationsRPKI Valid212.180.119.0
- 212.180.120.0/24AS210538KEYUBU Internet ve Bilisim Tic. Ltd. Sti.RPKI Valid212.180.120.0
- 212.180.121.0/24AS212238Datacamp LimitedRPKI Valid212.180.121.0
- 212.180.122.0/23AS206766Travchis LLCRPKI Valid212.180.122.0
- 212.180.125.0/24AS5065Bunny CommunicationsRPKI Valid212.180.125.0
- 212.180.127.0/24AS13537Mega Colocation, Inc.RPKI Valid212.180.127.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.