جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
2a02:e0:6000::/36
دقیقاً اعلام‌شده
- 2a02:e0:6000::/36AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6000::
- ثبت‌کننده
- RIPE NCC · ترکیه · ۸ اسفند ۱۳۸۶
- بلوک واگذارشده
- 2a02:e0:: – 2a02:e0:ffff:ffff:ffff:ffff:ffff:ffff
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 2a02:e0:6000::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6000::
- 2a02:e0:6100::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6100::
- 2a02:e0:6200::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6200::
- 2a02:e0:6300::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6300::
- 2a02:e0:6400::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6400::
- 2a02:e0:6500::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6500::
- 2a02:e0:6600::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6600::
- 2a02:e0:6700::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6700::
- 2a02:e0:6800::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6800::
- 2a02:e0:6900::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6900::
- 2a02:e0:6a00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6a00::
- 2a02:e0:6b00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6b00::
- 2a02:e0:6c00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6c00::
- 2a02:e0:6d00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6d00::
- 2a02:e0:6e00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6e00::
- 2a02:e0:6f00::/40AS34984Superonline Iletisim Hizmetleri A.S.RPKI معتبر2a02:e0:6f00::
این متن هنوز به فارسی در دسترس نیست. تا انتشار ترجمه به انگلیسی نمایش داده می‌شود.
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.