جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
64.186.224.0/19
دقیقاً اعلامشده
- 64.186.224.0/19AS3257GTT Communications Inc.RPKI بدون ROA64.186.224.0
- ثبتکننده
- ARIN · ایالات متحده · ۱۲ مرداد ۱۳۸۰
- بلوک واگذارشده
- 64.186.224.0 – 64.186.255.255
مسیرهای پوشاننده
هیچ مسیر کلیتری آن را نمیپوشاند.
مسیرهای جزئیتر
- 64.186.224.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.224.0
- 64.186.225.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.225.0
- 64.186.226.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.226.0
- 64.186.227.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.227.0
- 64.186.228.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.228.0
- 64.186.229.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.229.0
- 64.186.230.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.230.0
- 64.186.231.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.231.0
- 64.186.232.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.232.0
- 64.186.233.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.233.0
- 64.186.234.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.234.0
- 64.186.235.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.235.0
- 64.186.236.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.236.0
- 64.186.237.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.237.0
- 64.186.238.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.238.0
- 64.186.239.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.239.0
- 64.186.240.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.240.0
- 64.186.241.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.241.0
- 64.186.242.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.242.0
- 64.186.243.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.243.0
- 64.186.244.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.244.0
- 64.186.245.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.245.0
- 64.186.246.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.246.0
- 64.186.247.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.247.0
- 64.186.248.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.248.0
- 64.186.249.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.249.0
- 64.186.250.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.250.0
- 64.186.251.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.251.0
- 64.186.252.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.252.0
- 64.186.253.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.253.0
- 64.186.254.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.254.0
- 64.186.255.0/24AS906DMIT Cloud ServicesRPKI معتبر64.186.255.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.