BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:1a68::/32
Announced exactly
- 2001:1a68::/32AS15694Atman Sp. z o.o.RPKI Valid2001:1a68::
- Registry
- RIPE NCC · Poland · Feb 20, 2004
- Delegated block
- 2001:1a68:: – 2001:1a68:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:1a68:a::/48AS20555Akademia WIT w WarszawieRPKI Valid2001:1a68:a::
- 2001:1a68:e::/48AS15694Atman Sp. z o.o.RPKI Valid2001:1a68:e::
- 2001:1a68:14::/48AS51373"TELKONEKT" SPOLKA Z OGRANICZONA ODPOWIEDZIALNOSCIARPKI Valid2001:1a68:14::
- 2001:1a68:15::/48AS35491TPnets.com sp. z o.o.RPKI Valid2001:1a68:15::
- 2001:1a68:18::/48AS15694Atman Sp. z o.o.RPKI Valid2001:1a68:18::
- 2001:1a68:19::/48AS57367Atman Sp. z o.o.RPKI Valid2001:1a68:19::
- 2001:1a68:2a::/48AS206838Link4 Towarzystwo Ubezpieczen S.A.RPKI Valid2001:1a68:2a::
- 2001:1a68:2b::/48AS29272WARTA-ASRPKI Valid2001:1a68:2b::
- 2001:1a68:2c::/48AS24723Atman Sp. z o.o.RPKI Valid2001:1a68:2c::
- 2001:1a68:2e::/48AS15694Atman Sp. z o.o.RPKI Valid2001:1a68:2e::
- 2001:1a68:37::/48AS24723Atman Sp. z o.o.RPKI Valid2001:1a68:37::
- 2001:1a68:53::/48AS203756Techland Sp. z o.o.RPKI Valid2001:1a68:53::
- 2001:1a68:ec00::/40AS57367Atman Sp. z o.o.RPKI Valid2001:1a68:ec00::
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.