BGP प्रीफ़िक्स लुकअप
एक प्रीफ़िक्स (या एकल पता) दर्ज करें। वैश्विक रूटिंग टेबल की हमारी दैनिक प्रति से उत्तर।
2405:c0::/32
ठीक इसी रूप में घोषित
- 2405:c0::/32AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0::
- रजिस्ट्री
- APNIC · इंडोनेशिया · 3 जुल॰ 2019
- आवंटित ब्लॉक
- 2405:c0:: – 2405:c0:ffff:ffff:ffff:ffff:ffff:ffff
कवर करने वाले रूट
कोई कम-विशिष्ट रूट इसे कवर नहीं करता।
अधिक-विशिष्ट रूट
- 2405:c0:10::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:10::
- 2405:c0:20::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:20::
- 2405:c0:30::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:30::
- 2405:c0:40::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:40::
- 2405:c0:50::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:50::
- 2405:c0:60::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:60::
- 2405:c0:70::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:70::
- 2405:c0:80::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:80::
- 2405:c0:90::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:90::
- 2405:c0:d1::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d1::
- 2405:c0:d2::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d2::
- 2405:c0:1000::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:1000::
- 2405:c0:1001::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:1001::
- 2405:c0:1100::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:1100::
- 2405:c0:d100::/40AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d100::
- 2405:c0:d200::/40AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d200::
- 2405:c0:d400::/40AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d400::
- 2405:c0:d500::/40AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d500::
- 2405:c0:d600::/40AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:d600::
- 2405:c0:dead::/48AS138881PT INDONESIA TRANS NETWORKRPKI मान्य2405:c0:dead::
यह पाठ अभी हिन्दी में उपलब्ध नहीं है। अनुवाद प्रकाशित होने तक इसे अंग्रेज़ी में दिखाया जाता है।
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.