BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
164.139.0.0/16
Annonceret præcist
- 164.139.0.0/16AS8569METRO Digital GmbHRPKI Ikke fundet164.139.0.0
- Register
- RIPE NCC · Tyskland · 16. dec. 1993
- Tildelt blok
- 164.139.0.0 – 164.139.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 164.139.0.0/21AS8569METRO Digital GmbHRPKI Ikke fundet164.139.0.0
- 164.139.8.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.8.0
- 164.139.12.0/22AS39290METRO Digital GmbHRPKI Ikke fundet164.139.12.0
- 164.139.16.0/20AS8569METRO Digital GmbHRPKI Ikke fundet164.139.16.0
- 164.139.32.0/20AS39290METRO Digital GmbHRPKI Ikke fundet164.139.32.0
- 164.139.34.0/24AS39290METRO Digital GmbHRPKI Ikke fundet164.139.34.0
- 164.139.36.0/24AS8569METRO Digital GmbHRPKI Ikke fundet164.139.36.0
- 164.139.40.0/24AS8569METRO Digital GmbHRPKI Ikke fundet164.139.40.0
- 164.139.48.0/20AS8569METRO Digital GmbHRPKI Ikke fundet164.139.48.0
- 164.139.64.0/20AS8569METRO Digital GmbHRPKI Ikke fundet164.139.64.0
- 164.139.80.0/22AS39290METRO Digital GmbHRPKI Ikke fundet164.139.80.0
- 164.139.84.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.84.0
- 164.139.88.0/21AS8569METRO Digital GmbHRPKI Ikke fundet164.139.88.0
- 164.139.96.0/19AS8569METRO Digital GmbHRPKI Ikke fundet164.139.96.0
- 164.139.128.0/21AS39290METRO Digital GmbHRPKI Ikke fundet164.139.128.0
- 164.139.136.0/21AS8569METRO Digital GmbHRPKI Ikke fundet164.139.136.0
- 164.139.144.0/20AS8569METRO Digital GmbHRPKI Ikke fundet164.139.144.0
- 164.139.160.0/19AS8569METRO Digital GmbHRPKI Ikke fundet164.139.160.0
- 164.139.160.0/21AS8569METRO Digital GmbHRPKI Ikke fundet164.139.160.0
- 164.139.168.0/21AS39290METRO Digital GmbHRPKI Ikke fundet164.139.168.0
- 164.139.176.0/20AS8569METRO Digital GmbHRPKI Ikke fundet164.139.176.0
- 164.139.192.0/19AS8569METRO Digital GmbHRPKI Ikke fundet164.139.192.0
- 164.139.224.0/21AS8569METRO Digital GmbHRPKI Ikke fundet164.139.224.0
- 164.139.232.0/22AS33959METRO Kereskedelmi Kft.RPKI Ikke fundet164.139.232.0
- 164.139.236.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.236.0
- 164.139.244.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.244.0
- 164.139.248.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.248.0
- 164.139.252.0/22AS8569METRO Digital GmbHRPKI Ikke fundet164.139.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.