جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
2405:3200::/36
دقیقاً اعلام‌شده
- 2405:3200::/36AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200::
- ثبت‌کننده
- APNIC · فیلیپین · ۲۱ آبان ۱۳۸۹
- بلوک واگذارشده
- 2405:3200:: – 2405:3200:ffff:ffff:ffff:ffff:ffff:ffff
مسیرهای پوشاننده
- 2405:3200::/32AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200::
مسیرهای جزئی‌تر
- 2405:3200:101::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:101::
- 2405:3200:107::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:107::
- 2405:3200:108::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:108::
- 2405:3200:112::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:112::
- 2405:3200:140::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:140::
- 2405:3200:141::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:141::
- 2405:3200:142::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:142::
- 2405:3200:150::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:150::
- 2405:3200:151::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:151::
- 2405:3200:152::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:152::
- 2405:3200:501::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:501::
- 2405:3200:506::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:506::
- 2405:3200:50b::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:50b::
- 2405:3200:50c::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:50c::
- 2405:3200:50d::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:50d::
- 2405:3200:50e::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:50e::
- 2405:3200:600::/40AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:600::
- 2405:3200:700::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:700::
- 2405:3200:710::/48AS17639Converge ICT Solutions Inc.RPKI معتبر2405:3200:710::
این متن هنوز به فارسی در دسترس نیست. تا انتشار ترجمه به انگلیسی نمایش داده می‌شود.
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.