BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
216.201.128.0/17
Annonceret præcist
- 216.201.128.0/17AS11215LogixRPKI Gyldig216.201.128.0
- Register
- ARIN · USA · 4. maj 1999
- Tildelt blok
- 216.201.128.0 – 216.201.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 216.201.128.0/22AS25956LogixRPKI Gyldig216.201.128.0
- 216.201.132.0/22AS25956LogixRPKI Gyldig216.201.132.0
- 216.201.136.0/22AS25956LogixRPKI Gyldig216.201.136.0
- 216.201.140.0/22AS25956LogixRPKI Gyldig216.201.140.0
- 216.201.144.0/21AS25956LogixRPKI Gyldig216.201.144.0
- 216.201.152.0/22AS25956LogixRPKI Gyldig216.201.152.0
- 216.201.156.0/22AS25956LogixRPKI Gyldig216.201.156.0
- 216.201.160.0/23AS25956LogixRPKI Gyldig216.201.160.0
- 216.201.162.0/23AS25956LogixRPKI Gyldig216.201.162.0
- 216.201.164.0/23AS25956LogixRPKI Gyldig216.201.164.0
- 216.201.166.0/23AS25956LogixRPKI Gyldig216.201.166.0
- 216.201.168.0/22AS25956LogixRPKI Gyldig216.201.168.0
- 216.201.172.0/22AS25956LogixRPKI Gyldig216.201.172.0
- 216.201.176.0/22AS25956LogixRPKI Gyldig216.201.176.0
- 216.201.180.0/23AS25956LogixRPKI Gyldig216.201.180.0
- 216.201.182.0/23AS25956LogixRPKI Gyldig216.201.182.0
- 216.201.184.0/23AS25956LogixRPKI Gyldig216.201.184.0
- 216.201.186.0/23AS25956LogixRPKI Gyldig216.201.186.0
- 216.201.188.0/22AS25956LogixRPKI Gyldig216.201.188.0
- 216.201.192.0/22AS25956LogixRPKI Gyldig216.201.192.0
- 216.201.196.0/23AS25956LogixRPKI Gyldig216.201.196.0
- 216.201.198.0/23AS25956LogixRPKI Gyldig216.201.198.0
- 216.201.200.0/23AS25956LogixRPKI Gyldig216.201.200.0
- 216.201.202.0/23AS25956LogixRPKI Gyldig216.201.202.0
- 216.201.204.0/22AS25956LogixRPKI Gyldig216.201.204.0
- 216.201.208.0/20AS25956LogixRPKI Gyldig216.201.208.0
- 216.201.224.0/23AS25956LogixRPKI Gyldig216.201.224.0
- 216.201.226.0/23AS25956LogixRPKI Gyldig216.201.226.0
- 216.201.228.0/22AS25956LogixRPKI Gyldig216.201.228.0
- 216.201.230.0/23AS25956LogixRPKI Gyldig216.201.230.0
- 216.201.232.0/22AS25956LogixRPKI Gyldig216.201.232.0
- 216.201.236.0/23AS25956LogixRPKI Gyldig216.201.236.0
- 216.201.238.0/23AS25956LogixRPKI Gyldig216.201.238.0
- 216.201.240.0/22AS25956LogixRPKI Gyldig216.201.240.0
- 216.201.244.0/22AS25956LogixRPKI Gyldig216.201.244.0
- 216.201.248.0/22AS25956LogixRPKI Gyldig216.201.248.0
- 216.201.252.0/22AS25956LogixRPKI Gyldig216.201.252.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.