BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
74.82.0.0/18
Annonceret præcist
- 74.82.0.0/18AS6939Hurricane Electric LLCRPKI Gyldig74.82.0.0
- Register
- ARIN · USA · 22. jul. 2008
- Tildelt blok
- 74.82.0.0 – 74.82.63.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 74.82.0.0/24AS394740Consolidated CooperativeRPKI Gyldig74.82.0.0
- 74.82.6.0/23AS36103Central Utah Telephone, Inc.RPKI Gyldig74.82.6.0
- 74.82.8.0/24AS54288SolidTools Technology, Inc.RPKI Gyldig74.82.8.0
- 74.82.16.0/24AS394230Civilized Discourse Construction Kit, Inc.RPKI Gyldig74.82.16.0
- 74.82.22.0/23AS6939Hurricane Electric LLCRPKI Gyldig74.82.22.0
- 74.82.25.0/24AS54466ISSQUARED, Inc.RPKI Gyldig74.82.25.0
- 74.82.28.0/23AS39499647-2339071RPKI Gyldig74.82.28.0
- 74.82.30.0/24AS39499647-2339071RPKI Gyldig74.82.30.0
- 74.82.31.0/24AS39499647-2339071RPKI Gyldig74.82.31.0
- 74.82.34.0/24AS398885Aerwave, Inc.RPKI Gyldig74.82.34.0
- 74.82.43.0/24AS18779EGIHostingRPKI Gyldig74.82.43.0
- 74.82.44.0/23AS36103Central Utah Telephone, Inc.RPKI Gyldig74.82.44.0
- 74.82.46.0/24AS6939Hurricane Electric LLCRPKI Gyldig74.82.46.0
- 74.82.48.0/22AS6939Hurricane Electric LLCRPKI Gyldig74.82.48.0
- 74.82.53.0/24AS39499647-2339071RPKI Gyldig74.82.53.0
- 74.82.54.0/23AS36103Central Utah Telephone, Inc.RPKI Gyldig74.82.54.0
- 74.82.56.0/24AS63186Call One Inc.RPKI Gyldig74.82.56.0
- 74.82.57.0/24AS36103Central Utah Telephone, Inc.RPKI Gyldig74.82.57.0
- 74.82.58.0/24AS401977Sierra Nevada CommunicationsRPKI Gyldig74.82.58.0
- 74.82.63.0/24AS401742ServerOptimaRPKI Gyldig74.82.63.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.