BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2401:e180::/32
Announced exactly
- 2401:e180::/32AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180::
- Registry
- APNIC · Taiwan · Dec 30, 2014
- Delegated block
- 2401:e180:: – 2401:e180:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2401:e180:7fff::/48AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:7fff::
- 2401:e180:8000::/33AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8000::
- 2401:e180:8800::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8800::
- 2401:e180:8820::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8820::
- 2401:e180:8840::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8840::
- 2401:e180:8860::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8860::
- 2401:e180:8880::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8880::
- 2401:e180:88a0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:88a0::
- 2401:e180:88c0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:88c0::
- 2401:e180:88e0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:88e0::
- 2401:e180:8900::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8900::
- 2401:e180:8920::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8920::
- 2401:e180:8940::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8940::
- 2401:e180:8960::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8960::
- 2401:e180:8980::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8980::
- 2401:e180:89c0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:89c0::
- 2401:e180:89e0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:89e0::
- 2401:e180:8a00::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8a00::
- 2401:e180:8a40::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8a40::
- 2401:e180:8a60::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8a60::
- 2401:e180:8a80::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8a80::
- 2401:e180:8c00::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8c00::
- 2401:e180:8c20::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8c20::
- 2401:e180:8c40::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8c40::
- 2401:e180:8c60::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8c60::
- 2401:e180:8c80::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8c80::
- 2401:e180:8d00::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8d00::
- 2401:e180:8d20::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8d20::
- 2401:e180:8d40::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8d40::
- 2401:e180:8d60::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8d60::
- 2401:e180:8d80::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8d80::
- 2401:e180:8dc0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8dc0::
- 2401:e180:8de0::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8de0::
- 2401:e180:8e20::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8e20::
- 2401:e180:8e60::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8e60::
- 2401:e180:8e80::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8e80::
- 2401:e180:8f00::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8f00::
- 2401:e180:8f20::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8f20::
- 2401:e180:8f40::/43AS9674Far EastTone Telecommunication Co., Ltd.RPKI Valid2401:e180:8f40::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.