BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
137.192.0.0/16
Annonceret præcist
- 137.192.0.0/16AS5006Inteliquent, inc.RPKI Ikke fundet137.192.0.0
- Register
- ARIN · USA · 21. dec. 1989
- Tildelt blok
- 137.192.0.0 – 137.192.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 137.192.1.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.1.0
- 137.192.4.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.4.0
- 137.192.5.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.5.0
- 137.192.7.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.7.0
- 137.192.12.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.12.0
- 137.192.21.0/24AS1347Inteliquent, inc.RPKI Ikke fundet137.192.21.0
- 137.192.24.0/22AS5006Inteliquent, inc.RPKI Ikke fundet137.192.24.0
- 137.192.36.0/22AS5006Inteliquent, inc.RPKI Ikke fundet137.192.36.0
- 137.192.54.0/23AS5006Inteliquent, inc.RPKI Ikke fundet137.192.54.0
- 137.192.76.0/23AS5006Inteliquent, inc.RPKI Ikke fundet137.192.76.0
- 137.192.78.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.78.0
- 137.192.79.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.79.0
- 137.192.80.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.80.0
- 137.192.81.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.81.0
- 137.192.82.0/24AS14929Inteliquent, inc.RPKI Ikke fundet137.192.82.0
- 137.192.101.0/24AS5006Inteliquent, inc.RPKI Ikke fundet137.192.101.0
- 137.192.128.0/23AS5006Inteliquent, inc.RPKI Ikke fundet137.192.128.0
- 137.192.192.0/22AS5006Inteliquent, inc.RPKI Ikke fundet137.192.192.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.