جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
216.84.0.0/15
دقیقاً اعلام‌شده
- 216.84.0.0/15AS3549Level 3 Parent, LLCRPKI بدون ROA216.84.0.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۲ مهر ۱۳۷۷
- بلوک واگذارشده
- 216.84.0.0 – 216.85.255.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 216.84.89.0/24AS32297Tucson Electric PowerRPKI بدون ROA216.84.89.0
- 216.84.141.0/24AS26831Cameron Communications, LLCRPKI بدون ROA216.84.141.0
- 216.84.142.0/24AS26831Cameron Communications, LLCRPKI بدون ROA216.84.142.0
- 216.84.143.0/24AS26831Cameron Communications, LLCRPKI بدون ROA216.84.143.0
- 216.84.156.0/24AS18662AflacRPKI بدون ROA216.84.156.0
- 216.84.165.0/24AS393538Alliance Coal, LLCRPKI بدون ROA216.84.165.0
- 216.84.188.0/24AS36180Cisco IoTRPKI بدون ROA216.84.188.0
- 216.84.198.0/24AS23357UNASSIGNEDRPKI بدون ROA216.84.198.0
- 216.84.199.0/24AS23357UNASSIGNEDRPKI بدون ROA216.84.199.0
- 216.84.200.0/21AS25649AYERA TECHNOLOGIES, INC.RPKI بدون ROA216.84.200.0
- 216.84.208.0/21AS25649AYERA TECHNOLOGIES, INC.RPKI بدون ROA216.84.208.0
- 216.84.222.0/23AS3356Level 3 Parent, LLCRPKI بدون ROA216.84.222.0
- 216.84.224.0/21AS62712State of HawaiiRPKI بدون ROA216.84.224.0
- 216.84.232.0/23AS62712State of HawaiiRPKI بدون ROA216.84.232.0
- 216.84.240.0/20AS33302Data102RPKI بدون ROA216.84.240.0
- 216.85.81.0/24AS33489Comcast Cable Communications, LLCRPKI بدون ROA216.85.81.0
- 216.85.85.0/24AS33623Hayneville Telephone CompanyRPKI بدون ROA216.85.85.0
- 216.85.115.0/24AS40139Jackson Technical LLCRPKI بدون ROA216.85.115.0
- 216.85.142.0/23AS40139Jackson Technical LLCRPKI بدون ROA216.85.142.0
- 216.85.168.0/24AS3356Level 3 Parent, LLCRPKI بدون ROA216.85.168.0
- 216.85.174.0/24AS393478Herbalife International of America, Inc.RPKI بدون ROA216.85.174.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.