جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
2a0f:6282::/32
دقیقاً اعلامشده
- 2a0f:6282::/32AS7029Windstream Communications LLCRPKI بدون ROA2a0f:6282::
- ثبتکننده
- RIPE NCC · ایالات متحده · ۳۱ فروردین ۱۴۰۱
- بلوک واگذارشده
- 2a0f:6280:: – 2a0f:6287:ffff:ffff:ffff:ffff:ffff:ffff
مسیرهای پوشاننده
هیچ مسیر کلیتری آن را نمیپوشاند.
مسیرهای جزئیتر
- 2a0f:6282::/36AS201279Loginov VladislavRPKI معتبر2a0f:6282::
- 2a0f:6282:1000::/36AS214040RUNNAN WENRPKI معتبر2a0f:6282:1000::
- 2a0f:6282:2108::/47AS211585Maiyun ZhangRPKI معتبر2a0f:6282:2108::
- 2a0f:6282:210a::/48AS211585Maiyun ZhangRPKI معتبر2a0f:6282:210a::
- 2a0f:6282:210b::/48AS211585Maiyun ZhangRPKI معتبر2a0f:6282:210b::
- 2a0f:6282:3000::/36AS200472xiao yuqingRPKI معتبر2a0f:6282:3000::
- 2a0f:6282:4000::/36AS397423Tier.Net Technologies LLCRPKI معتبر2a0f:6282:4000::
- 2a0f:6282:5000::/36AS218805Stacklayer Communications LimitedRPKI معتبر2a0f:6282:5000::
- 2a0f:6282:6000::/36AS212895Johannes ErnstRPKI معتبر2a0f:6282:6000::
- 2a0f:6282:7000::/36AS47272HYEHOST LLCRPKI معتبر2a0f:6282:7000::
- 2a0f:6282:8000::/36AS215108WebDevAE FZERPKI معتبر2a0f:6282:8000::
- 2a0f:6282:9000::/36AS47272HYEHOST LLCRPKI معتبر2a0f:6282:9000::
- 2a0f:6282:a000::/36AS214040RUNNAN WENRPKI معتبر2a0f:6282:a000::
- 2a0f:6282:b000::/36AS203446SMARTNET Germany GmbHRPKI معتبر2a0f:6282:b000::
- 2a0f:6282:c000::/36AS215108WebDevAE FZERPKI معتبر2a0f:6282:c000::
- 2a0f:6282:e000::/36AS214040RUNNAN WENRPKI معتبر2a0f:6282:e000::
- 2a0f:6282:f000::/36AS207083HOSTSLIM OURPKI معتبر2a0f:6282:f000::
این متن هنوز به فارسی در دسترس نیست. تا انتشار ترجمه به انگلیسی نمایش داده میشود.
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.