BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
35.200.0.0/14
Announced exactly
- 35.200.0.0/14AS396982Google LLCRPKI Valid35.200.0.0
- Registry
- ARIN · United States · Mar 21, 2017
- Delegated block
- 35.192.0.0 – 35.207.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 35.200.0.0/15AS396982Google LLCRPKI Valid35.200.0.0
- 35.200.0.0/20AS396982Google LLCRPKI Valid35.200.0.0
- 35.200.16.0/20AS396982Google LLCRPKI Valid35.200.16.0
- 35.200.32.0/20AS396982Google LLCRPKI Valid35.200.32.0
- 35.200.48.0/20AS396982Google LLCRPKI Valid35.200.48.0
- 35.200.64.0/20AS396982Google LLCRPKI Valid35.200.64.0
- 35.200.80.0/20AS396982Google LLCRPKI Valid35.200.80.0
- 35.200.96.0/20AS396982Google LLCRPKI Valid35.200.96.0
- 35.200.112.0/20AS396982Google LLCRPKI Valid35.200.112.0
- 35.200.128.0/20AS396982Google LLCRPKI Valid35.200.128.0
- 35.200.144.0/20AS396982Google LLCRPKI Valid35.200.144.0
- 35.200.160.0/20AS396982Google LLCRPKI Valid35.200.160.0
- 35.200.176.0/20AS396982Google LLCRPKI Valid35.200.176.0
- 35.200.192.0/20AS396982Google LLCRPKI Valid35.200.192.0
- 35.200.208.0/20AS396982Google LLCRPKI Valid35.200.208.0
- 35.200.224.0/20AS396982Google LLCRPKI Valid35.200.224.0
- 35.200.240.0/20AS396982Google LLCRPKI Valid35.200.240.0
- 35.201.0.0/20AS396982Google LLCRPKI Valid35.201.0.0
- 35.201.16.0/20AS396982Google LLCRPKI Valid35.201.16.0
- 35.201.32.0/24AS396982Google LLCRPKI Valid35.201.32.0
- 35.201.33.0/24AS396982Google LLCRPKI Valid35.201.33.0
- 35.201.34.0/24AS396982Google LLCRPKI Valid35.201.34.0
- 35.201.35.0/24AS396982Google LLCRPKI Valid35.201.35.0
- 35.201.36.0/24AS396982Google LLCRPKI Valid35.201.36.0
- 35.201.37.0/24AS396982Google LLCRPKI Valid35.201.37.0
- 35.201.38.0/24AS396982Google LLCRPKI Valid35.201.38.0
- 35.201.39.0/24AS396982Google LLCRPKI Valid35.201.39.0
- 35.201.40.0/24AS396982Google LLCRPKI Valid35.201.40.0
- 35.201.41.0/24AS396982Google LLCRPKI Valid35.201.41.0
- 35.201.42.0/24AS396982Google LLCRPKI Valid35.201.42.0
- 35.201.43.0/24AS396982Google LLCRPKI Valid35.201.43.0
- 35.201.44.0/24AS396982Google LLCRPKI Valid35.201.44.0
- 35.201.45.0/24AS396982Google LLCRPKI Valid35.201.45.0
- 35.201.46.0/24AS396982Google LLCRPKI Valid35.201.46.0
- 35.201.47.0/24AS396982Google LLCRPKI Valid35.201.47.0
- 35.201.128.0/20AS396982Google LLCRPKI Valid35.201.128.0
- 35.201.144.0/20AS396982Google LLCRPKI Valid35.201.144.0
- 35.201.160.0/20AS396982Google LLCRPKI Valid35.201.160.0
- 35.201.176.0/20AS396982Google LLCRPKI Valid35.201.176.0
- 35.201.192.0/20AS396982Google LLCRPKI Valid35.201.192.0
- 35.201.208.0/20AS396982Google LLCRPKI Valid35.201.208.0
- 35.201.224.0/20AS396982Google LLCRPKI Valid35.201.224.0
- 35.201.240.0/20AS396982Google LLCRPKI Valid35.201.240.0
- 35.202.0.0/15AS396982Google LLCRPKI Valid35.202.0.0
- 35.202.0.0/20AS396982Google LLCRPKI Valid35.202.0.0
- 35.202.16.0/20AS396982Google LLCRPKI Valid35.202.16.0
- 35.202.32.0/20AS396982Google LLCRPKI Valid35.202.32.0
- 35.202.48.0/20AS396982Google LLCRPKI Valid35.202.48.0
- 35.202.64.0/20AS396982Google LLCRPKI Valid35.202.64.0
- 35.202.80.0/20AS396982Google LLCRPKI Valid35.202.80.0
- 35.202.96.0/20AS396982Google LLCRPKI Valid35.202.96.0
- 35.202.112.0/20AS396982Google LLCRPKI Valid35.202.112.0
- 35.202.128.0/20AS396982Google LLCRPKI Valid35.202.128.0
- 35.202.144.0/20AS396982Google LLCRPKI Valid35.202.144.0
- 35.202.160.0/20AS396982Google LLCRPKI Valid35.202.160.0
- 35.202.176.0/20AS396982Google LLCRPKI Valid35.202.176.0
- 35.202.192.0/20AS396982Google LLCRPKI Valid35.202.192.0
- 35.202.208.0/20AS396982Google LLCRPKI Valid35.202.208.0
- 35.202.224.0/20AS396982Google LLCRPKI Valid35.202.224.0
- 35.202.240.0/20AS396982Google LLCRPKI Valid35.202.240.0
- 35.203.0.0/20AS396982Google LLCRPKI Valid35.203.0.0
- 35.203.16.0/20AS396982Google LLCRPKI Valid35.203.16.0
- 35.203.32.0/20AS396982Google LLCRPKI Valid35.203.32.0
- 35.203.48.0/20AS396982Google LLCRPKI Valid35.203.48.0
- 35.203.64.0/20AS396982Google LLCRPKI Valid35.203.64.0
- 35.203.80.0/20AS396982Google LLCRPKI Valid35.203.80.0
- 35.203.96.0/20AS396982Google LLCRPKI Valid35.203.96.0
- 35.203.112.0/20AS396982Google LLCRPKI Valid35.203.112.0
- 35.203.128.0/20AS396982Google LLCRPKI Valid35.203.128.0
- 35.203.144.0/20AS396982Google LLCRPKI Valid35.203.144.0
- 35.203.160.0/20AS396982Google LLCRPKI Valid35.203.160.0
- 35.203.176.0/20AS396982Google LLCRPKI Valid35.203.176.0
- 35.203.192.0/20AS396982Google LLCRPKI Valid35.203.192.0
- 35.203.208.0/24AS396982Google LLCRPKI Valid35.203.208.0
- 35.203.209.0/24AS396982Google LLCRPKI Valid35.203.209.0
- 35.203.210.0/24AS396982Google LLCRPKI Valid35.203.210.0
- 35.203.211.0/24AS396982Google LLCRPKI Valid35.203.211.0
- 35.203.212.0/24AS396982Google LLCRPKI Valid35.203.212.0
- 35.203.213.0/24AS396982Google LLCRPKI Valid35.203.213.0
- 35.203.214.0/24AS396982Google LLCRPKI Valid35.203.214.0
- 35.203.215.0/24AS396982Google LLCRPKI Valid35.203.215.0
- 35.203.216.0/24AS396982Google LLCRPKI Valid35.203.216.0
- 35.203.217.0/24AS396982Google LLCRPKI Valid35.203.217.0
- 35.203.218.0/24AS396982Google LLCRPKI Valid35.203.218.0
- 35.203.219.0/24AS396982Google LLCRPKI Valid35.203.219.0
- 35.203.220.0/24AS396982Google LLCRPKI Valid35.203.220.0
- 35.203.221.0/24AS396982Google LLCRPKI Valid35.203.221.0
- 35.203.222.0/24AS396982Google LLCRPKI Valid35.203.222.0
- 35.203.223.0/24AS396982Google LLCRPKI Valid35.203.223.0
- 35.203.224.0/23AS139070Google Asia Pacific Pte. Ltd.RPKI Valid35.203.224.0
- 35.203.224.0/24AS396982Google LLCRPKI Valid35.203.224.0
- 35.203.225.0/24AS396982Google LLCRPKI Valid35.203.225.0
- 35.203.226.0/23AS396982Google LLCRPKI Valid35.203.226.0
- 35.203.228.0/23AS396982Google LLCRPKI Valid35.203.228.0
- 35.203.230.0/24AS396982Google LLCRPKI Valid35.203.230.0
- 35.203.232.0/21AS396982Google LLCRPKI Valid35.203.232.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.