البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
2001:4430:6000::/36
معلنة كما هي
- 2001:4430:6000::/36AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6000::
- السجل
- APNIC · كوريا الجنوبية · 06/07/2005
- الكتلة المفوَّضة
- 2001:4430:: – 2001:4430:ffff:ffff:ffff:ffff:ffff:ffff
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 2001:4430:6000::/37AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6000::
- 2001:4430:6000::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6000::
- 2001:4430:6010::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6010::
- 2001:4430:6020::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6020::
- 2001:4430:6030::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6030::
- 2001:4430:6040::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6040::
- 2001:4430:6050::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6050::
- 2001:4430:6060::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6060::
- 2001:4430:6070::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6070::
- 2001:4430:6080::/44AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6080::
- 2001:4430:6800::/37AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6800::
- 2001:4430:6800::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6800::
- 2001:4430:6808::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6808::
- 2001:4430:6810::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6810::
- 2001:4430:6818::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6818::
- 2001:4430:6820::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6820::
- 2001:4430:6828::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6828::
- 2001:4430:6830::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6830::
- 2001:4430:6838::/45AS17853LGTELECOMRPKI غير مُغطّى2001:4430:6838::
هذا النص غير متوفر بعد باللغة العربية. يُعرض باللغة الإنجليزية إلى أن تُنشر ترجمة.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.