البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
89.106.0.0/19
معلنة كما هي
- 89.106.0.0/19AS21769Colocation America CorporationRPKI صالح89.106.0.0
- السجل
- RIPE NCC · الولايات المتحدة · 21/03/2006
- الكتلة المفوَّضة
- 89.106.0.0 – 89.106.31.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 89.106.0.0/24AS18526DDPS Networks, LLCRPKI صالح89.106.0.0
- 89.106.1.0/24AS19318Interserver, IncRPKI صالح89.106.1.0
- 89.106.3.0/24AS211440Karolio IT paslaugos, UABRPKI صالح89.106.3.0
- 89.106.4.0/24AS16125UAB "Cherry Servers"RPKI صالح89.106.4.0
- 89.106.5.0/24AS59642UAB "Cherry Servers"RPKI صالح89.106.5.0
- 89.106.6.0/24AS204770UAB "Cherry Servers"RPKI صالح89.106.6.0
- 89.106.7.0/24AS214159UAB "Cherry Servers"RPKI صالح89.106.7.0
- 89.106.8.0/23AS20326TeraSwitch Networks Inc.RPKI صالح89.106.8.0
- 89.106.10.0/23AS20326TeraSwitch Networks Inc.RPKI صالح89.106.10.0
- 89.106.12.0/24AS213896UAB "Cherry Servers"RPKI صالح89.106.12.0
- 89.106.13.0/24AS216444UAB "Cherry Servers"RPKI صالح89.106.13.0
- 89.106.14.0/24AS137409GSL Networks Pty LTDRPKI صالح89.106.14.0
- 89.106.15.0/24AS393942WiredISP Inc.RPKI صالح89.106.15.0
- 89.106.17.0/24AS215724Edgevana, Inc.RPKI صالح89.106.17.0
- 89.106.18.0/24AS18229CtrlSRPKI صالح89.106.18.0
- 89.106.19.0/24AS215724Edgevana, Inc.RPKI صالح89.106.19.0
- 89.106.20.0/24AS215724Edgevana, Inc.RPKI صالح89.106.20.0
- 89.106.21.0/24AS18229CtrlSRPKI صالح89.106.21.0
- 89.106.22.0/24AS137409GSL Networks Pty LTDRPKI صالح89.106.22.0
- 89.106.23.0/24AS21859Zenlayer IncRPKI صالح89.106.23.0
- 89.106.25.0/24AS136744DREAM POWER TECHNOLOGY LIMITEDRPKI صالح89.106.25.0
- 89.106.26.0/24AS397630Blazing SEO, LLCRPKI صالح89.106.26.0
- 89.106.27.0/24AS209336GB Wholesale Networks LTDRPKI صالح89.106.27.0
- 89.106.28.0/24AS200169Manish PantRPKI صالح89.106.28.0
هذا النص غير متوفر بعد باللغة العربية. يُعرض باللغة الإنجليزية إلى أن تُنشر ترجمة.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.0.0/14. 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.