جستوجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده میشود.
205.198.48.0/20
دقیقاً اعلامشده
- 205.198.48.0/20AS133613MTel telecommunication company ltd.RPKI معتبر205.198.48.0
- ثبتکننده
- ARIN · ایالات متحده · ۱۰ فروردین ۱۳۷۴
- بلوک واگذارشده
- 205.198.0.0 – 205.199.255.255
مسیرهای پوشاننده
- 205.198.0.0/15AS174Cogent Communications, LLCRPKI بدون ROA205.198.0.0
مسیرهای جزئیتر
- 205.198.48.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.48.0
- 205.198.49.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.49.0
- 205.198.50.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.50.0
- 205.198.51.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.51.0
- 205.198.52.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.52.0
- 205.198.53.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.53.0
- 205.198.54.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.54.0
- 205.198.55.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.55.0
- 205.198.56.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.56.0
- 205.198.57.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.57.0
- 205.198.58.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.58.0
- 205.198.59.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.59.0
- 205.198.60.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.60.0
- 205.198.61.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.61.0
- 205.198.62.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.62.0
- 205.198.63.0/24AS133613MTel telecommunication company ltd.RPKI معتبر205.198.63.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.