BGP प्रीफ़िक्स लुकअप
एक प्रीफ़िक्स (या एकल पता) दर्ज करें। वैश्विक रूटिंग टेबल की हमारी दैनिक प्रति से उत्तर।
2a13:aac0::/29
ठीक इसी रूप में घोषित
- 2a13:aac0::/29AS60539Huicast Telecom LimitedRPKI नहीं मिला2a13:aac0::
- रजिस्ट्री
- RIPE NCC · हाँग काँग (चीन विशेष प्रशासनिक क्षेत्र) · 14 अग॰ 2023
- आवंटित ब्लॉक
- 2a13:aac0:: – 2a13:aac7:ffff:ffff:ffff:ffff:ffff:ffff
कवर करने वाले रूट
कोई कम-विशिष्ट रूट इसे कवर नहीं करता।
अधिक-विशिष्ट रूट
- 2a13:aac4:1000::/36AS204508Gatterer Manuel trading as MLGTRPKI मान्य2a13:aac4:1000::
- 2a13:aac4:1000::/37AS204508Gatterer Manuel trading as MLGTRPKI मान्य2a13:aac4:1000::
- 2a13:aac4:1800::/37AS44908Manuel GattererRPKI मान्य2a13:aac4:1800::
- 2a13:aac4:f000::/44AS215502Xing QingyuRPKI मान्य2a13:aac4:f000::
- 2a13:aac4:f050::/44AS212628ARTRUBY PTE. LTD.RPKI मान्य2a13:aac4:f050::
- 2a13:aac4:f052::/48AS212628ARTRUBY PTE. LTD.RPKI मान्य2a13:aac4:f052::
- 2a13:aac4:f060::/44AS215340Huize Telecom LimitedRPKI नहीं मिला2a13:aac4:f060::
- 2a13:aac6:c300::/40AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac6:c300::
- 2a13:aac7:60::/44AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:60::
- 2a13:aac7:100::/40AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:100::
- 2a13:aac7:100::/46AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:100::
- 2a13:aac7:140::/46AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:140::
- 2a13:aac7:500::/40AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:500::
- 2a13:aac7:600::/44AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:600::
- 2a13:aac7:b0c::/48AS60539Huicast Telecom LimitedRPKI मान्य2a13:aac7:b0c::
यह पाठ अभी हिन्दी में उपलब्ध नहीं है। अनुवाद प्रकाशित होने तक इसे अंग्रेज़ी में दिखाया जाता है।
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.