جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
64.152.0.0/13
دقیقاً اعلامشده
- 64.152.0.0/13AS3356Level 3 Parent, LLCRPKI بدون ROA64.152.0.0
- ثبتکننده
- ARIN · ایالات متحده · ۱۹ خرداد ۱۳۷۹
- بلوک واگذارشده
- 64.152.0.0 – 64.159.255.255
مسیرهای پوشاننده
هیچ مسیر کلیتری آن را نمیپوشاند.
مسیرهای جزئیتر
- 64.154.4.0/22AS20454SECURED SERVERS LLCRPKI بدون ROA64.154.4.0
- 64.154.18.0/24AS32208SKL Services IncRPKI بدون ROA64.154.18.0
- 64.154.20.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA64.154.20.0
- 64.154.21.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA64.154.21.0
- 64.154.22.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA64.154.22.0
- 64.154.23.0/24AS14127Iland Internet Solutions CorporationRPKI بدون ROA64.154.23.0
- 64.154.41.0/24AS46714IP Communications LLCRPKI بدون ROA64.154.41.0
- 64.154.88.0/22AS40866San Diego BroadbandRPKI بدون ROA64.154.88.0
- 64.156.56.0/24AS62CyrusOne LLCRPKI بدون ROA64.156.56.0
- 64.156.167.0/24AS25751Conversant, Inc.RPKI بدون ROA64.156.167.0
- 64.157.123.0/24AS33693TierPoint, LLCRPKI بدون ROA64.157.123.0
- 64.157.238.0/24AS20053The Descartes Systems Group IncRPKI بدون ROA64.157.238.0
- 64.158.44.0/24AS32208SKL Services IncRPKI بدون ROA64.158.44.0
- 64.158.152.0/24AS33099DTS FiberRPKI بدون ROA64.158.152.0
- 64.158.153.0/24AS33099DTS FiberRPKI بدون ROA64.158.153.0
- 64.158.201.0/24AS26842MFXCHANGE US, INCRPKI معتبر64.158.201.0
- 64.158.223.0/24AS41041Conversant LLCRPKI بدون ROA64.158.223.0
- 64.159.123.0/24AS18848Altec Industries, Inc.RPKI بدون ROA64.159.123.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.