BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
58.181.128.0/17
Announced exactly
- 58.181.128.0/17AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.128.0
- Registry
- APNIC · Thailand · Jul 18, 2005
- Delegated block
- 58.181.128.0 – 58.181.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 58.181.128.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.128.0
- 58.181.144.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.144.0
- 58.181.146.0/23AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.146.0
- 58.181.147.0/24AS45800Suan sunandha Rajabhat University, which is one university in ThailandRPKI Valid58.181.147.0
- 58.181.154.0/24AS38554ICL (THAILAND)RPKI Valid58.181.154.0
- 58.181.160.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.160.0
- 58.181.176.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.176.0
- 58.181.182.0/24AS149762Hakuhodo (Bangkok) Co., Ltd.RPKI Valid58.181.182.0
- 58.181.192.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.192.0
- 58.181.200.0/24AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.200.0
- 58.181.208.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.208.0
- 58.181.212.0/24AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.212.0
- 58.181.224.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.224.0
- 58.181.225.0/24AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.225.0
- 58.181.227.0/24AS17478Bangkok Metropolitan AdministrationRPKI Valid58.181.227.0
- 58.181.240.0/20AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.240.0
- 58.181.248.0/23AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.248.0
- 58.181.252.0/22AS7693KSC Commercial Internet Co. Ltd.RPKI Valid58.181.252.0
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.