جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
207.12.0.0/14
دقیقاً اعلام‌شده
- 207.12.0.0/14AS174Cogent Communications, LLCRPKI بدون ROA207.12.0.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۲۹ آذر ۱۳۷۴
- بلوک واگذارشده
- 207.12.0.0 – 207.15.255.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 207.12.88.0/21AS11403NYIRPKI بدون ROA207.12.88.0
- 207.12.168.0/21AS14174North Central Kansas Community Network Co.RPKI بدون ROA207.12.168.0
- 207.12.168.0/22AS14174North Central Kansas Community Network Co.RPKI بدون ROA207.12.168.0
- 207.13.72.0/24AS174Cogent Communications, LLCRPKI بدون ROA207.13.72.0
- 207.14.29.0/24AS394945Expeditors International of Wa Inc.RPKI بدون ROA207.14.29.0
- 207.14.32.0/24AS13871Telebyte NWRPKI بدون ROA207.14.32.0
- 207.14.33.0/24AS13871Telebyte NWRPKI بدون ROA207.14.33.0
- 207.14.34.0/24AS18530Isomedia, Inc.RPKI بدون ROA207.14.34.0
- 207.14.35.0/24AS19133Bird Hosting Inc.RPKI بدون ROA207.14.35.0
- 207.14.36.0/24AS13871Telebyte NWRPKI بدون ROA207.14.36.0
- 207.14.37.0/24AS13871Telebyte NWRPKI بدون ROA207.14.37.0
- 207.14.38.0/24AS13871Telebyte NWRPKI بدون ROA207.14.38.0
- 207.14.39.0/24AS13871Telebyte NWRPKI بدون ROA207.14.39.0
- 207.14.188.0/22AS6222CenturyLink Communications, LLCRPKI بدون ROA207.14.188.0
- 207.14.236.0/23AS209CenturyLink Communications, LLCRPKI بدون ROA207.14.236.0
- 207.15.6.0/24AS174Cogent Communications, LLCRPKI بدون ROA207.15.6.0
- 207.15.10.0/24AS11463Kindred Healthcare, Inc.RPKI بدون ROA207.15.10.0
- 207.15.64.0/19AS4637Telstra GlobalRPKI بدون ROA207.15.64.0
- 207.15.96.0/19AS4637Telstra GlobalRPKI بدون ROA207.15.96.0
- 207.15.198.0/24AS14979Aeronet WirelessRPKI بدون ROA207.15.198.0
- 207.15.224.0/20AS7459Grande Communications Networks, LLCRPKI بدون ROA207.15.224.0
- 207.15.240.0/20AS7459Grande Communications Networks, LLCRPKI بدون ROA207.15.240.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.