BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
202.85.0.0/17
Announced exactly
- 202.85.0.0/17AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.0.0
- Registry
- APNIC · Hong Kong SAR China · May 30, 1995
- Delegated block
- 202.85.0.0 – 202.85.15.255
Covering routes
No less-specific route covers it.
More-specific routes
- 202.85.4.0/24AS4760HKT LimitedRPKI Not found202.85.4.0
- 202.85.22.0/23AS4760HKT LimitedRPKI Not found202.85.22.0
- 202.85.31.0/24AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.31.0
- 202.85.35.0/24AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.35.0
- 202.85.43.0/24AS4760HKT LimitedRPKI Not found202.85.43.0
- 202.85.44.0/24AS4760HKT LimitedRPKI Not found202.85.44.0
- 202.85.53.0/24AS137897PAN-LIAN TECHNOLOGY CO., LIMITEDRPKI Not found202.85.53.0
- 202.85.56.0/24AS4760HKT LimitedRPKI Not found202.85.56.0
- 202.85.60.0/24AS4760HKT LimitedRPKI Not found202.85.60.0
- 202.85.64.0/24AS4760HKT LimitedRPKI Not found202.85.64.0
- 202.85.66.0/24AS4760HKT LimitedRPKI Not found202.85.66.0
- 202.85.67.0/24AS4760HKT LimitedRPKI Not found202.85.67.0
- 202.85.68.0/24AS4760HKT LimitedRPKI Not found202.85.68.0
- 202.85.74.0/24AS4760HKT LimitedRPKI Not found202.85.74.0
- 202.85.75.0/24AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.75.0
- 202.85.76.0/24AS137897PAN-LIAN TECHNOLOGY CO., LIMITEDRPKI Not found202.85.76.0
- 202.85.78.0/24AS4760HKT LimitedRPKI Not found202.85.78.0
- 202.85.84.0/24AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.84.0
- 202.85.90.0/24AS4760HKT LimitedRPKI Not found202.85.90.0
- 202.85.102.0/24AS4760HKT LimitedRPKI Not found202.85.102.0
- 202.85.103.0/24AS4760HKT LimitedRPKI Not found202.85.103.0
- 202.85.104.0/24AS4760HKT LimitedRPKI Not found202.85.104.0
- 202.85.106.0/24AS4760HKT LimitedRPKI Not found202.85.106.0
- 202.85.109.0/24AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.109.0
- 202.85.116.0/24AS4760HKT LimitedRPKI Not found202.85.116.0
- 202.85.122.0/23AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found202.85.122.0
- 202.85.124.0/24AS4760HKT LimitedRPKI Not found202.85.124.0
- 202.85.125.0/24AS9925VDC Powerbase Hong Kong Data Centers LimitedRPKI Not found202.85.125.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.