AwanCerahBGP
Autonomous System

Psychz Networks

AS40676Amerika SerikatARIN · sejak 2008ContentPeering: Open

AS40676

psychz.net
Psychz Networks website
B83/100Baik

Rapor BGP

Peringkat 2.399 dari 19.161 jaringan di Amerika Serikat, peringkat 770 dari 2.091 ISP dan transit. Peringkat dunia 20.370.

  • RPKI ROA19/30
  • Route object IRR17/20
  • Redundansi upstream15/15
  • Visibilitas global9/10
  • IPv610/10
  • PeeringDB10/10
  • Agregasi prefix3/5

Dihitung dari snapshot route collector, IRR, RPKI, dan PeeringDB. Cara penilaian

Riwayat nilai

RPKI ROA

Bermasalah
19/30

464 dari 661 prefix punya ROA yang cocok (valid). 40 invalid, 157 tanpa ROA.

Banyak jaringan besar menolak rute RPKI invalid, dan prefix tanpa ROA lebih mudah dibajak.

Cara memperbaiki
  1. Dahulukan prefix berstatus invalid: jaringan yang menjalankan ROV sudah menolaknya, jadi prefix itu tidak terjangkau dari sebagian internet.
  2. Buat ROA untuk setiap prefix di portal RIR atau NIR tempat prefix terdaftar, misalnya MyAPNIC, portal anggota IDNIC, RIPE NCC LIR Portal, ARIN Online, MyAFRINIC, atau MiLACNIC.
  3. Origin di ROA harus AS yang benar-benar mengumumkan prefix. Isi maxLength sama dengan panjang prefix yang diumumkan; maxLength yang longgar membuka celah pembajakan sub-prefix.
Prefix invalid (40)
Prefix tanpa ROA (157)
23.146.216.0/2423.159.169.0/2423.226.131.0/2443.250.72.0/2443.250.73.0/2443.250.74.0/2443.250.75.0/2445.42.200.0/2445.42.201.0/2445.42.202.0/2445.42.203.0/2445.156.64.0/2445.156.65.0/2445.156.66.0/2445.156.67.0/2445.156.204.0/2445.156.207.0/2449.246.226.0/2449.246.227.0/2449.246.234.0/2449.246.235.0/2471.19.140.0/2471.19.141.0/2471.19.142.0/2471.19.143.0/2474.117.56.0/2174.117.61.0/2482.38.52.0/2282.38.88.0/2283.143.105.0/2492.118.18.0/24103.126.136.0/24103.126.137.0/24103.126.138.0/24103.126.139.0/24103.231.184.0/24104.244.152.0/24104.244.153.0/24104.244.154.0/24104.244.155.0/24104.244.157.0/24104.254.56.0/24104.254.62.0/24104.254.63.0/24123.108.128.0/23131.226.0.0/24131.226.1.0/24131.226.3.0/24131.226.6.0/24131.226.7.0/24139.64.135.0/24147.90.50.0/24154.22.5.0/24165.73.240.0/20165.73.240.0/24165.73.241.0/24165.73.242.0/24165.73.244.0/24165.73.248.0/24165.73.249.0/24165.73.252.0/23165.73.252.0/24165.231.210.0/24167.253.140.0/24167.253.141.0/24167.253.142.0/24167.253.143.0/24170.39.52.0/22172.83.178.0/24172.83.179.0/24172.83.180.0/24172.83.181.0/24172.83.182.0/24172.83.183.0/24172.83.184.0/24172.97.64.0/24172.97.66.0/24172.97.67.0/24173.224.208.0/20183.182.10.0/24183.182.18.0/24183.182.19.0/24183.182.20.0/23183.182.22.0/24185.225.4.0/23192.109.201.0/24193.42.247.0/24193.148.61.0/24194.32.127.0/24194.124.42.0/24196.60.8.0/22196.240.255.0/24198.175.228.0/24199.43.207.0/24199.71.212.0/24199.71.213.0/24199.71.214.0/24199.119.200.0/21202.5.25.0/24208.87.240.0/22208.88.149.0/24208.88.151.0/24210.16.100.0/24210.16.102.0/24211.155.64.0/23216.252.232.0/21216.252.234.0/24216.252.235.0/24216.252.236.0/24216.252.237.0/24216.252.238.0/24216.252.239.0/242406:4f40:4::/462406:4f40:8::/482406:4f40:c::/462406:4f40:f::/482406:4f40:10::/462406:4f40:14::/462406:b2c0::/322602:2c5:1::/482602:f652::/402602:ff96:5::/482602:ff96:9::/482602:ff96:12::/482602:ff96:15::/482602:ff96:16::/482602:ff96:17::/482602:ff96:1f::/482602:ff96:1fe::/482604:980:1::/482606:c0:3::/482606:6680:2::/482606:6680:4::/482606:6680:7::/482606:6680:10::/482606:6680:11::/482606:6680:12::/482606:6680:15::/482606:6680:16::/482606:6680:17::/482606:6680:18::/482606:6680:21::/482606:6680:22::/482606:6680:23::/482606:6680:24::/482606:6680:37::/482606:6680:38::/482606:6680:245::/482606:6680:409::/482606:6680:1001::/482606:6680:2000::/362606:6680:3000::/362606:6680:4000::/362606:6680:5000::/362606:6680:6000::/362a0f:2c80::/482a10:17c7:ff85::/48

Route object IRR

Perlu perbaikan
17/20

454 prefix punya route object yang persis, 156 tercakup route object yang lebih besar, 38 hanya punya route object dengan origin lain, 13 tanpa route object.

Upstream dan IX membuat filter prefix dari IRR. Prefix tanpa route object bisa ditolak tanpa pemberitahuan.

Cara memperbaiki
  1. Buat objek route (IPv4) dan route6 (IPv6) dengan origin AS Anda di IRR milik RIR Anda, misalnya APNIC lewat MyAPNIC atau IDNIC, atau di RADB.
  2. Kelompokkan pelanggan Anda dalam satu as-set dan cantumkan di PeeringDB supaya upstream bisa membuat filter otomatis.
Tanpa route object (13)
Route object dengan origin lain (38)
Tercakup route object yang lebih besar (156)
45.156.64.0/2445.156.65.0/2445.156.66.0/2445.156.67.0/24104.222.160.0/24108.181.0.0/19108.181.8.0/24108.181.32.0/20108.181.48.0/24108.181.49.0/24108.181.54.0/23108.181.56.0/23108.181.60.0/32108.181.61.0/24108.181.68.0/23108.181.70.0/23108.181.72.0/23108.181.74.0/23108.181.76.0/23108.181.78.0/23108.181.80.0/23108.181.82.0/23108.181.84.0/23108.181.86.0/23108.181.88.0/23108.181.90.0/23108.181.92.0/23108.181.94.0/23108.181.96.0/23108.181.98.0/23108.181.100.0/23108.181.102.0/23108.181.104.0/23108.181.106.0/23108.181.108.0/23108.181.110.0/23108.181.112.0/23108.181.114.0/23108.181.114.0/24108.181.116.0/23108.181.118.0/23108.181.118.0/24108.181.120.0/24108.181.121.0/24108.181.130.0/24108.181.132.0/22108.181.144.0/23108.181.146.0/23108.181.148.0/22108.181.152.0/22108.181.154.0/24108.181.155.0/24108.181.156.0/22108.181.156.0/24108.181.160.0/21108.181.164.0/24108.181.165.0/24108.181.166.0/24108.181.167.0/24108.181.168.0/21108.181.168.0/24108.181.170.0/24108.181.171.0/24108.181.172.0/24108.181.173.0/24108.181.174.0/24108.181.175.0/24108.181.180.0/22108.181.181.0/24108.181.184.0/21108.181.184.0/24108.181.185.0/24108.181.187.0/24108.181.188.0/24108.181.189.0/24108.181.190.0/24108.181.191.0/24108.181.192.0/21108.181.192.0/24108.181.194.0/24108.181.195.0/24108.181.200.0/22108.181.200.0/24108.181.203.0/24108.181.204.0/22108.181.208.0/22108.181.212.0/22108.181.212.0/24108.181.216.0/22108.181.218.0/24108.181.219.0/24108.181.220.0/22108.181.221.0/24108.181.224.0/22108.181.229.0/24108.181.230.0/23108.181.230.0/24108.181.232.0/22108.181.236.0/23108.181.240.0/21108.181.248.0/23108.181.250.0/24108.181.252.0/22108.181.254.0/24108.181.255.0/24131.226.0.0/24131.226.1.0/24131.226.3.0/24131.226.6.0/24131.226.7.0/24140.174.48.0/24140.174.49.0/24140.174.50.0/24140.174.51.0/24140.174.52.0/24140.174.176.0/24140.174.178.0/24140.174.183.0/24140.174.184.0/24140.174.185.0/24140.174.186.0/24140.174.187.0/24140.174.189.0/24140.174.190.0/23165.73.244.0/24165.73.249.0/24165.73.252.0/23165.73.252.0/24199.71.214.0/24205.236.250.0/24205.236.251.0/24216.252.234.0/24216.252.235.0/24216.252.236.0/24216.252.237.0/24216.252.238.0/24216.252.239.0/242406:4f40:f::/482406:4f40:14::/462604:6600:5::/482604:6600:7::/482604:6600:a::/482604:6600:2000::/482604:6600:2001::/482604:6600:2002::/482604:6600:2009::/482604:6600:2010::/482604:6600:2600::/402604:6600:2601::/482604:6600:2700::/402604:6600:fcfe::/482604:6600:fd00::/482604:6600:fffb::/482604:6600:fffc::/482604:6600:fffd::/482a10:17c7:ff85::/48

IPv6

Baik
10/10

118 prefix IPv6 diumumkan.

Sebagian besar pengguna seluler dan layanan besar sudah memakai IPv6.

PeeringDB

Baik
10/10

Profil ada, terdaftar di 10 IX.

Calon peer dan upstream mencari kontak, kebijakan, dan as-set Anda di PeeringDB.

Agregasi prefix

Perlu perbaikan
3/5

543 prefix IPv4 bisa diringkas menjadi 339.

Pemecahan prefix menambah beban tabel routing dunia. Pemecahan untuk traffic engineering tetap wajar.

Cara memperbaiki
  1. Umumkan agregat bila pemecahan tidak diperlukan. Bila disengaja, pastikan setiap potongan punya ROA dan route object sendiri.

Penolakan rute invalid (ROV)

Baik

Tidak terlihat meneruskan rute RPKI invalid milik jaringan lain di jalur sampel.

Tidak dihitung dalam nilai. Dugaan ini diambil dari contoh AS path, jadi bisa saja rute itu datang dari pelanggan yang dikecualikan.

Pasang lencana di situs Anda

Rapor BGP AS40676Lencana diperbarui otomatis setiap snapshot.
HTML
<a href="https://bgp.awancerah.cloud/AS40676/rapor"><img src="https://bgp.awancerah.cloud/AS40676/rapor.svg" alt="Rapor BGP AS40676"></a>
Markdown
[![Rapor BGP AS40676](https://bgp.awancerah.cloud/AS40676/rapor.svg)](https://bgp.awancerah.cloud/AS40676/rapor)