جست‌وجوی پیشوند BGP
یک پیشوند (یا یک نشانی) وارد کنید. از نسخهٔ روزانهٔ ما از جدول جهانی مسیریابی پاسخ داده می‌شود.
80.231.0.0/16
دقیقاً اعلام‌شده
- 80.231.0.0/16AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.0.0
- ثبت‌کننده
- RIPE NCC · کانادا · ۲۹ اسفند ۱۳۸۰
- بلوک واگذارشده
- 80.231.0.0 – 80.231.255.255
مسیرهای پوشاننده
هیچ مسیر کلی‌تری آن را نمی‌پوشاند.
مسیرهای جزئی‌تر
- 80.231.8.0/21AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.8.0
- 80.231.9.0/24AS12670Completel SASRPKI معتبر80.231.9.0
- 80.231.11.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.11.0
- 80.231.16.0/23AS40009BitGravity, Inc.RPKI معتبر80.231.16.0
- 80.231.53.0/24AS6774Belgacom International Carrier Services SARPKI معتبر80.231.53.0
- 80.231.56.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.56.0
- 80.231.71.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.71.0
- 80.231.93.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.93.0
- 80.231.94.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.94.0
- 80.231.136.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.136.0
- 80.231.155.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.155.0
- 80.231.162.0/23AS40009BitGravity, Inc.RPKI معتبر80.231.162.0
- 80.231.162.0/24AS40009BitGravity, Inc.RPKI معتبر80.231.162.0
- 80.231.163.0/24AS40009BitGravity, Inc.RPKI معتبر80.231.163.0
- 80.231.213.0/24AS8529Zain Omantel International FZ-LLCRPKI معتبر80.231.213.0
- 80.231.218.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.218.0
- 80.231.235.0/24AS6453TATA COMMUNICATIONS (AMERICA) INCRPKI معتبر80.231.235.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.