BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2604:76c0::/32
Annonceret præcist
- 2604:76c0::/32AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0::
- Register
- ARIN · USA · 16. okt. 2017
- Tildelt blok
- 2604:76c0:: – 2604:76c0:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 2604:76c0:43::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:43::
- 2604:76c0:44::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:44::
- 2604:76c0:a74::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:a74::
- 2604:76c0:21ed::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:21ed::
- 2604:76c0:21ef::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:21ef::
- 2604:76c0:24ed::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:24ed::
- 2604:76c0:24ef::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:24ef::
- 2604:76c0:26ef::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:26ef::
- 2604:76c0:75ed::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:75ed::
- 2604:76c0:75ef::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:75ef::
- 2604:76c0:a188::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:a188::
- 2604:76c0:deac::/47AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:deac::
- 2604:76c0:deec::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:deec::
- 2604:76c0:deed::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:deed::
- 2604:76c0:fafa::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:fafa::
- 2604:76c0:feed::/48AS36103Central Utah Telephone, Inc.RPKI Gyldig2604:76c0:feed::
- 2604:76c0:fefe::/48AS395123CENTRACOM INTERACTIVERPKI Gyldig2604:76c0:fefe::
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.