BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2607:f368::/32
Annonceret præcist
- 2607:f368::/32AS32982U.S. Department of EnergyRPKI Ikke fundet2607:f368::
- Register
- ARIN · USA · 6. mar. 2008
- Tildelt blok
- 2607:f368:: – 2607:f368:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 2607:f368:f::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:f::
- 2607:f368:300::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:300::
- 2607:f368:f00::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:f00::
- 2607:f368:1003::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:1003::
- 2607:f368:2000::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:2000::
- 2607:f368:2800::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:2800::
- 2607:f368:2900::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:2900::
- 2607:f368:2a00::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:2a00::
- 2607:f368:2c00::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:2c00::
- 2607:f368:320f::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:320f::
- 2607:f368:3220::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:3220::
- 2607:f368:3700::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:3700::
- 2607:f368:3800::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:3800::
- 2607:f368:3a00::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:3a00::
- 2607:f368:3d00::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:3d00::
- 2607:f368:4500::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:4500::
- 2607:f368:4700::/40AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:4700::
- 2607:f368:8301::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:8301::
- 2607:f368:8302::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:8302::
- 2607:f368:830a::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:830a::
- 2607:f368:8312::/47AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:8312::
- 2607:f368:8318::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:8318::
- 2607:f368:831c::/47AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:831c::
- 2607:f368:831e::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:831e::
- 2607:f368:8324::/48AS46846U.S. Department of EnergyRPKI Ikke fundet2607:f368:8324::
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.