البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
128.75.224.0/19
معلنة كما هي
- 128.75.224.0/19AS3216PJSC "Vimpelcom"RPKI غير مُغطّى128.75.224.0
- السجل
- RIPE NCC · روسيا · 22/11/2011
- الكتلة المفوَّضة
- 128.72.0.0 – 128.75.255.255
المسارات المغطّية
- 128.72.0.0/14AS8402PJSC "Vimpelcom"RPKI غير مُغطّى128.72.0.0
المسارات الأكثر تحديداً
- 128.75.226.0/24AS205084ASK-IT LLCRPKI غير مُغطّى128.75.226.0
- 128.75.230.0/24AS3216PJSC "Vimpelcom"RPKI غير مُغطّى128.75.230.0
- 128.75.231.0/24AS57363CDNvideo LLCRPKI غير مُغطّى128.75.231.0
- 128.75.232.0/24AS3216PJSC "Vimpelcom"RPKI غير مُغطّى128.75.232.0
- 128.75.233.0/24AS204720GLOBAL CLOUD NETWORK LLCRPKI غير مُغطّى128.75.233.0
- 128.75.237.0/24AS3216PJSC "Vimpelcom"RPKI غير مُغطّى128.75.237.0
- 128.75.244.0/22AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.244.0
- 128.75.244.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.244.0
- 128.75.245.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.245.0
- 128.75.246.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.246.0
- 128.75.247.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.247.0
- 128.75.248.0/23AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.248.0
- 128.75.248.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.248.0
- 128.75.249.0/24AS52193EUROCONTACT VELIKY NOVGOROD LLCRPKI غير مُغطّى128.75.249.0
- 128.75.250.0/23AS206171Iridium Communications LLCRPKI غير مُغطّى128.75.250.0
هذا النص غير متوفر بعد باللغة العربية. يُعرض باللغة الإنجليزية إلى أن تُنشر ترجمة.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 128.139.0.0/16. 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.
الأسئلة الشائعة
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.