BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
213.210.0.0/18
Announced exactly
- 213.210.0.0/18AS8851EDGE ta GCI ComRPKI Valid213.210.0.0
- Registry
- RIPE NCC · United Kingdom · Sep 20, 1999
- Delegated block
- 213.210.0.0 – 213.210.31.255
Covering routes
No less-specific route covers it.
More-specific routes
- 213.210.0.0/19AS8851EDGE ta GCI ComRPKI Valid213.210.0.0
- 213.210.4.0/23AS212336BYTEVIRTLLCRPKI Valid213.210.4.0
- 213.210.11.0/24AS154408URLSTART-AS-AP URLSTARTRPKI Valid213.210.11.0
- 213.210.13.0/24AS47583AS-HOSTINGERRPKI Valid213.210.13.0
- 213.210.16.0/24AS16509Amazon.com, Inc.RPKI Valid213.210.16.0
- 213.210.18.0/24AS16509Amazon.com, Inc.RPKI Valid213.210.18.0
- 213.210.20.0/24AS47583AS-HOSTINGERRPKI Valid213.210.20.0
- 213.210.21.0/24AS47583AS-HOSTINGERRPKI Valid213.210.21.0
- 213.210.24.0/24AS22160INIsmart Technology Ltd.RPKI Valid213.210.24.0
- 213.210.28.0/24AS49981WORLDSTREAMRPKI Valid213.210.28.0
- 213.210.32.0/20AS8851EDGE ta GCI ComRPKI Valid213.210.32.0
- 213.210.33.0/24AS16509Amazon.com, Inc.RPKI Valid213.210.33.0
- 213.210.34.0/24AS213515HONEYBANK-STUDIOSRPKI Valid213.210.34.0
- 213.210.35.0/24AS42927S-NET-ASRPKI Valid213.210.35.0
- 213.210.36.0/24AS47583AS-HOSTINGERRPKI Valid213.210.36.0
- 213.210.37.0/24AS47583AS-HOSTINGERRPKI Valid213.210.37.0
- 213.210.39.0/24AS214285ABOVEBARRPKI Valid213.210.39.0
- 213.210.40.0/24AS9009M247RPKI Valid213.210.40.0
- 213.210.41.0/24AS212238CDNEXTRPKI Valid213.210.41.0
- 213.210.42.0/24AS135402US-FXCAPITALRPKI Valid213.210.42.0
- 213.210.48.0/22AS8851EDGE ta GCI ComRPKI Valid213.210.48.0
- 213.210.48.0/23AS20473The Constant Company, LLCRPKI Valid213.210.48.0
- 213.210.51.0/24AS16509Amazon.com, Inc.RPKI Valid213.210.51.0
- 213.210.52.0/24AS137235AS137235RPKI Valid213.210.52.0
- 213.210.53.0/24AS13537Mega Colocation, Inc.RPKI Valid213.210.53.0
- 213.210.56.0/21AS8851EDGE ta GCI ComRPKI Valid213.210.56.0
- 213.210.57.0/24AS47583AS-HOSTINGERRPKI Valid213.210.57.0
- 213.210.58.0/24AS204044ONLYSERVERS Dedicated Server Hosting ProviderRPKI Valid213.210.58.0
- 213.210.59.0/24AS212416PROXIMITYRPKI Valid213.210.59.0
- 213.210.62.0/24AS61317ASDETUK www.heficed.comRPKI Valid213.210.62.0
- 213.210.63.0/24AS400866Harmony Networks, Inc.RPKI Valid213.210.63.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.