BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2606:5000::/32
Announced exactly
- 2606:5000::/32AS209CenturyLink Communications, LLCRPKI Not found2606:5000::
- Registry
- ARIN · United States · Mar 30, 2010
- Delegated block
- 2606:5000:: – 2606:5000:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2606:5000::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000::
- 2606:5000:200::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:200::
- 2606:5000:400::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:400::
- 2606:5000:600::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:600::
- 2606:5000:800::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:800::
- 2606:5000:a00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:a00::
- 2606:5000:e00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:e00::
- 2606:5000:1000::/39AS19901BrightspeedRPKI Not found2606:5000:1000::
- 2606:5000:1200::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:1200::
- 2606:5000:1400::/39AS19901BrightspeedRPKI Not found2606:5000:1400::
- 2606:5000:1600::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:1600::
- 2606:5000:1800::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:1800::
- 2606:5000:1a00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:1a00::
- 2606:5000:1c00::/39AS19901BrightspeedRPKI Not found2606:5000:1c00::
- 2606:5000:1e00::/39AS19901BrightspeedRPKI Not found2606:5000:1e00::
- 2606:5000:2000::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:2000::
- 2606:5000:2400::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:2400::
- 2606:5000:2600::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:2600::
- 2606:5000:2800::/39AS19901BrightspeedRPKI Not found2606:5000:2800::
- 2606:5000:2c00::/39AS19901BrightspeedRPKI Not found2606:5000:2c00::
- 2606:5000:2e00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:2e00::
- 2606:5000:3000::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:3000::
- 2606:5000:3400::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:3400::
- 2606:5000:3600::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:3600::
- 2606:5000:3800::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:3800::
- 2606:5000:3a00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:3a00::
- 2606:5000:3c00::/39AS19901BrightspeedRPKI Not found2606:5000:3c00::
- 2606:5000:3e00::/39AS19901BrightspeedRPKI Not found2606:5000:3e00::
- 2606:5000:4000::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:4000::
- 2606:5000:4200::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:4200::
- 2606:5000:4400::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:4400::
- 2606:5000:4800::/39AS19901BrightspeedRPKI Not found2606:5000:4800::
- 2606:5000:4a00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:4a00::
- 2606:5000:4c00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:4c00::
- 2606:5000:4e00::/39AS19901BrightspeedRPKI Not found2606:5000:4e00::
- 2606:5000:5000::/39AS19901BrightspeedRPKI Not found2606:5000:5000::
- 2606:5000:5200::/39AS19901BrightspeedRPKI Not found2606:5000:5200::
- 2606:5000:5400::/39AS19901BrightspeedRPKI Not found2606:5000:5400::
- 2606:5000:5600::/39AS19901BrightspeedRPKI Not found2606:5000:5600::
- 2606:5000:5800::/39AS19901BrightspeedRPKI Not found2606:5000:5800::
- 2606:5000:5a00::/39AS209CenturyLink Communications, LLCRPKI Not found2606:5000:5a00::
- 2606:5000:5c00::/39AS19901BrightspeedRPKI Not found2606:5000:5c00::
- 2606:5000:5e00::/39AS19901BrightspeedRPKI Not found2606:5000:5e00::
- 2606:5000:6000::/39AS19901BrightspeedRPKI Not found2606:5000:6000::
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.