BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
165.186.0.0/16
Annonceret præcist
- 165.186.0.0/16AS4668LG CNSRPKI Ikke fundet165.186.0.0
- Register
- APNIC · Sydkorea · 20. aug. 1996
- Tildelt blok
- 165.186.0.0 – 165.186.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 165.186.2.0/23AS4668LG CNSRPKI Ikke fundet165.186.2.0
- 165.186.4.0/22AS4668LG CNSRPKI Ikke fundet165.186.4.0
- 165.186.8.0/22AS4668LG CNSRPKI Ikke fundet165.186.8.0
- 165.186.12.0/24AS4668LG CNSRPKI Ikke fundet165.186.12.0
- 165.186.14.0/24AS4668LG CNSRPKI Ikke fundet165.186.14.0
- 165.186.20.0/22AS4668LG CNSRPKI Ikke fundet165.186.20.0
- 165.186.24.0/22AS4668LG CNSRPKI Ikke fundet165.186.24.0
- 165.186.28.0/23AS4668LG CNSRPKI Ikke fundet165.186.28.0
- 165.186.30.0/23AS4668LG CNSRPKI Ikke fundet165.186.30.0
- 165.186.32.0/21AS4668LG CNSRPKI Ikke fundet165.186.32.0
- 165.186.40.0/22AS4668LG CNSRPKI Ikke fundet165.186.40.0
- 165.186.47.0/24AS4668LG CNSRPKI Ikke fundet165.186.47.0
- 165.186.49.0/24AS4668LG CNSRPKI Ikke fundet165.186.49.0
- 165.186.51.0/24AS4668LG CNSRPKI Ikke fundet165.186.51.0
- 165.186.52.0/22AS4668LG CNSRPKI Ikke fundet165.186.52.0
- 165.186.56.0/22AS4668LG CNSRPKI Ikke fundet165.186.56.0
- 165.186.60.0/22AS4668LG CNSRPKI Ikke fundet165.186.60.0
- 165.186.65.0/24AS4668LG CNSRPKI Ikke fundet165.186.65.0
- 165.186.89.0/24AS4668LG CNSRPKI Ikke fundet165.186.89.0
- 165.186.90.0/23AS4668LG CNSRPKI Ikke fundet165.186.90.0
- 165.186.92.0/23AS4668LG CNSRPKI Ikke fundet165.186.92.0
- 165.186.93.0/24AS4668LG CNSRPKI Ikke fundet165.186.93.0
- 165.186.173.0/24AS4668LG CNSRPKI Ikke fundet165.186.173.0
- 165.186.174.0/24AS4668LG CNSRPKI Ikke fundet165.186.174.0
- 165.186.175.0/24AS4668LG CNSRPKI Ikke fundet165.186.175.0
- 165.186.209.0/24AS4668LG CNSRPKI Ikke fundet165.186.209.0
- 165.186.210.0/23AS4668LG CNSRPKI Ikke fundet165.186.210.0
- 165.186.212.0/24AS4668LG CNSRPKI Ikke fundet165.186.212.0
- 165.186.255.0/24AS4668LG CNSRPKI Ikke fundet165.186.255.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.