BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
84.200.0.0/16
Announced exactly
- 84.200.0.0/16AS44066DE-FIRSTCOLO firstcolo.netRPKI Valid84.200.0.0
- Registry
- RIPE NCC · Germany · Apr 28, 2004
- Delegated block
- 84.200.0.0 – 84.200.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 84.200.16.0/24AS214036ULTAHOST-ASRPKI Valid84.200.16.0
- 84.200.17.0/24AS214036ULTAHOST-ASRPKI Valid84.200.17.0
- 84.200.24.0/24AS214036ULTAHOST-ASRPKI Valid84.200.24.0
- 84.200.27.0/24AS214036ULTAHOST-ASRPKI Valid84.200.27.0
- 84.200.39.0/24AS44066DE-FIRSTCOLO firstcolo.netRPKI Valid84.200.39.0
- 84.200.73.0/24AS214036ULTAHOST-ASRPKI Valid84.200.73.0
- 84.200.76.0/24AS44066DE-FIRSTCOLO firstcolo.netRPKI Valid84.200.76.0
- 84.200.77.0/24AS214036ULTAHOST-ASRPKI Valid84.200.77.0
- 84.200.80.0/24AS214036ULTAHOST-ASRPKI Valid84.200.80.0
- 84.200.81.0/24AS214036ULTAHOST-ASRPKI Valid84.200.81.0
- 84.200.87.0/24AS214036ULTAHOST-ASRPKI Valid84.200.87.0
- 84.200.89.0/24AS214036ULTAHOST-ASRPKI Valid84.200.89.0
- 84.200.91.0/24AS214036ULTAHOST-ASRPKI Valid84.200.91.0
- 84.200.125.0/24AS214036ULTAHOST-ASRPKI Valid84.200.125.0
- 84.200.128.0/24AS214036ULTAHOST-ASRPKI Valid84.200.128.0
- 84.200.145.0/24AS44066DE-FIRSTCOLO firstcolo.netRPKI Valid84.200.145.0
- 84.200.154.0/24AS214036ULTAHOST-ASRPKI Valid84.200.154.0
- 84.200.192.0/24AS214036ULTAHOST-ASRPKI Valid84.200.192.0
- 84.200.193.0/24AS214036ULTAHOST-ASRPKI Valid84.200.193.0
- 84.200.205.0/24AS214036ULTAHOST-ASRPKI Valid84.200.205.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.