BGP-præfiksopslag
Indtast et præfiks (eller en enkelt adresse). Besvares fra vores daglige kopi af den globale routingtabel.
36.64.0.0/16
Annonceret præcist
- 36.64.0.0/16AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.0.0
- Register
- APNIC · Indonesien · 14. jan. 2011
- Tildelt blok
- 36.64.0.0 – 36.95.255.255
Dækkende ruter
Ingen mindre specifik rute dækker det.
Mere specifikke ruter
- 36.64.1.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.1.0
- 36.64.2.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.2.0
- 36.64.15.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.15.0
- 36.64.19.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.19.0
- 36.64.21.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.21.0
- 36.64.31.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.31.0
- 36.64.34.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.34.0
- 36.64.49.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.49.0
- 36.64.51.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.51.0
- 36.64.53.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.53.0
- 36.64.58.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.58.0
- 36.64.61.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.61.0
- 36.64.107.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.107.0
- 36.64.113.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.113.0
- 36.64.122.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.122.0
- 36.64.131.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.131.0
- 36.64.134.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.134.0
- 36.64.135.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.135.0
- 36.64.137.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.137.0
- 36.64.155.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.155.0
- 36.64.156.0/23AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.156.0
- 36.64.164.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.164.0
- 36.64.170.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.170.0
- 36.64.171.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.171.0
- 36.64.176.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.176.0
- 36.64.181.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.181.0
- 36.64.182.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.182.0
- 36.64.185.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.185.0
- 36.64.187.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.187.0
- 36.64.197.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.197.0
- 36.64.199.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.199.0
- 36.64.200.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.200.0
- 36.64.203.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.203.0
- 36.64.207.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.207.0
- 36.64.208.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.208.0
- 36.64.215.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.215.0
- 36.64.239.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.239.0
- 36.64.250.0/24AS7713PT Telekomunikasi IndonesiaRPKI Gyldig36.64.250.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.