BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2a03:db80::/32
Announced exactly
- 2a03:db80::/32AS680Verein zur Foerderung eines Deutschen Forschungsnetzes e.V.RPKI Valid2a03:db80::
- Registry
- RIPE NCC · Germany · Nov 7, 2011
- Delegated block
- 2a03:db80:: – 2a03:db80:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2a03:db80:1c14::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:1c14::
- 2a03:db80:2c10::/48AS47610RWTH Aachen UniversityRPKI Valid2a03:db80:2c10::
- 2a03:db80:2c14::/48AS47610RWTH Aachen UniversityRPKI Valid2a03:db80:2c14::
- 2a03:db80:3410::/48AS12643Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:3410::
- 2a03:db80:3810::/48AS9020Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:3810::
- 2a03:db80:3824::/48AS199578Rheinland-Pfaelzische Technische Universitaet Kaiserslautern-LandauRPKI Valid2a03:db80:3824::
- 2a03:db80:4404::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4404::
- 2a03:db80:4410::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4410::
- 2a03:db80:4414::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4414::
- 2a03:db80:4416::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4416::
- 2a03:db80:4420::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4420::
- 2a03:db80:4424::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4424::
- 2a03:db80:4434::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4434::
- 2a03:db80:4460::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4460::
- 2a03:db80:4470::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4470::
- 2a03:db80:4480::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4480::
- 2a03:db80:4484::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4484::
- 2a03:db80:4494::/48AS5501Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4494::
- 2a03:db80:4810::/48AS60824Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4810::
- 2a03:db80:4814::/48AS60824Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:4814::
- 2a03:db80:5460::/48AS200943Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:5460::
- 2a03:db80:5464::/48AS200943Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:5464::
- 2a03:db80:5470::/48AS200943Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:5470::
- 2a03:db80:5474::/48AS200943Fraunhofer-Gesellschaft zur Foerderung der angewandten Forschung e.V.RPKI Valid2a03:db80:5474::
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.