جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
92.38.0.0/17
دقیقاً اعلامشده
- 92.38.0.0/17AS44546ALFA TELECOM s.r.o.RPKI معتبر92.38.0.0
- ثبتکننده
- RIPE NCC · چک · ۱۲ بهمن ۱۳۸۶
- بلوک واگذارشده
- 92.38.0.0 – 92.38.127.255
مسیرهای پوشاننده
هیچ مسیر کلیتری آن را نمیپوشاند.
مسیرهای جزئیتر
- 92.38.0.0/23AS3205Electron-Service Ltd.RPKI معتبر92.38.0.0
- 92.38.2.0/24AS20688Chudo Telecom Ltd.RPKI معتبر92.38.2.0
- 92.38.3.0/24AS62069Telecommunication Union Ltd.RPKI معتبر92.38.3.0
- 92.38.4.0/24AS209926SkyStream Ltd.RPKI معتبر92.38.4.0
- 92.38.5.0/24AS215237Namangan Kelazhak Kabel Servis MCHJRPKI معتبر92.38.5.0
- 92.38.6.0/24AS62083Fio banka, a.s.RPKI معتبر92.38.6.0
- 92.38.7.0/24AS62083Fio banka, a.s.RPKI معتبر92.38.7.0
- 92.38.8.0/21AS47726INFOBOX MCHJRPKI معتبر92.38.8.0
- 92.38.16.0/22AS43533OOO "Gals Telecom"RPKI معتبر92.38.16.0
- 92.38.20.0/23AS51812KTVS Ltd.RPKI معتبر92.38.20.0
- 92.38.22.0/23AS197520UnionCOM LtdRPKI معتبر92.38.22.0
- 92.38.24.0/22AS43533OOO "Gals Telecom"RPKI معتبر92.38.24.0
- 92.38.28.0/24AS198803Alonstelefonstroy LLPRPKI معتبر92.38.28.0
- 92.38.29.0/24AS198803Alonstelefonstroy LLPRPKI معتبر92.38.29.0
- 92.38.30.0/24AS198803Alonstelefonstroy LLPRPKI معتبر92.38.30.0
- 92.38.31.0/24AS198803Alonstelefonstroy LLPRPKI معتبر92.38.31.0
- 92.38.32.0/24AS62314Atmospherica Ltd.RPKI معتبر92.38.32.0
- 92.38.33.0/24AS61390Garant-G Ltd.RPKI معتبر92.38.33.0
- 92.38.35.0/24AS204416Lukashkin EvgeniiRPKI معتبر92.38.35.0
- 92.38.36.0/24AS62008Cable Systems LtdRPKI معتبر92.38.36.0
- 92.38.37.0/24AS62008Cable Systems LtdRPKI معتبر92.38.37.0
- 92.38.38.0/24AS50245Serverel Inc.RPKI معتبر92.38.38.0
- 92.38.39.0/24AS211433Silver Telecom Ltd.RPKI معتبر92.38.39.0
- 92.38.40.0/24AS199011CSI CJSCRPKI معتبر92.38.40.0
- 92.38.41.0/24AS204584Qnet LLCRPKI معتبر92.38.41.0
- 92.38.42.0/24AS31133PJSC MegaFonRPKI معتبر92.38.42.0
- 92.38.43.0/24AS62006Unecha Television Network Ltd.RPKI معتبر92.38.43.0
- 92.38.44.0/23AS49811Uzlovaya.net LtdRPKI معتبر92.38.44.0
- 92.38.48.0/23AS42447EQU Technologies LLPRPKI معتبر92.38.48.0
- 92.38.50.0/24AS210519ToshTeleQabul MChJRPKI معتبر92.38.50.0
- 92.38.51.0/24AS210519ToshTeleQabul MChJRPKI معتبر92.38.51.0
- 92.38.52.0/22AS43533OOO "Gals Telecom"RPKI معتبر92.38.52.0
- 92.38.56.0/21AS56361Orgtechservice LtdRPKI معتبر92.38.56.0
- 92.38.64.0/21AS42772Unitary enterprise A1RPKI معتبر92.38.64.0
- 92.38.72.0/21AS42772Unitary enterprise A1RPKI معتبر92.38.72.0
- 92.38.80.0/22AS56361Orgtechservice LtdRPKI معتبر92.38.80.0
- 92.38.86.0/24AS197971Inet Telecom Ltd.RPKI معتبر92.38.86.0
- 92.38.87.0/24AS197971Inet Telecom Ltd.RPKI معتبر92.38.87.0
- 92.38.88.0/23AS51812KTVS Ltd.RPKI معتبر92.38.88.0
- 92.38.90.0/23AS51812KTVS Ltd.RPKI معتبر92.38.90.0
- 92.38.92.0/24AS209954Star-Telecom Ltd.RPKI معتبر92.38.92.0
- 92.38.95.0/24AS62314Atmospherica Ltd.RPKI معتبر92.38.95.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.