BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
135.245.0.0/16
Announced exactly
- 135.245.0.0/16AS10455Nokia of America CorporationRPKI Not found135.245.0.0
- Registry
- ARIN · United States · Apr 30, 1996
- Delegated block
- 135.245.0.0 – 135.245.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 135.245.0.0/24AS10455Nokia of America CorporationRPKI Not found135.245.0.0
- 135.245.1.0/24AS10455Nokia of America CorporationRPKI Not found135.245.1.0
- 135.245.2.0/24AS10455Nokia of America CorporationRPKI Not found135.245.2.0
- 135.245.3.0/24AS10455Nokia of America CorporationRPKI Not found135.245.3.0
- 135.245.4.0/24AS10455Nokia of America CorporationRPKI Not found135.245.4.0
- 135.245.8.0/24AS10455Nokia of America CorporationRPKI Not found135.245.8.0
- 135.245.10.0/24AS10455Nokia of America CorporationRPKI Not found135.245.10.0
- 135.245.12.0/23AS10455Nokia of America CorporationRPKI Not found135.245.12.0
- 135.245.14.0/24AS10455Nokia of America CorporationRPKI Not found135.245.14.0
- 135.245.16.0/20AS10455Nokia of America CorporationRPKI Not found135.245.16.0
- 135.245.16.0/21AS10455Nokia of America CorporationRPKI Not found135.245.16.0
- 135.245.20.0/22AS10455Nokia of America CorporationRPKI Not found135.245.20.0
- 135.245.24.0/21AS10455Nokia of America CorporationRPKI Not found135.245.24.0
- 135.245.24.0/22AS10455Nokia of America CorporationRPKI Not found135.245.24.0
- 135.245.40.0/22AS10455Nokia of America CorporationRPKI Not found135.245.40.0
- 135.245.44.0/22AS10455Nokia of America CorporationRPKI Not found135.245.44.0
- 135.245.48.0/24AS10455Nokia of America CorporationRPKI Not found135.245.48.0
- 135.245.49.0/24AS10455Nokia of America CorporationRPKI Not found135.245.49.0
- 135.245.50.0/24AS10455Nokia of America CorporationRPKI Not found135.245.50.0
- 135.245.52.0/24AS10455Nokia of America CorporationRPKI Not found135.245.52.0
- 135.245.53.0/24AS10455Nokia of America CorporationRPKI Not found135.245.53.0
- 135.245.54.0/24AS10455Nokia of America CorporationRPKI Not found135.245.54.0
- 135.245.55.0/24AS10455Nokia of America CorporationRPKI Not found135.245.55.0
- 135.245.56.0/23AS10455Nokia of America CorporationRPKI Not found135.245.56.0
- 135.245.58.0/23AS10455Nokia of America CorporationRPKI Not found135.245.58.0
- 135.245.108.0/22AS2579Nokia of America CorporationRPKI Not found135.245.108.0
- 135.245.111.0/24AS2579Nokia of America CorporationRPKI Not found135.245.111.0
- 135.245.115.0/24AS34414NOKIA-APAC Nokia APACRPKI Not found135.245.115.0
- 135.245.117.0/24AS34414NOKIA-APAC Nokia APACRPKI Not found135.245.117.0
- 135.245.121.0/24AS34414NOKIA-APAC Nokia APACRPKI Not found135.245.121.0
- 135.245.128.0/22AS34414NOKIA-APAC Nokia APACRPKI Not found135.245.128.0
- 135.245.190.0/23AS34414NOKIA-APAC Nokia APACRPKI Not found135.245.190.0
- 135.245.192.0/18AS8983NOKIA-ASRPKI Not found135.245.192.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.