BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2001:5f8::/32
Annonceret præcist
- 2001:5f8::/32AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8::
- Register
- ARIN · USA · 9. maj 2003
- Tildelt blok
- 2001:5f8:: – 2001:5f8:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 2001:5f8:300::/40AS397446Midwest Fiber Network, LLCRPKI Ikke fundet2001:5f8:300::
- 2001:5f8:700::/40AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:700::
- 2001:5f8:b00::/40AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:b00::
- 2001:5f8:7d09::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7d09::
- 2001:5f8:7e03::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7e03::
- 2001:5f8:7f09::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f09::
- 2001:5f8:7f0b::/48AS18883FiberNet Communications L.C.RPKI Ikke fundet2001:5f8:7f0b::
- 2001:5f8:7f0d::/48AS399693Northwest CommunicationsRPKI Ikke fundet2001:5f8:7f0d::
- 2001:5f8:7f10::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f10::
- 2001:5f8:7f11::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f11::
- 2001:5f8:7f14::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f14::
- 2001:5f8:7f24::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f24::
- 2001:5f8:7f26::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f26::
- 2001:5f8:7f27::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:7f27::
- 2001:5f8:8300::/40AS33690Aureon Network ServicesRPKI Ikke fundet2001:5f8:8300::
- 2001:5f8:fb31::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:fb31::
- 2001:5f8:fe02::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:fe02::
- 2001:5f8:fe03::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:fe03::
- 2001:5f8:fe04::/48AS5056Aureon Network ServicesRPKI Ikke fundet2001:5f8:fe04::
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.