BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a02:580::/29
Announced exactly
- 2a02:580::/29AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:580::
- Registry
- RIPE NCC · Greece · Jul 3, 2008
- Delegated block
- 2a02:580:: – 2a02:587:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a02:582:1800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:582:1800::
- 2a02:582:4800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:582:4800::
- 2a02:582:5800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:582:5800::
- 2a02:582:7000::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:582:7000::
- 2a02:586::/35AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586::
- 2a02:586:2000::/36AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586:2000::
- 2a02:586:3000::/36AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586:3000::
- 2a02:586:4000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586:4000::
- 2a02:586:8000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586:8000::
- 2a02:586:c000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:586:c000::
- 2a02:587::/35AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587::
- 2a02:587:1800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:1800::
- 2a02:587:2000::/36AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:2000::
- 2a02:587:3000::/36AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:3000::
- 2a02:587:4000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:4000::
- 2a02:587:4800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:4800::
- 2a02:587:4c00::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:4c00::
- 2a02:587:501a::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:501a::
- 2a02:587:501d::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:501d::
- 2a02:587:501e::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:501e::
- 2a02:587:50da::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:50da::
- 2a02:587:50f7::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:50f7::
- 2a02:587:50fa::/48AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:50fa::
- 2a02:587:5400::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:5400::
- 2a02:587:5800::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:5800::
- 2a02:587:5c00::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:5c00::
- 2a02:587:6000::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:6000::
- 2a02:587:6400::/38AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:6400::
- 2a02:587:8000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:8000::
- 2a02:587:8400::/40AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:8400::
- 2a02:587:c000::/34AS6799Ote SA (Hellenic Telecommunications Organisation)RPKI Valid2a02:587:c000::
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.