BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
198.30.0.0/16
Annonceret præcist
- 198.30.0.0/16AS600OARnetRPKI Ikke fundet198.30.0.0
- Register
- ARIN · USA · 21. dec. 1992
- Tildelt blok
- 198.30.0.0 – 198.30.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 198.30.13.0/24AS17135Ohio UniversityRPKI Ikke fundet198.30.13.0
- 198.30.56.0/21AS36831UNASSIGNEDRPKI Ikke fundet198.30.56.0
- 198.30.81.0/24AS394061Franklin CountyRPKI Ikke fundet198.30.81.0
- 198.30.88.0/23AS3112OARnetRPKI Ikke fundet198.30.88.0
- 198.30.131.0/24AS25822Tiffin UniversityRPKI Ikke fundet198.30.131.0
- 198.30.132.0/24AS25822Tiffin UniversityRPKI Ikke fundet198.30.132.0
- 198.30.154.0/23AS17135Ohio UniversityRPKI Ikke fundet198.30.154.0
- 198.30.160.0/22AS36831UNASSIGNEDRPKI Ikke fundet198.30.160.0
- 198.30.164.0/22AS36831UNASSIGNEDRPKI Ikke fundet198.30.164.0
- 198.30.180.0/23AS2025University of ToledoRPKI Ikke fundet198.30.180.0
- 198.30.181.0/24AS2025University of ToledoRPKI Ikke fundet198.30.181.0
- 198.30.182.0/24AS396381Genesis Healthcare SystemRPKI Ikke fundet198.30.182.0
- 198.30.183.0/24AS3112OARnetRPKI Ikke fundet198.30.183.0
- 198.30.187.0/24AS26898ConnectRPKI Ikke fundet198.30.187.0
- 198.30.192.0/24AS2025University of ToledoRPKI Ikke fundet198.30.192.0
- 198.30.200.0/22AS159Ohio State UniversityRPKI Ikke fundet198.30.200.0
- 198.30.228.0/24AS11446Lakeland Community CollegeRPKI Ikke fundet198.30.228.0
- 198.30.229.0/24AS11446Lakeland Community CollegeRPKI Ikke fundet198.30.229.0
- 198.30.230.0/24AS11446Lakeland Community CollegeRPKI Ikke fundet198.30.230.0
- 198.30.237.0/24AS2025University of ToledoRPKI Ikke fundet198.30.237.0
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.