جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
2604:200::/32
دقیقاً اعلام‌شده
- 2604:200::/32AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200::
- ثبت‌کننده
- ARIN · ایالات متحده · ۲۷ مهر ۱۳۸۹
- بلوک واگذارشده
- 2604:200:: – 2604:200:ffff:ffff:ffff:ffff:ffff:ffff
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 2604:200:4::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:4::
- 2604:200:6::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:6::
- 2604:200:8::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:8::
- 2604:200:9::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:9::
- 2604:200:a::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:a::
- 2604:200:b::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:b::
- 2604:200:c::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:c::
- 2604:200:d::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:d::
- 2604:200:e::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:e::
- 2604:200:f::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:f::
- 2604:200:11::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:11::
- 2604:200:13::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:13::
- 2604:200:17::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:17::
- 2604:200:18::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:18::
- 2604:200:19::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:19::
- 2604:200:1a::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:1a::
- 2604:200:1d::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:1d::
- 2604:200:1e::/48AS33132Crown Castle Fiber LLCRPKI بدون ROA2604:200:1e::
- 2604:200:1f::/48AS46887Crown Castle Fiber LLCRPKI بدون ROA2604:200:1f::
- 2604:200:1500::/48AS46887Crown Castle Fiber LLCRPKI بدون ROA2604:200:1500::
این متن هنوز به فارسی در دسترس نیست. تا انتشار ترجمه به انگلیسی نمایش داده می‌شود.
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.