BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
5.136.0.0/13
Announced exactly
- 5.136.0.0/13AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.0.0
- Registry
- RIPE NCC · Russia · Jul 3, 2012
- Delegated block
- 5.136.0.0 – 5.143.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 5.136.0.0/15AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.0.0
- 5.136.0.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.0.0
- 5.136.8.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.8.0
- 5.136.16.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.16.0
- 5.136.32.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.32.0
- 5.136.64.0/18AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.64.0
- 5.136.128.0/17AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.136.128.0
- 5.137.0.0/16AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.137.0.0
- 5.137.0.0/17AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.137.0.0
- 5.137.128.0/18AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.137.128.0
- 5.137.192.0/18AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.137.192.0
- 5.138.0.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.138.0.0
- 5.138.64.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.138.64.0
- 5.138.96.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.138.96.0
- 5.138.128.0/17AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.138.128.0
- 5.139.0.0/18AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.0.0
- 5.139.0.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.0.0
- 5.139.8.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.8.0
- 5.139.16.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.16.0
- 5.139.24.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.24.0
- 5.139.64.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.64.0
- 5.139.64.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.64.0
- 5.139.72.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.72.0
- 5.139.80.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.80.0
- 5.139.88.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.88.0
- 5.139.96.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.96.0
- 5.139.128.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.128.0
- 5.139.160.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.160.0
- 5.139.192.0/21AS35177ASI-AS PJSC Rostelecom. Astrakhan branchRPKI Valid5.139.192.0
- 5.139.204.0/23AS35177ASI-AS PJSC Rostelecom. Astrakhan branchRPKI Valid5.139.204.0
- 5.139.207.0/24AS35177ASI-AS PJSC Rostelecom. Astrakhan branchRPKI Valid5.139.207.0
- 5.139.208.0/20AS35177ASI-AS PJSC Rostelecom. Astrakhan branchRPKI Valid5.139.208.0
- 5.139.208.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.208.0
- 5.139.218.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.218.0
- 5.139.234.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.234.0
- 5.139.236.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.236.0
- 5.139.238.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.238.0
- 5.139.240.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.240.0
- 5.139.248.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.139.248.0
- 5.140.0.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.0.0
- 5.140.32.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.32.0
- 5.140.48.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.48.0
- 5.140.64.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.64.0
- 5.140.96.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.96.0
- 5.140.96.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.96.0
- 5.140.112.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.112.0
- 5.140.128.0/19AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.128.0
- 5.140.160.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.160.0
- 5.140.161.0/24AS60716IUT-ASRPKI Valid5.140.161.0
- 5.140.164.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.164.0
- 5.140.165.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.165.0
- 5.140.166.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.166.0
- 5.140.168.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.168.0
- 5.140.169.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.169.0
- 5.140.170.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.170.0
- 5.140.172.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.172.0
- 5.140.176.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.176.0
- 5.140.184.0/21AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.184.0
- 5.140.192.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.192.0
- 5.140.192.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.192.0
- 5.140.196.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.196.0
- 5.140.197.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.197.0
- 5.140.198.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.198.0
- 5.140.199.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.199.0
- 5.140.200.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.200.0
- 5.140.201.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.201.0
- 5.140.204.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.204.0
- 5.140.208.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.208.0
- 5.140.212.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.212.0
- 5.140.213.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.213.0
- 5.140.214.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.214.0
- 5.140.216.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.216.0
- 5.140.220.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.220.0
- 5.140.224.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.224.0
- 5.140.225.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.225.0
- 5.140.226.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.226.0
- 5.140.228.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.228.0
- 5.140.230.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.230.0
- 5.140.232.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.232.0
- 5.140.233.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.233.0
- 5.140.234.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.234.0
- 5.140.235.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.235.0
- 5.140.236.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.236.0
- 5.140.240.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.140.240.0
- 5.141.0.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.0.0
- 5.141.4.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.4.0
- 5.141.9.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.9.0
- 5.141.10.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.10.0
- 5.141.12.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.12.0
- 5.141.16.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.16.0
- 5.141.21.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.21.0
- 5.141.22.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.22.0
- 5.141.23.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.23.0
- 5.141.24.0/22AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.24.0
- 5.141.28.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.28.0
- 5.141.29.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.29.0
- 5.141.30.0/23AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.30.0
- 5.141.64.0/20AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.64.0
- 5.141.80.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.80.0
- 5.141.81.0/24AS12389ROSTELECOM-AS PJSC Rostelecom. Technical TeamRPKI Valid5.141.81.0
Showing the first 100.
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.