BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
216.183.224.0/19
Announced exactly
- 216.183.224.0/19AS21769Colocation America CorporationRPKI Valid216.183.224.0
- Registry
- ARIN · United States · Sep 17, 2025
- Delegated block
- 216.183.224.0 – 216.183.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 216.183.224.0/24AS47007Colocation America CorporationRPKI Valid216.183.224.0
- 216.183.225.0/24AS47007Colocation America CorporationRPKI Valid216.183.225.0
- 216.183.226.0/24AS47007Colocation America CorporationRPKI Valid216.183.226.0
- 216.183.227.0/24AS47007Colocation America CorporationRPKI Valid216.183.227.0
- 216.183.230.0/24AS26042FiberState, LLCRPKI Valid216.183.230.0
- 216.183.232.0/24AS402327AnterisRPKI Valid216.183.232.0
- 216.183.233.0/24AS402327AnterisRPKI Valid216.183.233.0
- 216.183.234.0/24AS214054Nitrode Corporation trading as ChartVPS TechnologiesRPKI Valid216.183.234.0
- 216.183.235.0/24AS214054Nitrode Corporation trading as ChartVPS TechnologiesRPKI Valid216.183.235.0
- 216.183.236.0/24AS32693NEXXRPKI Valid216.183.236.0
- 216.183.238.0/24AS32693NEXXRPKI Valid216.183.238.0
- 216.183.239.0/24AS272109FIBERLINK COMMUNICATIONS, S.A.RPKI Valid216.183.239.0
- 216.183.240.0/24AS397423Tier.Net Technologies LLCRPKI Valid216.183.240.0
- 216.183.244.0/24AS21859Zenlayer IncRPKI Valid216.183.244.0
- 216.183.245.0/24AS40564VOCOM International Telecommunication, INC.RPKI Valid216.183.245.0
- 216.183.246.0/24AS394380Leaseweb USA, Inc.RPKI Valid216.183.246.0
- 216.183.247.0/24AS212384Simoresta UABRPKI Valid216.183.247.0
- 216.183.248.0/24AS174Cogent Communications, LLCRPKI Valid216.183.248.0
- 216.183.250.0/24AS6079RCNRPKI Valid216.183.250.0
- 216.183.251.0/24AS174Cogent Communications, LLCRPKI Valid216.183.251.0
- 216.183.252.0/23AS9304HGC Global Communications LimitedRPKI Valid216.183.252.0
- 216.183.254.0/24AS212384Simoresta UABRPKI Valid216.183.254.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.