البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
209.26.0.0/16
معلنة كما هي
- 209.26.0.0/16AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.0.0
- السجل
- ARIN · الولايات المتحدة · 24/01/1997
- الكتلة المفوَّضة
- 209.26.0.0 – 209.26.255.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 209.26.0.0/17AS2379CenturyLink Communications, LLCRPKI غير مُغطّى209.26.0.0
- 209.26.3.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.3.0
- 209.26.19.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.19.0
- 209.26.20.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.20.0
- 209.26.23.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.23.0
- 209.26.26.0/23AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.26.0
- 209.26.28.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.28.0
- 209.26.48.0/21AS6364Atlantic.net, Inc.RPKI غير مُغطّى209.26.48.0
- 209.26.59.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.59.0
- 209.26.128.0/17AS2379CenturyLink Communications, LLCRPKI غير مُغطّى209.26.128.0
- 209.26.150.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.150.0
- 209.26.153.0/24AS20367CITY OF ST. CLOUDRPKI غير مُغطّى209.26.153.0
- 209.26.178.0/23AS14467KUA.netRPKI غير مُغطّى209.26.178.0
- 209.26.180.0/23AS14467KUA.netRPKI غير مُغطّى209.26.180.0
- 209.26.182.0/24AS14467KUA.netRPKI غير مُغطّى209.26.182.0
- 209.26.235.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.235.0
- 209.26.236.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.236.0
- 209.26.238.0/24AS2379CenturyLink Communications, LLCRPKI غير مُغطّى209.26.238.0
- 209.26.239.0/24AS2379CenturyLink Communications, LLCRPKI غير مُغطّى209.26.239.0
- 209.26.240.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.240.0
- 209.26.251.0/24AS209CenturyLink Communications, LLCRPKI غير مُغطّى209.26.251.0
- 209.26.253.0/24AS23067Orange County, FloridaRPKI غير مُغطّى209.26.253.0
- 209.26.254.0/24AS23067Orange County, FloridaRPKI غير مُغطّى209.26.254.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.