BGP-prefix opzoeken
Voer een prefix (of één adres) in. Beantwoord uit onze dagelijkse kopie van de wereldwijde routeringstabel.
2803:f610::/32
Exact aangekondigd
- 2803:f610::/32AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610::
- Register
- LACNIC · Colombia · 13 aug 2021
- Toegewezen blok
- 2803:f610:: – 2803:f610:ffff:ffff:ffff:ffff:ffff:ffff
Overkoepelende routes
Geen minder specifieke route omvat het.
Specifiekere routes
- 2803:f610:1::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:1::
- 2803:f610:3::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:3::
- 2803:f610:5::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:5::
- 2803:f610:6::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:6::
- 2803:f610:7::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:7::
- 2803:f610:40::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:40::
- 2803:f610:101::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:101::
- 2803:f610:102::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:102::
- 2803:f610:104::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:104::
- 2803:f610:200::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:200::
- 2803:f610:500::/48AS271957SOMOS NETWORKS COLOMBIA S.A.S. BICRPKI Geen ROA2803:f610:500::
Deze tekst is nog niet beschikbaar in het Nederlands. Hij wordt in het Engels getoond tot er een vertaling is gepubliceerd.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.
Veelgestelde vragen
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.