البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
209.236.192.0/19
معلنة كما هي
- 209.236.192.0/19AS21769Colocation America CorporationRPKI صالح209.236.192.0
- السجل
- ARIN · الولايات المتحدة · 17/09/2025
- الكتلة المفوَّضة
- 209.236.192.0 – 209.236.223.255
المسارات المغطّية
لا يغطيها أي مسار أقل تحديداً.
المسارات الأكثر تحديداً
- 209.236.192.0/24AS47007Colocation America CorporationRPKI صالح209.236.192.0
- 209.236.193.0/24AS47007Colocation America CorporationRPKI صالح209.236.193.0
- 209.236.194.0/24AS47007Colocation America CorporationRPKI صالح209.236.194.0
- 209.236.195.0/24AS47007Colocation America CorporationRPKI صالح209.236.195.0
- 209.236.197.0/24AS60841berrybyte LimitedRPKI صالح209.236.197.0
- 209.236.198.0/23AS53991AcronisRPKI صالح209.236.198.0
- 209.236.200.0/24AS215224NovoServe B.V.RPKI صالح209.236.200.0
- 209.236.203.0/24AS211440Karolio IT paslaugos, UABRPKI صالح209.236.203.0
- 209.236.206.0/24AS214054Nitrode Corporation trading as ChartVPS TechnologiesRPKI صالح209.236.206.0
- 209.236.208.0/24AS16276OVH SASRPKI صالح209.236.208.0
- 209.236.210.0/24AS13335Cloudflare, Inc.RPKI صالح209.236.210.0
- 209.236.211.0/24AS211440Karolio IT paslaugos, UABRPKI صالح209.236.211.0
- 209.236.212.0/24AS402174Shield ITSM, LLCRPKI صالح209.236.212.0
- 209.236.213.0/24AS402174Shield ITSM, LLCRPKI صالح209.236.213.0
- 209.236.214.0/24AS147281Luckynet9 Private LimitedRPKI صالح209.236.214.0
- 209.236.216.0/24AS212238Datacamp LimitedRPKI صالح209.236.216.0
- 209.236.219.0/24AS20473The Constant Company, LLCRPKI صالح209.236.219.0
- 209.236.220.0/24AS20473The Constant Company, LLCRPKI صالح209.236.220.0
- 209.236.221.0/24AS274794Hiper TelecomRPKI صالح209.236.221.0
- 209.236.222.0/24AS211440Karolio IT paslaugos, UABRPKI صالح209.236.222.0
- 209.236.223.0/24AS20473The Constant Company, LLCRPKI صالح209.236.223.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.