جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
209.236.192.0/19
دقیقاً اعلام‌شده
- 209.236.192.0/19AS21769Colocation America CorporationRPKI معتبر209.236.192.0
- ثبت‌کننده
- ARIN · ایالات متحده · ۲۶ شهریور ۱۴۰۴
- بلوک واگذارشده
- 209.236.192.0 – 209.236.223.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 209.236.192.0/24AS47007Colocation America CorporationRPKI معتبر209.236.192.0
- 209.236.193.0/24AS47007Colocation America CorporationRPKI معتبر209.236.193.0
- 209.236.194.0/24AS47007Colocation America CorporationRPKI معتبر209.236.194.0
- 209.236.195.0/24AS47007Colocation America CorporationRPKI معتبر209.236.195.0
- 209.236.197.0/24AS60841berrybyte LimitedRPKI معتبر209.236.197.0
- 209.236.198.0/23AS53991AcronisRPKI معتبر209.236.198.0
- 209.236.200.0/24AS215224NovoServe B.V.RPKI معتبر209.236.200.0
- 209.236.203.0/24AS211440Karolio IT paslaugos, UABRPKI معتبر209.236.203.0
- 209.236.206.0/24AS214054Nitrode Corporation trading as ChartVPS TechnologiesRPKI معتبر209.236.206.0
- 209.236.208.0/24AS16276OVH SASRPKI معتبر209.236.208.0
- 209.236.210.0/24AS13335Cloudflare, Inc.RPKI معتبر209.236.210.0
- 209.236.211.0/24AS211440Karolio IT paslaugos, UABRPKI معتبر209.236.211.0
- 209.236.212.0/24AS402174Shield ITSM, LLCRPKI معتبر209.236.212.0
- 209.236.213.0/24AS402174Shield ITSM, LLCRPKI معتبر209.236.213.0
- 209.236.214.0/24AS147281Luckynet9 Private LimitedRPKI معتبر209.236.214.0
- 209.236.216.0/24AS212238Datacamp LimitedRPKI معتبر209.236.216.0
- 209.236.219.0/24AS20473The Constant Company, LLCRPKI معتبر209.236.219.0
- 209.236.220.0/24AS20473The Constant Company, LLCRPKI معتبر209.236.220.0
- 209.236.221.0/24AS274794Hiper TelecomRPKI معتبر209.236.221.0
- 209.236.222.0/24AS211440Karolio IT paslaugos, UABRPKI معتبر209.236.222.0
- 209.236.223.0/24AS20473The Constant Company, LLCRPKI معتبر209.236.223.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.