البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
210.3.0.0/18
معلنة كما هي
- 210.3.0.0/18AS9304HGC Global Communications LimitedRPKI صالح210.3.0.0
- السجل
- APNIC · هونغ كونغ الصينية (منطقة إدارية خاصة) · 06/06/2001
- الكتلة المفوَّضة
- 210.3.0.0 – 210.3.127.255
المسارات المغطّية
- 210.3.0.0/16AS9304HGC Global Communications LimitedRPKI صالح210.3.0.0
المسارات الأكثر تحديداً
- 210.3.0.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.0.0
- 210.3.4.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.4.0
- 210.3.6.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.6.0
- 210.3.8.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.8.0
- 210.3.12.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.12.0
- 210.3.16.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.16.0
- 210.3.21.0/24AS140881HGC Global Communications LimitedRPKI صالح210.3.21.0
- 210.3.24.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.24.0
- 210.3.28.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.28.0
- 210.3.32.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.32.0
- 210.3.36.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.36.0
- 210.3.38.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.38.0
- 210.3.40.0/23AS9304HGC Global Communications LimitedRPKI صالح210.3.40.0
- 210.3.42.0/24AS9304HGC Global Communications LimitedRPKI صالح210.3.42.0
- 210.3.43.0/24AS9304HGC Global Communications LimitedRPKI صالح210.3.43.0
- 210.3.48.0/21AS9304HGC Global Communications LimitedRPKI صالح210.3.48.0
- 210.3.56.0/22AS9304HGC Global Communications LimitedRPKI صالح210.3.56.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.