BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
2a00:1d34:c000::/36
Annonceret præcist
- 2a00:1d34:c000::/36AS9121Turk Telekomunikasyon Anonim SirketiRPKI Gyldig2a00:1d34:c000::
- Register
- RIPE NCC · Tyrkiet · 12. mar. 2010
- Tildelt blok
- 2a00:1d30:: – 2a00:1d37:ffff:ffff:ffff:ffff:ffff:ffff
Dækkende ruter
- 2a00:1d34::/32AS9121Turk Telekomunikasyon Anonim SirketiRPKI Gyldig2a00:1d34::
Mere specifikke ruter
- 2a00:1d34:c000::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c000::
- 2a00:1d34:c100::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c100::
- 2a00:1d34:c200::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c200::
- 2a00:1d34:c300::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c300::
- 2a00:1d34:c400::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c400::
- 2a00:1d34:c500::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c500::
- 2a00:1d34:c600::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c600::
- 2a00:1d34:c700::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c700::
- 2a00:1d34:c800::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c800::
- 2a00:1d34:c900::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:c900::
- 2a00:1d34:ca00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:ca00::
- 2a00:1d34:cb00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:cb00::
- 2a00:1d34:cc00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:cc00::
- 2a00:1d34:cd00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:cd00::
- 2a00:1d34:ce00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:ce00::
- 2a00:1d34:cf00::/40AS47331TTNet A.S.RPKI Gyldig2a00:1d34:cf00::
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.