BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.220.0.0/15
Announced exactly
- 204.220.0.0/15AS5006Inteliquent, inc.RPKI Not found204.220.0.0
- Registry
- ARIN · United States · Jan 5, 1995
- Delegated block
- 204.220.0.0 – 204.221.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.220.52.0/24AS5006Inteliquent, inc.RPKI Not found204.220.52.0
- 204.220.62.0/24AS5006Inteliquent, inc.RPKI Not found204.220.62.0
- 204.220.64.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.64.0
- 204.220.90.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.90.0
- 204.220.91.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.91.0
- 204.220.92.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.92.0
- 204.220.94.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.94.0
- 204.220.95.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.95.0
- 204.220.152.0/24AS5006Inteliquent, inc.RPKI Not found204.220.152.0
- 204.220.156.0/24AS5006Inteliquent, inc.RPKI Not found204.220.156.0
- 204.220.160.0/24AS200069MAILJET SASRPKI Not found204.220.160.0
- 204.220.161.0/24AS200069MAILJET SASRPKI Not found204.220.161.0
- 204.220.162.0/24AS200069MAILJET SASRPKI Not found204.220.162.0
- 204.220.163.0/24AS200069MAILJET SASRPKI Not found204.220.163.0
- 204.220.164.0/24AS200069MAILJET SASRPKI Not found204.220.164.0
- 204.220.165.0/24AS200069MAILJET SASRPKI Not found204.220.165.0
- 204.220.166.0/24AS200069MAILJET SASRPKI Not found204.220.166.0
- 204.220.167.0/24AS200069MAILJET SASRPKI Not found204.220.167.0
- 204.220.168.0/24AS200069MAILJET SASRPKI Not found204.220.168.0
- 204.220.169.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.169.0
- 204.220.170.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.170.0
- 204.220.171.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.171.0
- 204.220.172.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.172.0
- 204.220.173.0/24AS200069MAILJET SASRPKI Not found204.220.173.0
- 204.220.174.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.174.0
- 204.220.175.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.175.0
- 204.220.176.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.176.0
- 204.220.178.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.178.0
- 204.220.179.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.179.0
- 204.220.180.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.180.0
- 204.220.181.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.181.0
- 204.220.182.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.182.0
- 204.220.183.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.183.0
- 204.220.184.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.184.0
- 204.220.186.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.186.0
- 204.220.187.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.187.0
- 204.220.188.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.188.0
- 204.220.189.0/24AS396479Mailgun Technologies Inc.RPKI Not found204.220.189.0
- 204.220.190.0/24AS396982Google LLCRPKI Valid204.220.190.0
- 204.220.191.0/24AS396479Mailgun Technologies Inc.RPKI Valid204.220.191.0
- 204.221.17.0/24AS33362Wikstrom Telephone Company, IncorporatedRPKI Valid204.221.17.0
- 204.221.18.0/23AS33362Wikstrom Telephone Company, IncorporatedRPKI Valid204.221.18.0
- 204.221.76.0/24AS14738Digi-Key CorporationRPKI Not found204.221.76.0
- 204.221.77.0/24AS14738Digi-Key CorporationRPKI Not found204.221.77.0
- 204.221.144.0/22AS33362Wikstrom Telephone Company, IncorporatedRPKI Valid204.221.144.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.