البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
64.62.128.0/17
معلنة كما هي
- 64.62.128.0/17AS6939Hurricane Electric LLCRPKI صالح64.62.128.0
- السجل
- ARIN · الولايات المتحدة · 27/08/2002
- الكتلة المفوَّضة
- 64.62.128.0 – 64.62.255.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 64.62.137.0/24AS55262Anthem BroadbandRPKI صالح64.62.137.0
- 64.62.141.0/24AS39499647-2339071RPKI صالح64.62.141.0
- 64.62.149.0/24AS57University of MinnesotaRPKI صالح64.62.149.0
- 64.62.162.0/24AS400779OntarioNetRPKI صالح64.62.162.0
- 64.62.169.0/24AS53813ZSCALER, INC.RPKI صالح64.62.169.0
- 64.62.170.0/24AS397787Black Oak CasinoRPKI صالح64.62.170.0
- 64.62.175.0/24AS15188Menlo, Inc.RPKI صالح64.62.175.0
- 64.62.176.0/24AS36103Central Utah Telephone, Inc.RPKI صالح64.62.176.0
- 64.62.177.0/24AS63141Xactly CorporationRPKI صالح64.62.177.0
- 64.62.189.0/24AS54288SolidTools Technology, Inc.RPKI صالح64.62.189.0
- 64.62.190.0/24AS27424Lucky Friday Labs, LLCRPKI صالح64.62.190.0
- 64.62.191.0/24AS54288SolidTools Technology, Inc.RPKI صالح64.62.191.0
- 64.62.192.0/24AS401725Open Infra Inc.RPKI صالح64.62.192.0
- 64.62.196.0/24AS54288SolidTools Technology, Inc.RPKI صالح64.62.196.0
- 64.62.201.0/24AS394993Santa Clara Valley Transportation AuthorityRPKI صالح64.62.201.0
- 64.62.209.0/24AS54288SolidTools Technology, Inc.RPKI صالح64.62.209.0
- 64.62.224.0/24AS27424Lucky Friday Labs, LLCRPKI صالح64.62.224.0
- 64.62.226.0/24AS14277GiGstreemRPKI صالح64.62.226.0
- 64.62.228.0/24AS401530Retail Solutions, LLCRPKI صالح64.62.228.0
- 64.62.231.0/24AS401256WK Kellogg Business Services LLCRPKI صالح64.62.231.0
- 64.62.238.0/24AS394330LTD Broadband LLCRPKI صالح64.62.238.0
- 64.62.253.0/24AS54288SolidTools Technology, Inc.RPKI صالح64.62.253.0
- 64.62.255.0/24AS39499647-2339071RPKI صالح64.62.255.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.