BGP प्रीफ़िक्स लुकअप
एक प्रीफ़िक्स (या एकल पता) दर्ज करें। वैश्विक रूटिंग टेबल की हमारी दैनिक प्रति से उत्तर।
80.91.64.0/19
ठीक इसी रूप में घोषित
- 80.91.64.0/19AS174Cogent Communications, LLCRPKI नहीं मिला80.91.64.0
- रजिस्ट्री
- RIPE NCC · संयुक्त राज्य · 11 सित॰ 2001
- आवंटित ब्लॉक
- 80.91.64.0 – 80.91.79.255
कवर करने वाले रूट
कोई कम-विशिष्ट रूट इसे कवर नहीं करता।
अधिक-विशिष्ट रूट
- 80.91.65.0/24AS203919LUMADOCK LTDRPKI मान्य80.91.65.0
- 80.91.66.0/24AS211348FERCA TECNOLOGIES SLRPKI नहीं मिला80.91.66.0
- 80.91.70.0/24AS210423ATUAXANELA, S.L.RPKI नहीं मिला80.91.70.0
- 80.91.71.0/24AS214382Bulent Aydin trading as HostlayiciRPKI मान्य80.91.71.0
- 80.91.72.0/24AS210395INTERNET MANTENIMIENTOS SLRPKI नहीं मिला80.91.72.0
- 80.91.73.0/24AS204805Voiped Wholesale BVRPKI नहीं मिला80.91.73.0
- 80.91.75.0/24AS205827ConectaT Servicios de Banda Ancha SLRPKI नहीं मिला80.91.75.0
- 80.91.79.0/24AS203919LUMADOCK LTDRPKI मान्य80.91.79.0
- 80.91.81.0/24AS174Cogent Communications, LLCRPKI मान्य80.91.81.0
- 80.91.84.0/23AS208905Exelera Telecom LtdRPKI मान्य80.91.84.0
- 80.91.86.0/24AS203919LUMADOCK LTDRPKI मान्य80.91.86.0
- 80.91.87.0/24AS33480Web WerksRPKI नहीं मिला80.91.87.0
- 80.91.88.0/24AS203919LUMADOCK LTDRPKI मान्य80.91.88.0
- 80.91.89.0/24AS47600RUBIX DATACENTER SASRPKI मान्य80.91.89.0
- 80.91.90.0/24AS210423ATUAXANELA, S.L.RPKI नहीं मिला80.91.90.0
- 80.91.92.0/24AS206119Veganet Teknolojileri ve Hizmetleri LTD STIRPKI मान्य80.91.92.0
- 80.91.93.0/24AS206119Veganet Teknolojileri ve Hizmetleri LTD STIRPKI मान्य80.91.93.0
- 80.91.94.0/24AS206119Veganet Teknolojileri ve Hizmetleri LTD STIRPKI मान्य80.91.94.0
- 80.91.95.0/24AS206119Veganet Teknolojileri ve Hizmetleri LTD STIRPKI मान्य80.91.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, 2.48.0.0/14. 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.