BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.28.160.0/19
Announced exactly
- 61.28.160.0/19AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.160.0
- Registry
- APNIC · Philippines · Dec 9, 2004
- Delegated block
- 61.28.128.0 – 61.28.191.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.28.160.0/21AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.160.0
- 61.28.160.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.160.0
- 61.28.161.0/24AS152173Robinsons Bank CorporationRPKI Valid61.28.161.0
- 61.28.162.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.162.0
- 61.28.163.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.163.0
- 61.28.164.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.164.0
- 61.28.166.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.166.0
- 61.28.168.0/21AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.168.0
- 61.28.171.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.171.0
- 61.28.172.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Invalid61.28.172.0
- 61.28.173.0/24AS18190SunValley New OrientalRPKI Valid61.28.173.0
- 61.28.174.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.174.0
- 61.28.175.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.175.0
- 61.28.176.0/21AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.176.0
- 61.28.179.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.179.0
- 61.28.184.0/21AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.184.0
- 61.28.184.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.184.0
- 61.28.185.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.185.0
- 61.28.187.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.187.0
- 61.28.191.0/24AS9658Eastern Telecoms Phils., Inc.RPKI Valid61.28.191.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.