BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
77.43.128.0/17
Annonceret præcist
- 77.43.128.0/17AS8359MTS PJSCRPKI Ikke fundet77.43.128.0
- Register
- RIPE NCC · Rusland · 8. dec. 2006
- Tildelt blok
- 77.43.128.0 – 77.43.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 77.43.128.0/21AS15640MTS PJSCRPKI Ikke fundet77.43.128.0
- 77.43.131.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.131.0
- 77.43.133.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.133.0
- 77.43.134.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.134.0
- 77.43.136.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.136.0
- 77.43.137.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.137.0
- 77.43.140.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.140.0
- 77.43.144.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.144.0
- 77.43.148.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.148.0
- 77.43.148.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.148.0
- 77.43.150.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.150.0
- 77.43.151.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.151.0
- 77.43.152.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.152.0
- 77.43.152.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.152.0
- 77.43.153.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.153.0
- 77.43.154.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.154.0
- 77.43.155.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.155.0
- 77.43.156.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.156.0
- 77.43.157.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.157.0
- 77.43.159.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.159.0
- 77.43.160.0/19AS15640MTS PJSCRPKI Ikke fundet77.43.160.0
- 77.43.160.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.160.0
- 77.43.163.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.163.0
- 77.43.168.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.168.0
- 77.43.170.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.170.0
- 77.43.171.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.171.0
- 77.43.172.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.172.0
- 77.43.173.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.173.0
- 77.43.174.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.174.0
- 77.43.176.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.176.0
- 77.43.179.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.179.0
- 77.43.180.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.180.0
- 77.43.181.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.181.0
- 77.43.192.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.192.0
- 77.43.196.0/22AS15640MTS PJSCRPKI Ikke fundet77.43.196.0
- 77.43.200.0/21AS15640MTS PJSCRPKI Ikke fundet77.43.200.0
- 77.43.207.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.207.0
- 77.43.208.0/20AS15640MTS PJSCRPKI Ikke fundet77.43.208.0
- 77.43.208.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.208.0
- 77.43.209.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.209.0
- 77.43.210.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.210.0
- 77.43.224.0/19AS15640MTS PJSCRPKI Ikke fundet77.43.224.0
- 77.43.237.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.237.0
- 77.43.238.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.238.0
- 77.43.239.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.239.0
- 77.43.240.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.240.0
- 77.43.241.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.241.0
- 77.43.242.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.242.0
- 77.43.244.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.244.0
- 77.43.245.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.245.0
- 77.43.246.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.246.0
- 77.43.247.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.247.0
- 77.43.248.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.248.0
- 77.43.249.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.249.0
- 77.43.250.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.250.0
- 77.43.251.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.251.0
- 77.43.252.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.252.0
- 77.43.253.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.253.0
- 77.43.254.0/24AS15640MTS PJSCRPKI Ikke fundet77.43.254.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.