BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2600:1902::/31
Announced exactly
- 2600:1902::/31AS15169Google LLCRPKI Valid2600:1902::
- Registry
- ARIN · United States · May 28, 2014
- Delegated block
- 2600:1900:: – 2600:190f:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2600:1902::/44AS19527Google LLCRPKI Valid2600:1902::
- 2600:1902:10::/44AS19527Google LLCRPKI Valid2600:1902:10::
- 2600:1902:20::/44AS15169Google LLCRPKI Valid2600:1902:20::
- 2600:1902:30::/44AS15169Google LLCRPKI Valid2600:1902:30::
- 2600:1902:40::/44AS15169Google LLCRPKI Valid2600:1902:40::
- 2600:1902:50::/44AS15169Google LLCRPKI Valid2600:1902:50::
- 2600:1902:60::/44AS15169Google LLCRPKI Valid2600:1902:60::
- 2600:1902:70::/44AS19527Google LLCRPKI Valid2600:1902:70::
- 2600:1902:80::/44AS19527Google LLCRPKI Valid2600:1902:80::
- 2600:1902:90::/44AS15169Google LLCRPKI Valid2600:1902:90::
- 2600:1902:a0::/44AS15169Google LLCRPKI Valid2600:1902:a0::
- 2600:1902:b0::/44AS19527Google LLCRPKI Valid2600:1902:b0::
- 2600:1902:c0::/44AS19527Google LLCRPKI Valid2600:1902:c0::
- 2600:1902:d0::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:d0::
- 2600:1902:e0::/44AS19527Google LLCRPKI Valid2600:1902:e0::
- 2600:1902:f0::/44AS19527Google LLCRPKI Valid2600:1902:f0::
- 2600:1902:100::/44AS19527Google LLCRPKI Valid2600:1902:100::
- 2600:1902:110::/44AS15169Google LLCRPKI Valid2600:1902:110::
- 2600:1902:120::/44AS15169Google LLCRPKI Valid2600:1902:120::
- 2600:1902:130::/44AS15169Google LLCRPKI Valid2600:1902:130::
- 2600:1902:140::/44AS19527Google LLCRPKI Valid2600:1902:140::
- 2600:1902:150::/44AS15169Google LLCRPKI Valid2600:1902:150::
- 2600:1902:160::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:160::
- 2600:1902:170::/44AS19527Google LLCRPKI Valid2600:1902:170::
- 2600:1902:180::/44AS19527Google LLCRPKI Valid2600:1902:180::
- 2600:1902:190::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:190::
- 2600:1902:1a0::/44AS19527Google LLCRPKI Valid2600:1902:1a0::
- 2600:1902:1b0::/44AS19527Google LLCRPKI Valid2600:1902:1b0::
- 2600:1902:1c0::/44AS19527Google LLCRPKI Valid2600:1902:1c0::
- 2600:1902:1d0::/44AS19527Google LLCRPKI Valid2600:1902:1d0::
- 2600:1902:1e0::/44AS19527Google LLCRPKI Valid2600:1902:1e0::
- 2600:1902:1f0::/44AS19527Google LLCRPKI Valid2600:1902:1f0::
- 2600:1902:200::/44AS15169Google LLCRPKI Valid2600:1902:200::
- 2600:1902:210::/44AS15169Google LLCRPKI Valid2600:1902:210::
- 2600:1902:220::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:220::
- 2600:1902:230::/44AS15169Google LLCRPKI Valid2600:1902:230::
- 2600:1902:250::/44AS15169Google LLCRPKI Valid2600:1902:250::
- 2600:1902:260::/44AS15169Google LLCRPKI Valid2600:1902:260::
- 2600:1902:270::/44AS19527Google LLCRPKI Valid2600:1902:270::
- 2600:1902:280::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:280::
- 2600:1902:290::/44AS15169Google LLCRPKI Valid2600:1902:290::
- 2600:1902:2a0::/44AS15169Google LLCRPKI Valid2600:1902:2a0::
- 2600:1902:2b0::/44AS15169Google LLCRPKI Valid2600:1902:2b0::
- 2600:1902:2c0::/44AS15169Google LLCRPKI Valid2600:1902:2c0::
- 2600:1902:2d0::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:2d0::
- 2600:1902:2e0::/44AS19527Google LLCRPKI Valid2600:1902:2e0::
- 2600:1902:2f0::/44AS15169Google LLCRPKI Valid2600:1902:2f0::
- 2600:1902:300::/44AS15169Google LLCRPKI Valid2600:1902:300::
- 2600:1902:330::/44AS19527Google LLCRPKI Valid2600:1902:330::
- 2600:1902:350::/44AS15169Google LLCRPKI Valid2600:1902:350::
- 2600:1902:3a0::/44AS19527Google LLCRPKI Valid2600:1902:3a0::
- 2600:1902:3d0::/44AS15169Google LLCRPKI Valid2600:1902:3d0::
- 2600:1902:400::/44AS15169Google LLCRPKI Valid2600:1902:400::
- 2600:1902:410::/44AS15169Google LLCRPKI Valid2600:1902:410::
- 2600:1902:420::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:420::
- 2600:1902:490::/44AS19527Google LLCRPKI Valid2600:1902:490::
- 2600:1902:4a0::/44AS19527Google LLCRPKI Valid2600:1902:4a0::
- 2600:1902:4e0::/44AS19527Google LLCRPKI Valid2600:1902:4e0::
- 2600:1902:4f0::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:4f0::
- 2600:1902:500::/44AS15169Google LLCRPKI Valid2600:1902:500::
- 2600:1902:520::/44AS15169Google LLCRPKI Valid2600:1902:520::
- 2600:1902:530::/44AS15169Google LLCRPKI Valid2600:1902:530::
- 2600:1902:550::/44AS43515Google Ireland LimitedRPKI Valid2600:1902:550::
- 2600:1902:560::/44AS15169Google LLCRPKI Valid2600:1902:560::
- 2600:1902:590::/44AS15169Google LLCRPKI Valid2600:1902:590::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.