البحث عن بادئة BGP
أدخل بادئة (أو عنواناً واحداً). يُجاب من نسختنا اليومية من جدول التوجيه العالمي.
46.61.128.0/17
معلنة كما هي
- 46.61.128.0/17AS12389PJSC RostelecomRPKI صالح46.61.128.0
- السجل
- RIPE NCC · روسيا · 27/10/2010
- الكتلة المفوَّضة
- 46.61.128.0 – 46.61.255.255
المسارات المغطّية
- 46.61.0.0/16AS12389PJSC RostelecomRPKI صالح46.61.0.0
المسارات الأكثر تحديداً
- 46.61.131.0/24AS12389PJSC RostelecomRPKI صالح46.61.131.0
- 46.61.137.0/24AS21403RTK-SERVICE LLCRPKI صالح46.61.137.0
- 46.61.149.0/24AS12389PJSC RostelecomRPKI صالح46.61.149.0
- 46.61.150.0/24AS201776Miranda-Media LtdRPKI صالح46.61.150.0
- 46.61.163.0/24AS12389PJSC RostelecomRPKI صالح46.61.163.0
- 46.61.179.0/24AS12389PJSC RostelecomRPKI صالح46.61.179.0
- 46.61.181.0/24AS212732JSC TsNIIMashRPKI صالح46.61.181.0
- 46.61.184.0/24AS205576JSC FC Spartak-MoscowRPKI صالح46.61.184.0
- 46.61.193.0/24AS12389PJSC RostelecomRPKI صالح46.61.193.0
- 46.61.197.0/24AS12389PJSC RostelecomRPKI صالح46.61.197.0
- 46.61.198.0/24AS12389PJSC RostelecomRPKI صالح46.61.198.0
- 46.61.205.0/24AS12389PJSC RostelecomRPKI صالح46.61.205.0
- 46.61.208.0/24AS12389PJSC RostelecomRPKI صالح46.61.208.0
- 46.61.209.0/24AS205060Departament Smolenskoy oblasti po Informatsionnym tekhnologiyamRPKI صالح46.61.209.0
- 46.61.230.0/24AS12389PJSC RostelecomRPKI صالح46.61.230.0
- 46.61.231.0/24AS12389PJSC RostelecomRPKI صالح46.61.231.0
- 46.61.232.0/24AS12389PJSC RostelecomRPKI صالح46.61.232.0
- 46.61.234.0/24AS12389PJSC RostelecomRPKI صالح46.61.234.0
- 46.61.237.0/24AS12389PJSC RostelecomRPKI صالح46.61.237.0
- 46.61.239.0/24AS12389PJSC RostelecomRPKI صالح46.61.239.0
- 46.61.245.0/24AS201776Miranda-Media LtdRPKI صالح46.61.245.0
- 46.61.247.0/24AS12389PJSC RostelecomRPKI صالح46.61.247.0
- 46.61.248.0/24AS12389PJSC RostelecomRPKI صالح46.61.248.0
- 46.61.251.0/24AS12389PJSC RostelecomRPKI صالح46.61.251.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.