البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
41.106.0.0/16
معلنة كما هي
- 41.106.0.0/16AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.0.0
- السجل
- AFRINIC · الجزائر · 04/05/2009
- الكتلة المفوَّضة
- 41.96.0.0 – 41.111.255.255
المسارات المغطّية
- 41.96.0.0/12AS36947Telecom AlgeriaRPKI غير مُغطّى41.96.0.0
المسارات الأكثر تحديداً
- 41.106.0.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.0.0
- 41.106.48.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.48.0
- 41.106.49.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.49.0
- 41.106.50.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.50.0
- 41.106.51.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.51.0
- 41.106.52.0/23AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.52.0
- 41.106.56.0/23AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.56.0
- 41.106.58.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.58.0
- 41.106.61.0/24AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.61.0
- 41.106.62.0/23AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.62.0
- 41.106.64.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.64.0
- 41.106.96.0/20AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.96.0
- 41.106.112.0/20AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.112.0
- 41.106.128.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.128.0
- 41.106.160.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.160.0
- 41.106.192.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.192.0
- 41.106.224.0/19AS36947Telecom AlgeriaRPKI غير مُغطّى41.106.224.0
هذا النص غير متوفر بعد باللغة العربية. يُعرض باللغة الإنجليزية إلى أن تُنشر ترجمة.
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.