جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
65.172.0.0/15
دقیقاً اعلامشده
- 65.172.0.0/15AS174Cogent Communications, LLCRPKI بدون ROA65.172.0.0
- ثبتکننده
- ARIN · ایالات متحده · ۲۹ شهریور ۱۳۷۹
- بلوک واگذارشده
- 65.172.0.0 – 65.173.255.255
مسیرهای پوشاننده
هیچ مسیر کلیتری آن را نمیپوشاند.
مسیرهای جزئیتر
- 65.172.24.0/22AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.24.0
- 65.172.24.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.24.0
- 65.172.24.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.24.0
- 65.172.25.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.25.0
- 65.172.26.0/23AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.26.0
- 65.172.26.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.26.0
- 65.172.27.0/24AS14813Columbus Telecommunications (Barbados) LimitedRPKI بدون ROA65.172.27.0
- 65.172.54.0/24AS1647Interop TechnologiesRPKI بدون ROA65.172.54.0
- 65.172.71.0/24AS174Cogent Communications, LLCRPKI بدون ROA65.172.71.0
- 65.172.72.0/23AS18632Volcano Vision, Inc.RPKI بدون ROA65.172.72.0
- 65.172.132.0/24AS174Cogent Communications, LLCRPKI بدون ROA65.172.132.0
- 65.172.240.0/24AS15065Slic Network Solutions, IncRPKI بدون ROA65.172.240.0
- 65.172.241.0/24AS15065Slic Network Solutions, IncRPKI بدون ROA65.172.241.0
- 65.172.242.0/24AS15065Slic Network Solutions, IncRPKI بدون ROA65.172.242.0
- 65.172.243.0/24AS15065Slic Network Solutions, IncRPKI بدون ROA65.172.243.0
- 65.172.244.0/22AS18435The Junction Internet, LLCRPKI بدون ROA65.172.244.0
- 65.172.244.0/24AS18435The Junction Internet, LLCRPKI بدون ROA65.172.244.0
- 65.172.245.0/24AS18435The Junction Internet, LLCRPKI بدون ROA65.172.245.0
- 65.172.246.0/24AS18435The Junction Internet, LLCRPKI بدون ROA65.172.246.0
- 65.172.247.0/24AS18435The Junction Internet, LLCRPKI بدون ROA65.172.247.0
- 65.173.64.0/22AS11398CenturyLink Communications, LLCRPKI بدون ROA65.173.64.0
- 65.173.76.0/24AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.76.0
- 65.173.78.0/24AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.78.0
- 65.173.79.0/24AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.79.0
- 65.173.82.0/23AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.82.0
- 65.173.82.0/24AS19901BrightspeedRPKI بدون ROA65.173.82.0
- 65.173.84.0/23AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.84.0
- 65.173.86.0/23AS11398CenturyLink Communications, LLCRPKI بدون ROA65.173.86.0
- 65.173.86.0/24AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.86.0
- 65.173.88.0/23AS11398CenturyLink Communications, LLCRPKI بدون ROA65.173.88.0
- 65.173.90.0/24AS209CenturyLink Communications, LLCRPKI بدون ROA65.173.90.0
- 65.173.92.0/22AS19901BrightspeedRPKI بدون ROA65.173.92.0
- 65.173.93.0/24AS19901BrightspeedRPKI بدون ROA65.173.93.0
- 65.173.94.0/24AS19901BrightspeedRPKI بدون ROA65.173.94.0
- 65.173.160.0/19AS4637Telstra GlobalRPKI بدون ROA65.173.160.0
- 65.173.245.0/24AS21582Northern Arizona UniversityRPKI بدون ROA65.173.245.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.