BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
83.239.0.0/16
Annonceret præcist
- 83.239.0.0/16AS12389PJSC RostelecomRPKI Gyldig83.239.0.0
- Register
- RIPE NCC · Rusland · 25. feb. 2004
- Tildelt blok
- 83.239.0.0 – 83.239.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 83.239.0.0/18AS25490PJSC RostelecomRPKI Gyldig83.239.0.0
- 83.239.0.0/20AS25490PJSC RostelecomRPKI Gyldig83.239.0.0
- 83.239.16.0/20AS25490PJSC RostelecomRPKI Gyldig83.239.16.0
- 83.239.32.0/19AS25490PJSC RostelecomRPKI Gyldig83.239.32.0
- 83.239.32.0/21AS25490PJSC RostelecomRPKI Gyldig83.239.32.0
- 83.239.40.0/22AS25490PJSC RostelecomRPKI Gyldig83.239.40.0
- 83.239.44.0/24AS44467PJSC RostelecomRPKI Gyldig83.239.44.0
- 83.239.45.0/24AS44467PJSC RostelecomRPKI Gyldig83.239.45.0
- 83.239.46.0/24AS44467PJSC RostelecomRPKI Gyldig83.239.46.0
- 83.239.47.0/24AS44467PJSC RostelecomRPKI Ugyldig83.239.47.0
- 83.239.48.0/20AS25490PJSC RostelecomRPKI Gyldig83.239.48.0
- 83.239.64.0/19AS25490PJSC RostelecomRPKI Gyldig83.239.64.0
- 83.239.96.0/20AS25490PJSC RostelecomRPKI Gyldig83.239.96.0
- 83.239.112.0/20AS42548PJSC RostelecomRPKI Gyldig83.239.112.0
- 83.239.123.0/24AS42548PJSC RostelecomRPKI Gyldig83.239.123.0
- 83.239.128.0/18AS33934PJSC RostelecomRPKI Gyldig83.239.128.0
- 83.239.128.0/22AS33934PJSC RostelecomRPKI Gyldig83.239.128.0
- 83.239.132.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.132.0
- 83.239.138.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.138.0
- 83.239.140.0/23AS12389PJSC RostelecomRPKI Gyldig83.239.140.0
- 83.239.142.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.142.0
- 83.239.144.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.144.0
- 83.239.148.0/23AS12389PJSC RostelecomRPKI Gyldig83.239.148.0
- 83.239.150.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.150.0
- 83.239.151.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.151.0
- 83.239.152.0/22AS33934PJSC RostelecomRPKI Gyldig83.239.152.0
- 83.239.156.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.156.0
- 83.239.158.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.158.0
- 83.239.159.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.159.0
- 83.239.161.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.161.0
- 83.239.162.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.162.0
- 83.239.164.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.164.0
- 83.239.165.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.165.0
- 83.239.166.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.166.0
- 83.239.167.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.167.0
- 83.239.168.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.168.0
- 83.239.170.0/23AS12389PJSC RostelecomRPKI Gyldig83.239.170.0
- 83.239.172.0/22AS33934PJSC RostelecomRPKI Gyldig83.239.172.0
- 83.239.176.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.176.0
- 83.239.177.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.177.0
- 83.239.178.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.178.0
- 83.239.179.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.179.0
- 83.239.180.0/22AS33934PJSC RostelecomRPKI Gyldig83.239.180.0
- 83.239.184.0/22AS33934PJSC RostelecomRPKI Gyldig83.239.184.0
- 83.239.188.0/23AS33934PJSC RostelecomRPKI Gyldig83.239.188.0
- 83.239.190.0/24AS12389PJSC RostelecomRPKI Gyldig83.239.190.0
- 83.239.191.0/24AS33934PJSC RostelecomRPKI Gyldig83.239.191.0
- 83.239.192.0/21AS42362PJSC RostelecomRPKI Gyldig83.239.192.0
- 83.239.200.0/21AS25490PJSC RostelecomRPKI Gyldig83.239.200.0
- 83.239.207.0/24AS25490PJSC RostelecomRPKI Gyldig83.239.207.0
- 83.239.208.0/20AS42362PJSC RostelecomRPKI Gyldig83.239.208.0
- 83.239.224.0/20AS25490PJSC RostelecomRPKI Gyldig83.239.224.0
- 83.239.240.0/22AS25490PJSC RostelecomRPKI Gyldig83.239.240.0
- 83.239.244.0/22AS25490PJSC RostelecomRPKI Gyldig83.239.244.0
Denne tekst findes endnu ikke på dansk. Den vises på engelsk, indtil en oversættelse er udgivet.
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.
Ofte stillede spørgsmål
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.