BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:938::/32
Announced exactly
- 2001:938::/32AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938::
- Registry
- RIPE NCC · Austria · Oct 14, 2002
- Delegated block
- 2001:938:: – 2001:938:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:938:2020::/45AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:2020::
- 2001:938:2028::/45AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:2028::
- 2001:938:2030::/45AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:2030::
- 2001:938:2038::/45AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:2038::
- 2001:938:2040::/45AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:2040::
- 2001:938:4000::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4000::
- 2001:938:4002::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4002::
- 2001:938:4003::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4003::
- 2001:938:4004::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4004::
- 2001:938:4007::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4007::
- 2001:938:400c::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:400c::
- 2001:938:400d::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:400d::
- 2001:938:400f::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:400f::
- 2001:938:4011::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4011::
- 2001:938:4014::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4014::
- 2001:938:4016::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4016::
- 2001:938:4017::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4017::
- 2001:938:4029::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4029::
- 2001:938:402a::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:402a::
- 2001:938:402b::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:402b::
- 2001:938:402e::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:402e::
- 2001:938:4032::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4032::
- 2001:938:4034::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4034::
- 2001:938:4035::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4035::
- 2001:938:4036::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4036::
- 2001:938:403a::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:403a::
- 2001:938:403f::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:403f::
- 2001:938:4040::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4040::
- 2001:938:4042::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4042::
- 2001:938:4043::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4043::
- 2001:938:4044::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4044::
- 2001:938:4046::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4046::
- 2001:938:4053::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4053::
- 2001:938:4054::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4054::
- 2001:938:4055::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4055::
- 2001:938:4056::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4056::
- 2001:938:4058::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:4058::
- 2001:938:405a::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:405a::
- 2001:938:405c::/48AS8437Hutchison Drei Austria GmbHRPKI Valid2001:938:405c::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.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.