BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:c20::/32
Announced exactly
- 2001:c20::/32AS3758SingNetRPKI Valid2001:c20::
- Registry
- APNIC · Singapore · Jul 24, 2002
- Delegated block
- 2001:c20:: – 2001:c20:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:c20::/38AS3758SingNetRPKI Valid2001:c20::
- 2001:c20:10::/48AS3758SingNetRPKI Valid2001:c20:10::
- 2001:c20:18::/48AS3758SingNetRPKI Valid2001:c20:18::
- 2001:c20:3c00::/38AS3758SingNetRPKI Valid2001:c20:3c00::
- 2001:c20:4800::/38AS3758SingNetRPKI Valid2001:c20:4800::
- 2001:c20:4849::/48AS9255Singapore TelecomRPKI Valid2001:c20:4849::
- 2001:c20:485e::/48AS9255Singapore TelecomRPKI Valid2001:c20:485e::
- 2001:c20:485f::/48AS9255Singapore TelecomRPKI Valid2001:c20:485f::
- 2001:c20:486c::/48AS9255Singapore TelecomRPKI Valid2001:c20:486c::
- 2001:c20:4871::/48AS9255Singapore TelecomRPKI Valid2001:c20:4871::
- 2001:c20:4874::/48AS9255Singapore TelecomRPKI Valid2001:c20:4874::
- 2001:c20:487e::/48AS9255Singapore TelecomRPKI Valid2001:c20:487e::
- 2001:c20:4884::/48AS9255Singapore TelecomRPKI Valid2001:c20:4884::
- 2001:c20:4887::/48AS9255Singapore TelecomRPKI Valid2001:c20:4887::
- 2001:c20:488c::/48AS9255Singapore TelecomRPKI Valid2001:c20:488c::
- 2001:c20:488d::/48AS9255Singapore TelecomRPKI Valid2001:c20:488d::
- 2001:c20:488f::/48AS9255Singapore TelecomRPKI Valid2001:c20:488f::
- 2001:c20:4892::/48AS9255Singapore TelecomRPKI Valid2001:c20:4892::
- 2001:c20:4894::/48AS9255Singapore TelecomRPKI Valid2001:c20:4894::
- 2001:c20:4895::/48AS9255Singapore TelecomRPKI Valid2001:c20:4895::
- 2001:c20:489a::/48AS9255Singapore TelecomRPKI Valid2001:c20:489a::
- 2001:c20:48a0::/48AS9255Singapore TelecomRPKI Valid2001:c20:48a0::
- 2001:c20:48a6::/48AS9255Singapore TelecomRPKI Valid2001:c20:48a6::
- 2001:c20:48ae::/48AS9255Singapore TelecomRPKI Valid2001:c20:48ae::
- 2001:c20:48af::/48AS9255Singapore TelecomRPKI Valid2001:c20:48af::
- 2001:c20:48b0::/48AS9255Singapore TelecomRPKI Valid2001:c20:48b0::
- 2001:c20:48b8::/48AS9255Singapore TelecomRPKI Valid2001:c20:48b8::
- 2001:c20:48c2::/48AS9255Singapore TelecomRPKI Valid2001:c20:48c2::
- 2001:c20:48c4::/48AS9255Singapore TelecomRPKI Valid2001:c20:48c4::
- 2001:c20:48c6::/48AS9255Singapore TelecomRPKI Valid2001:c20:48c6::
- 2001:c20:48cc::/48AS9255Singapore TelecomRPKI Valid2001:c20:48cc::
- 2001:c20:48da::/48AS9255Singapore TelecomRPKI Valid2001:c20:48da::
- 2001:c20:48db::/48AS9255Singapore TelecomRPKI Valid2001:c20:48db::
- 2001:c20:48dc::/48AS9255Singapore TelecomRPKI Valid2001:c20:48dc::
- 2001:c20:48e6::/48AS9255Singapore TelecomRPKI Valid2001:c20:48e6::
- 2001:c20:48e7::/48AS9255Singapore TelecomRPKI Valid2001:c20:48e7::
- 2001:c20:48f0::/48AS9255Singapore TelecomRPKI Valid2001:c20:48f0::
- 2001:c20:48fe::/48AS3758SingNetRPKI Valid2001:c20:48fe::
- 2001:c20:4c00::/38AS3758SingNetRPKI Valid2001:c20:4c00::
- 2001:c20:5000::/38AS3758SingNetRPKI Valid2001:c20:5000::
- 2001:c20:6c00::/38AS3758SingNetRPKI Valid2001:c20:6c00::
- 2001:c20:7009::/48AS3758SingNetRPKI Valid2001:c20:7009::
- 2001:c20:7807::/48AS3758SingNetRPKI Valid2001:c20:7807::
- 2001:c20:8405::/48AS3758SingNetRPKI Valid2001:c20:8405::
- 2001:c20:8407::/48AS3758SingNetRPKI Valid2001:c20:8407::
- 2001:c20:8408::/48AS3758SingNetRPKI Valid2001:c20:8408::
- 2001:c20:8409::/48AS3758SingNetRPKI Valid2001:c20:8409::
- 2001:c20:c814::/48AS3758SingNetRPKI Valid2001:c20:c814::
- 2001:c20:c818::/48AS3758SingNetRPKI Valid2001:c20:c818::
- 2001:c20:c819::/48AS9255Singapore TelecomRPKI Valid2001:c20:c819::
- 2001:c20:c824::/48AS9255Singapore TelecomRPKI Valid2001:c20:c824::
- 2001:c20:c825::/48AS9255Singapore TelecomRPKI Valid2001:c20:c825::
- 2001:c20:c826::/48AS9255Singapore TelecomRPKI Valid2001:c20:c826::
- 2001:c20:c827::/48AS9255Singapore TelecomRPKI Valid2001:c20:c827::
- 2001:c20:c831::/48AS9255Singapore TelecomRPKI Valid2001:c20:c831::
- 2001:c20:c835::/48AS9255Singapore TelecomRPKI Valid2001:c20:c835::
- 2001:c20:c839::/48AS9255Singapore TelecomRPKI Valid2001:c20:c839::
- 2001:c20:c83f::/48AS9255Singapore TelecomRPKI Valid2001:c20:c83f::
- 2001:c20:c844::/48AS9255Singapore TelecomRPKI Valid2001:c20:c844::
- 2001:c20:c847::/48AS9255Singapore TelecomRPKI Valid2001:c20:c847::
- 2001:c20:c84e::/48AS9255Singapore TelecomRPKI Valid2001:c20:c84e::
- 2001:c20:c856::/48AS9255Singapore TelecomRPKI Valid2001:c20:c856::
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.