BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2a06:c240::/29
Annonceret præcist
- 2a06:c240::/29AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240::
- Register
- RIPE NCC · Sverige · 16. nov. 2015
- Tildelt blok
- 2a06:c240:: – 2a06:c247:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 2a06:c240::/43AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240::
- 2a06:c240:20::/43AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:20::
- 2a06:c240:60::/43AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:60::
- 2a06:c240:80::/43AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:80::
- 2a06:c240:c000::/48AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c000::
- 2a06:c240:c001::/48AS28852Aeris Communications, INC.RPKI Ikke fundet2a06:c240:c001::
- 2a06:c240:c002::/48AS28852Aeris Communications, INC.RPKI Ikke fundet2a06:c240:c002::
- 2a06:c240:c004::/46AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c004::
- 2a06:c240:c008::/46AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c008::
- 2a06:c240:c00c::/46AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c00c::
- 2a06:c240:c010::/46AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c010::
- 2a06:c240:c014::/46AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c014::
- 2a06:c240:c020::/44AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:c020::
- 2a06:c240:e000::/36AS49222Telenor Connexion ABRPKI Ikke fundet2a06:c240:e000::
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.