BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
94.233.0.0/17
Announced exactly
- 94.233.0.0/17AS33934PJSC RostelecomRPKI Valid94.233.0.0
- Registry
- RIPE NCC · Russia · Sep 18, 2008
- Delegated block
- 94.233.0.0 – 94.233.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 94.233.0.0/20AS12389PJSC RostelecomRPKI Valid94.233.0.0
- 94.233.16.0/22AS12389PJSC RostelecomRPKI Valid94.233.16.0
- 94.233.20.0/24AS33934PJSC RostelecomRPKI Valid94.233.20.0
- 94.233.23.0/24AS33934PJSC RostelecomRPKI Valid94.233.23.0
- 94.233.24.0/22AS33934PJSC RostelecomRPKI Valid94.233.24.0
- 94.233.28.0/24AS33934PJSC RostelecomRPKI Valid94.233.28.0
- 94.233.30.0/23AS33934PJSC RostelecomRPKI Valid94.233.30.0
- 94.233.32.0/21AS33934PJSC RostelecomRPKI Valid94.233.32.0
- 94.233.40.0/22AS12389PJSC RostelecomRPKI Valid94.233.40.0
- 94.233.44.0/23AS33934PJSC RostelecomRPKI Valid94.233.44.0
- 94.233.46.0/24AS12389PJSC RostelecomRPKI Valid94.233.46.0
- 94.233.47.0/24AS33934PJSC RostelecomRPKI Valid94.233.47.0
- 94.233.48.0/21AS33934PJSC RostelecomRPKI Valid94.233.48.0
- 94.233.56.0/21AS12389PJSC RostelecomRPKI Valid94.233.56.0
- 94.233.66.0/23AS33934PJSC RostelecomRPKI Valid94.233.66.0
- 94.233.68.0/23AS12389PJSC RostelecomRPKI Valid94.233.68.0
- 94.233.70.0/24AS33934PJSC RostelecomRPKI Valid94.233.70.0
- 94.233.71.0/24AS12389PJSC RostelecomRPKI Valid94.233.71.0
- 94.233.72.0/23AS12389PJSC RostelecomRPKI Valid94.233.72.0
- 94.233.74.0/23AS33934PJSC RostelecomRPKI Valid94.233.74.0
- 94.233.76.0/23AS33934PJSC RostelecomRPKI Valid94.233.76.0
- 94.233.78.0/24AS33934PJSC RostelecomRPKI Valid94.233.78.0
- 94.233.80.0/22AS12389PJSC RostelecomRPKI Valid94.233.80.0
- 94.233.85.0/24AS33934PJSC RostelecomRPKI Valid94.233.85.0
- 94.233.87.0/24AS33934PJSC RostelecomRPKI Valid94.233.87.0
- 94.233.88.0/21AS12389PJSC RostelecomRPKI Valid94.233.88.0
- 94.233.96.0/21AS12389PJSC RostelecomRPKI Valid94.233.96.0
- 94.233.106.0/24AS33934PJSC RostelecomRPKI Valid94.233.106.0
- 94.233.107.0/24AS33934PJSC RostelecomRPKI Valid94.233.107.0
- 94.233.108.0/22AS12389PJSC RostelecomRPKI Valid94.233.108.0
- 94.233.112.0/21AS12389PJSC RostelecomRPKI Valid94.233.112.0
- 94.233.120.0/22AS12389PJSC RostelecomRPKI Valid94.233.120.0
- 94.233.126.0/23AS33934PJSC RostelecomRPKI Valid94.233.126.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.