البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
209.67.0.0/16
معلنة كما هي
- 209.67.0.0/16AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.0.0
- السجل
- ARIN · الولايات المتحدة · 11/04/1997
- الكتلة المفوَّضة
- 209.67.0.0 – 209.67.255.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 209.67.64.0/18AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.64.0
- 209.67.128.0/18AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.128.0
- 209.67.128.0/24AS26254Mail2world INC.RPKI غير مُغطّى209.67.128.0
- 209.67.129.0/24AS26254Mail2world INC.RPKI غير مُغطّى209.67.129.0
- 209.67.131.0/24AS40422Paciolan, LLCRPKI غير مُغطّى209.67.131.0
- 209.67.132.0/22AS203Level 3 Parent, LLCRPKI غير مُغطّى209.67.132.0
- 209.67.136.0/22AS203Level 3 Parent, LLCRPKI غير مُغطّى209.67.136.0
- 209.67.140.0/24AS40422Paciolan, LLCRPKI غير مُغطّى209.67.140.0
- 209.67.166.0/24AS397691CompuGroup Medical Inc.RPKI غير مُغطّى209.67.166.0
- 209.67.176.0/24AS64212Advantage Sales & Marketing LLCRPKI غير مُغطّى209.67.176.0
- 209.67.188.0/24AS14415Host Collective, Inc.RPKI غير مُغطّى209.67.188.0
- 209.67.192.0/21AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.192.0
- 209.67.208.0/20AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.208.0
- 209.67.208.0/24AS13993MotiveRPKI غير مُغطّى209.67.208.0
- 209.67.219.0/24AS16641ACBB-BITS, LLCRPKI غير مُغطّى209.67.219.0
- 209.67.224.0/19AS3561CenturyLink Communications, LLCRPKI غير مُغطّى209.67.224.0
- 209.67.228.0/23AS8739ICDSoft Ltd.RPKI غير مُغطّى209.67.228.0
- 209.67.236.0/22AS8739ICDSoft Ltd.RPKI غير مُغطّى209.67.236.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.