BGP پریفکس تلاش
ایک پریفکس (یا واحد ایڈریس) درج کریں۔ عالمی روٹنگ ٹیبل کی ہماری روزانہ نقل سے جواب۔
240e:45c::/32
بالکل اسی شکل میں اعلان شدہ
- 240e:45c::/32AS131285CHINATELECOM Hubei province Shengji 5G networkRPKI درست240e:45c::
- رجسٹری
- APNIC · چین · 14 دسمبر، 2011
- تفویض شدہ بلاک
- 240e:400:: – 240e:7ff:ffff:ffff:ffff:ffff:ffff:ffff
ڈھانپنے والے روٹس
- 240e:45c::/30AS4134No.31,Jin-rong StreetRPKI درست240e:45c::
- 240e::/20AS4134No.31,Jin-rong StreetRPKI نہیں ملا240e::
زیادہ مخصوص روٹس
- 240e:45c::/33AS131285CHINATELECOM Hubei province Shengji 5G networkRPKI درست240e:45c::
- 240e:45c:1b00::/40AS137401CHINATELECOM Hubei province Huangshi 5G networkRPKI درست240e:45c:1b00::
- 240e:45c:1d00::/40AS137401CHINATELECOM Hubei province Huangshi 5G networkRPKI درست240e:45c:1d00::
- 240e:45c:1f00::/40AS137401CHINATELECOM Hubei province Huangshi 5G networkRPKI درست240e:45c:1f00::
- 240e:45c:2700::/40AS137402CHINATELECOM Hubei province Shiyan 5G networkRPKI درست240e:45c:2700::
- 240e:45c:2900::/40AS137402CHINATELECOM Hubei province Shiyan 5G networkRPKI درست240e:45c:2900::
- 240e:45c:2b00::/40AS137402CHINATELECOM Hubei province Shiyan 5G networkRPKI درست240e:45c:2b00::
- 240e:45c:3700::/40AS140528CHINATELECOM Hubei province Yichang 5G networkRPKI درست240e:45c:3700::
- 240e:45c:3900::/40AS140528CHINATELECOM Hubei province Yichang 5G networkRPKI درست240e:45c:3900::
- 240e:45c:3b00::/40AS140528CHINATELECOM Hubei province Yichang 5G networkRPKI درست240e:45c:3b00::
- 240e:45c:5100::/40AS140529CHINATELECOM Hubei province Xiangyang 5G networkRPKI درست240e:45c:5100::
- 240e:45c:5300::/40AS140529CHINATELECOM Hubei province Xiangyang 5G networkRPKI درست240e:45c:5300::
- 240e:45c:5500::/40AS140529CHINATELECOM Hubei province Xiangyang 5G networkRPKI درست240e:45c:5500::
- 240e:45c:6300::/40AS140530CHINATELECOM Hubei province Ezhou 5G networkRPKI درست240e:45c:6300::
- 240e:45c:6500::/40AS140530CHINATELECOM Hubei province Ezhou 5G networkRPKI درست240e:45c:6500::
- 240e:45c:6700::/40AS140530CHINATELECOM Hubei province Ezhou 5G networkRPKI درست240e:45c:6700::
- 240e:45c:6900::/40AS140531CHINATELECOM Hubei province Jingmen 5G networkRPKI درست240e:45c:6900::
- 240e:45c:6b00::/40AS140531CHINATELECOM Hubei province Jingmen 5G networkRPKI درست240e:45c:6b00::
- 240e:45c:6d00::/40AS140531CHINATELECOM Hubei province Jingmen 5G networkRPKI درست240e:45c:6d00::
- 240e:45c:7300::/40AS140532CHINATELECOM Hubei province Xiaogan 5G networkRPKI درست240e:45c:7300::
- 240e:45c:7500::/40AS140532CHINATELECOM Hubei province Xiaogan 5G networkRPKI درست240e:45c:7500::
- 240e:45c:7700::/40AS140532CHINATELECOM Hubei province Xiaogan 5G networkRPKI درست240e:45c:7700::
- 240e:45c:8000::/33AS131285CHINATELECOM Hubei province Shengji 5G networkRPKI درست240e:45c:8000::
- 240e:45c:8100::/40AS140533CHINATELECOM Hubei province Jingzhou 5G networkRPKI درست240e:45c:8100::
- 240e:45c:8300::/40AS140533CHINATELECOM Hubei province Jingzhou 5G networkRPKI درست240e:45c:8300::
- 240e:45c:8500::/40AS140533CHINATELECOM Hubei province Jingzhou 5G networkRPKI درست240e:45c:8500::
- 240e:45c:9100::/40AS140534CHINATELECOM Hubei province Huanggang 5G networkRPKI درست240e:45c:9100::
- 240e:45c:9300::/40AS140534CHINATELECOM Hubei province Huanggang 5G networkRPKI درست240e:45c:9300::
- 240e:45c:9500::/40AS140534CHINATELECOM Hubei province Huanggang 5G networkRPKI درست240e:45c:9500::
- 240e:45c:a500::/40AS140535CHINATELECOM Hubei province Xianning 5G networkRPKI درست240e:45c:a500::
- 240e:45c:a700::/40AS140535CHINATELECOM Hubei province Xianning 5G networkRPKI درست240e:45c:a700::
- 240e:45c:a900::/40AS140535CHINATELECOM Hubei province Xianning 5G networkRPKI درست240e:45c:a900::
- 240e:45c:b100::/40AS140537CHINATELECOM Hubei province Enshi 5G networkRPKI درست240e:45c:b100::
- 240e:45c:b300::/40AS140537CHINATELECOM Hubei province Enshi 5G networkRPKI درست240e:45c:b300::
- 240e:45c:b500::/40AS140537CHINATELECOM Hubei province Enshi 5G networkRPKI درست240e:45c:b500::
- 240e:45c:c100::/40AS140536CHINATELECOM Hubei province Suizhou 5G networkRPKI درست240e:45c:c100::
- 240e:45c:c300::/40AS140536CHINATELECOM Hubei province Suizhou 5G networkRPKI درست240e:45c:c300::
- 240e:45c:c500::/40AS140536CHINATELECOM Hubei province Suizhou 5G networkRPKI درست240e:45c:c500::
- 240e:45c:c700::/40AS140538CHINATELECOM Hubei province Xiantao 5G networkRPKI درست240e:45c:c700::
- 240e:45c:c900::/40AS140538CHINATELECOM Hubei province Xiantao 5G networkRPKI درست240e:45c:c900::
- 240e:45c:cb00::/40AS140538CHINATELECOM Hubei province Xiantao 5G networkRPKI درست240e:45c:cb00::
یہ متن ابھی اردو میں دستیاب نہیں۔ ترجمہ شائع ہونے تک اسے انگریزی میں دکھایا جاتا ہے۔
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.