BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
199.106.0.0/15
Announced exactly
- 199.106.0.0/15AS7018AT&T Enterprises, LLCRPKI Not found199.106.0.0
- Registry
- ARIN · United States · Jan 10, 1994
- Delegated block
- 199.106.0.0 – 199.107.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 199.106.88.0/24AS399604EXL SERVICE.COM, LLCRPKI Not found199.106.88.0
- 199.106.96.0/22AS11030Qualcomm, Inc.RPKI Valid199.106.96.0
- 199.106.100.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.100.0
- 199.106.101.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.101.0
- 199.106.102.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.102.0
- 199.106.103.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.103.0
- 199.106.104.0/23AS11030Qualcomm, Inc.RPKI Valid199.106.104.0
- 199.106.106.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.106.0
- 199.106.107.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.107.0
- 199.106.108.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.108.0
- 199.106.109.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.109.0
- 199.106.110.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.110.0
- 199.106.111.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.111.0
- 199.106.112.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.112.0
- 199.106.113.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.113.0
- 199.106.114.0/23AS11030Qualcomm, Inc.RPKI Valid199.106.114.0
- 199.106.116.0/22AS11030Qualcomm, Inc.RPKI Valid199.106.116.0
- 199.106.120.0/23AS11030Qualcomm, Inc.RPKI Valid199.106.120.0
- 199.106.122.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.122.0
- 199.106.123.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.123.0
- 199.106.124.0/23AS11030Qualcomm, Inc.RPKI Valid199.106.124.0
- 199.106.126.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.126.0
- 199.106.127.0/24AS11030Qualcomm, Inc.RPKI Valid199.106.127.0
- 199.107.16.0/24AS13788US CourtsRPKI Not found199.107.16.0
- 199.107.17.0/24AS13788US CourtsRPKI Not found199.107.17.0
- 199.107.18.0/24AS13788US CourtsRPKI Not found199.107.18.0
- 199.107.19.0/24AS13788US CourtsRPKI Not found199.107.19.0
- 199.107.20.0/22AS13788US CourtsRPKI Not found199.107.20.0
- 199.107.32.0/24AS394572Tyler Technologies, Inc.RPKI Not found199.107.32.0
- 199.107.38.0/24AS13788US CourtsRPKI Not found199.107.38.0
- 199.107.120.0/24AS36157Acer America CorporationRPKI Not found199.107.120.0
- 199.107.160.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.160.0
- 199.107.161.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.161.0
- 199.107.162.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.162.0
- 199.107.163.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.163.0
- 199.107.164.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.164.0
- 199.107.165.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.165.0
- 199.107.166.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.166.0
- 199.107.167.0/24AS11045Sterling Communications, Inc.RPKI Not found199.107.167.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.