جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
96.31.0.0/19
دقیقاً اعلام‌شده
- 96.31.0.0/19AS53347Premier CommunicationsRPKI معتبر96.31.0.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۲۱ آذر ۱۳۸۷
- بلوک واگذارشده
- 96.31.0.0 – 96.31.31.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 96.31.0.0/24AS53347Premier CommunicationsRPKI معتبر96.31.0.0
- 96.31.2.0/24AS53347Premier CommunicationsRPKI معتبر96.31.2.0
- 96.31.4.0/24AS53347Premier CommunicationsRPKI معتبر96.31.4.0
- 96.31.9.0/24AS53347Premier CommunicationsRPKI معتبر96.31.9.0
- 96.31.11.0/24AS53347Premier CommunicationsRPKI معتبر96.31.11.0
- 96.31.12.0/24AS53347Premier CommunicationsRPKI معتبر96.31.12.0
- 96.31.13.0/24AS53347Premier CommunicationsRPKI معتبر96.31.13.0
- 96.31.14.0/24AS53347Premier CommunicationsRPKI معتبر96.31.14.0
- 96.31.15.0/24AS53347Premier CommunicationsRPKI معتبر96.31.15.0
- 96.31.16.0/24AS53347Premier CommunicationsRPKI معتبر96.31.16.0
- 96.31.17.0/24AS53347Premier CommunicationsRPKI معتبر96.31.17.0
- 96.31.18.0/24AS53347Premier CommunicationsRPKI معتبر96.31.18.0
- 96.31.20.0/24AS53347Premier CommunicationsRPKI معتبر96.31.20.0
- 96.31.21.0/24AS53347Premier CommunicationsRPKI معتبر96.31.21.0
- 96.31.23.0/24AS53347Premier CommunicationsRPKI معتبر96.31.23.0
- 96.31.24.0/24AS53347Premier CommunicationsRPKI معتبر96.31.24.0
- 96.31.25.0/24AS53347Premier CommunicationsRPKI معتبر96.31.25.0
- 96.31.26.0/24AS53347Premier CommunicationsRPKI معتبر96.31.26.0
- 96.31.28.0/23AS53347Premier CommunicationsRPKI معتبر96.31.28.0
- 96.31.30.0/24AS53347Premier CommunicationsRPKI معتبر96.31.30.0
- 96.31.31.0/24AS53347Premier CommunicationsRPKI معتبر96.31.31.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.