البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
66.11.64.0/19
معلنة كما هي
- 66.11.64.0/19AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.64.0
- السجل
- ARIN · كندا · 03/05/2002
- الكتلة المفوَّضة
- 66.11.64.0 – 66.11.95.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 66.11.64.0/22AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.64.0
- 66.11.68.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.68.0
- 66.11.69.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.69.0
- 66.11.70.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.70.0
- 66.11.71.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.71.0
- 66.11.72.0/23AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.72.0
- 66.11.74.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.74.0
- 66.11.75.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.75.0
- 66.11.76.0/23AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.76.0
- 66.11.78.0/23AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.78.0
- 66.11.80.0/23AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.80.0
- 66.11.82.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.82.0
- 66.11.83.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.83.0
- 66.11.84.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.84.0
- 66.11.85.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.85.0
- 66.11.86.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.86.0
- 66.11.88.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.88.0
- 66.11.89.0/24AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.89.0
- 66.11.90.0/23AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.90.0
- 66.11.92.0/22AS20161TeraGo Networks Inc.RPKI غير مُغطّى66.11.92.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.