البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
1.201.64.0/18
معلنة كما هي
- 1.201.64.0/18AS9286KINXRPKI غير مُغطّى1.201.64.0
- السجل
- APNIC · كوريا الجنوبية · 13/07/2010
- الكتلة المفوَّضة
- 1.201.0.0 – 1.201.255.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 1.201.65.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.65.0
- 1.201.66.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.66.0
- 1.201.67.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.67.0
- 1.201.68.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.68.0
- 1.201.99.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.99.0
- 1.201.109.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.109.0
- 1.201.110.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.110.0
- 1.201.111.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.111.0
- 1.201.112.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.112.0
- 1.201.113.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.113.0
- 1.201.114.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.114.0
- 1.201.115.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.115.0
- 1.201.116.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.116.0
- 1.201.117.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.117.0
- 1.201.118.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.118.0
- 1.201.119.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.119.0
- 1.201.120.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.120.0
- 1.201.121.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.121.0
- 1.201.122.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.122.0
- 1.201.123.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.123.0
- 1.201.124.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.124.0
- 1.201.125.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.125.0
- 1.201.126.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.126.0
- 1.201.127.0/24AS17589GABIA Inc.RPKI غير مُغطّى1.201.127.0
هذا النص غير متوفر بعد باللغة العربية. يُعرض باللغة الإنجليزية إلى أن تُنشر ترجمة.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.
الأسئلة الشائعة
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.