BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a04:52c0::/32
Announced exactly
- 2a04:52c0::/32AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0::
- Registry
- RIPE NCC · Netherlands · Jul 24, 2013
- Delegated block
- 2a04:52c0:: – 2a04:52c7:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a04:52c0:1::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:1::
- 2a04:52c0:101::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:101::
- 2a04:52c0:102::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:102::
- 2a04:52c0:103::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:103::
- 2a04:52c0:104::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:104::
- 2a04:52c0:105::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:105::
- 2a04:52c0:106::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:106::
- 2a04:52c0:107::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:107::
- 2a04:52c0:108::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:108::
- 2a04:52c0:109::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:109::
- 2a04:52c0:110::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:110::
- 2a04:52c0:111::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:111::
- 2a04:52c0:112::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:112::
- 2a04:52c0:113::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:113::
- 2a04:52c0:114::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:114::
- 2a04:52c0:115::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:115::
- 2a04:52c0:116::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:116::
- 2a04:52c0:117::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:117::
- 2a04:52c0:118::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:118::
- 2a04:52c0:119::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:119::
- 2a04:52c0:120::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:120::
- 2a04:52c0:121::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:121::
- 2a04:52c0:122::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:122::
- 2a04:52c0:123::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:123::
- 2a04:52c0:124::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:124::
- 2a04:52c0:125::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:125::
- 2a04:52c0:126::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:126::
- 2a04:52c0:127::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:127::
- 2a04:52c0:128::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:128::
- 2a04:52c0:129::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:129::
- 2a04:52c0:130::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:130::
- 2a04:52c0:131::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:131::
- 2a04:52c0:132::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:132::
- 2a04:52c0:133::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:133::
- 2a04:52c0:134::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:134::
- 2a04:52c0:135::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:135::
- 2a04:52c0:136::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:136::
- 2a04:52c0:138::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:138::
- 2a04:52c0:139::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:139::
- 2a04:52c0:140::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:140::
- 2a04:52c0:1000::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:1000::
- 2a04:52c0:1674::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:1674::
- 2a04:52c0:1a00::/48AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:1a00::
- 2a04:52c0:2000::/36AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:2000::
- 2a04:52c0:6000::/36AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:6000::
- 2a04:52c0:7000::/36AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:7000::
- 2a04:52c0:9000::/36AS60404The Infrastructure Group B.V.RPKI Valid2a04:52c0:9000::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. 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.