BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
42.200.192.0/19
Announced exactly
- 42.200.192.0/19AS4760HKT LimitedRPKI Not found42.200.192.0
- Registry
- APNIC · Hong Kong SAR China · Mar 22, 2011
- Delegated block
- 42.200.0.0 – 42.200.255.255
Covering routes
- 42.200.0.0/16AS4515PCCW IMS Ltd (PCCW Business Internet Access)RPKI Not found42.200.0.0
More-specific routes
- 42.200.192.0/24AS4760HKT LimitedRPKI Not found42.200.192.0
- 42.200.193.0/24AS4760HKT LimitedRPKI Not found42.200.193.0
- 42.200.194.0/24AS4760HKT LimitedRPKI Not found42.200.194.0
- 42.200.195.0/24AS4760HKT LimitedRPKI Not found42.200.195.0
- 42.200.196.0/24AS4760HKT LimitedRPKI Not found42.200.196.0
- 42.200.197.0/24AS4760HKT LimitedRPKI Not found42.200.197.0
- 42.200.198.0/24AS4760HKT LimitedRPKI Not found42.200.198.0
- 42.200.199.0/24AS4760HKT LimitedRPKI Not found42.200.199.0
- 42.200.200.0/24AS4760HKT LimitedRPKI Not found42.200.200.0
- 42.200.201.0/24AS4760HKT LimitedRPKI Not found42.200.201.0
- 42.200.202.0/24AS4760HKT LimitedRPKI Not found42.200.202.0
- 42.200.203.0/24AS4760HKT LimitedRPKI Not found42.200.203.0
- 42.200.204.0/24AS4760HKT LimitedRPKI Not found42.200.204.0
- 42.200.205.0/24AS4760HKT LimitedRPKI Not found42.200.205.0
- 42.200.206.0/24AS4760HKT LimitedRPKI Not found42.200.206.0
- 42.200.207.0/24AS4760HKT LimitedRPKI Not found42.200.207.0
- 42.200.208.0/24AS4760HKT LimitedRPKI Not found42.200.208.0
- 42.200.209.0/24AS4760HKT LimitedRPKI Not found42.200.209.0
- 42.200.210.0/24AS4760HKT LimitedRPKI Not found42.200.210.0
- 42.200.211.0/24AS4760HKT LimitedRPKI Not found42.200.211.0
- 42.200.212.0/24AS4760HKT LimitedRPKI Not found42.200.212.0
- 42.200.213.0/24AS4760HKT LimitedRPKI Not found42.200.213.0
- 42.200.214.0/24AS4760HKT LimitedRPKI Not found42.200.214.0
- 42.200.215.0/24AS4760HKT LimitedRPKI Not found42.200.215.0
- 42.200.216.0/24AS4760HKT LimitedRPKI Not found42.200.216.0
- 42.200.217.0/24AS4760HKT LimitedRPKI Not found42.200.217.0
- 42.200.218.0/24AS4760HKT LimitedRPKI Not found42.200.218.0
- 42.200.219.0/24AS4760HKT LimitedRPKI Not found42.200.219.0
- 42.200.220.0/24AS4760HKT LimitedRPKI Not found42.200.220.0
- 42.200.221.0/24AS4760HKT LimitedRPKI Not found42.200.221.0
- 42.200.222.0/24AS4760HKT LimitedRPKI Not found42.200.222.0
- 42.200.223.0/24AS4760HKT LimitedRPKI Not found42.200.223.0
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.