AwanCerahBGP
Autonomous System

Nexeon Technologies, Inc.

AS20278Amerika SerikatARIN · sejak 2014NSPPeering: Open

NEXEON

nexeon.com
Nexeon Technologies, Inc. website
B80/100Baik

Rapor BGP

Peringkat 3.060 dari 19.161 jaringan di Amerika Serikat, peringkat 832 dari 2.091 ISP dan transit. Peringkat dunia 24.394.

  • RPKI ROA17/30
  • Route object IRR17/20
  • Redundansi upstream15/15
  • Visibilitas global10/10
  • IPv610/10
  • PeeringDB10/10
  • Agregasi prefix1/5

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

Riwayat nilai

RPKI ROA

Perlu perbaikan
17/30

157 dari 283 prefix punya ROA yang cocok (valid). 126 tanpa ROA.

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

Cara memperbaiki
  1. 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.
  2. 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 tanpa ROA (126)
23.94.12.0/2423.94.35.0/2423.94.39.0/2423.94.42.0/2423.95.21.0/2423.95.22.0/2423.95.40.0/2423.95.46.0/2423.239.188.0/2423.239.189.0/2438.135.224.0/2238.135.228.0/2338.135.232.0/2238.135.236.0/2238.135.240.0/2238.135.244.0/2238.135.250.0/2338.135.252.0/2296.9.192.0/1896.9.208.0/2396.9.220.0/2496.9.222.0/2496.9.223.0/2496.9.230.0/2496.47.164.0/24107.173.56.0/24107.173.58.0/24107.173.59.0/24107.173.62.0/24107.173.63.0/24107.173.64.0/24107.173.65.0/24107.173.66.0/24107.173.68.0/24107.173.69.0/24107.173.72.0/24107.173.73.0/24107.173.74.0/24107.173.75.0/24107.173.76.0/24107.173.78.0/24107.173.138.0/24107.173.139.0/24107.174.16.0/24107.174.17.0/24107.174.18.0/24107.174.19.0/24107.174.20.0/24107.174.21.0/24107.174.22.0/24107.174.23.0/24107.174.29.0/24107.174.31.0/24107.174.72.0/24107.174.73.0/24107.174.74.0/24107.174.75.0/24107.174.77.0/24107.174.98.0/24107.174.99.0/24107.174.134.0/24107.174.135.0/24107.174.168.0/24107.174.169.0/24107.175.4.0/24107.175.5.0/24107.175.9.0/24107.175.10.0/24107.175.11.0/24107.175.40.0/24107.175.41.0/24107.175.42.0/24107.175.43.0/24107.175.96.0/24107.175.97.0/24107.175.98.0/24107.175.99.0/24107.175.100.0/24107.175.101.0/24107.175.103.0/24107.175.104.0/22107.175.104.0/24107.175.105.0/24107.175.106.0/24107.175.107.0/24107.175.120.0/24107.175.121.0/24107.175.138.0/24107.175.139.0/24107.175.160.0/24107.175.161.0/24107.175.162.0/24107.175.163.0/24107.175.164.0/24107.175.165.0/24107.175.166.0/24107.175.167.0/24107.175.168.0/24107.175.169.0/24107.175.170.0/24107.175.171.0/24107.175.173.0/24107.175.174.0/24107.175.175.0/24107.175.176.0/24107.175.177.0/24107.175.179.0/24107.175.192.0/24107.175.200.0/24107.175.252.0/24108.174.51.0/24108.174.53.0/24108.174.55.0/24172.93.128.0/17172.93.163.0/24172.93.179.0/24172.93.214.0/24172.245.65.0/24172.245.69.0/24172.245.121.0/24172.245.125.0/24185.223.172.0/22192.210.208.0/24192.210.209.0/24192.210.211.0/24198.23.245.0/24

Route object IRR

Baik
17/20

139 prefix punya route object yang persis, 144 tercakup route object yang lebih besar, 0 tanpa route object.

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

Tercakup route object yang lebih besar (144)
38.135.224.0/2238.135.228.0/2338.135.232.0/2238.135.236.0/2238.135.240.0/2238.135.244.0/2238.135.250.0/2338.135.252.0/2264.44.21.0/2464.44.30.0/2464.44.32.0/2464.44.33.0/2464.44.34.0/2464.44.35.0/2464.44.36.0/2464.44.37.0/2464.44.38.0/2464.44.39.0/2464.44.40.0/2464.44.41.0/2464.44.42.0/2464.44.43.0/2464.44.44.0/2464.44.45.0/2464.44.46.0/2464.44.47.0/2464.44.55.0/2464.44.93.0/2464.44.97.0/2464.44.102.0/2464.44.112.0/2464.44.113.0/2464.44.114.0/2464.44.115.0/2464.44.116.0/2464.44.117.0/2464.44.119.0/2464.44.120.0/2464.44.121.0/2464.44.122.0/2464.44.123.0/2464.44.125.0/2464.44.126.0/2464.44.127.0/2464.44.134.0/2464.44.154.0/2464.44.176.0/2164.44.184.0/2164.44.192.0/2164.44.196.0/2464.44.200.0/2164.44.200.0/2464.44.224.0/2164.44.224.0/2464.44.254.0/2464.44.255.0/2496.9.220.0/2496.9.222.0/2496.9.223.0/2496.9.240.0/2096.9.240.0/2496.9.241.0/2496.9.242.0/2496.9.243.0/2496.9.244.0/2496.9.245.0/2496.9.246.0/2496.9.247.0/2496.9.248.0/2496.9.249.0/2496.9.250.0/2496.9.251.0/2496.9.252.0/2496.9.253.0/2496.9.254.0/2496.9.255.0/24104.200.60.0/24104.200.61.0/24104.237.194.0/24104.237.201.0/24104.237.203.0/24104.237.211.0/24167.88.0.0/24167.88.1.0/24167.88.2.0/24167.88.8.0/24167.88.10.0/24172.93.128.0/24172.93.130.0/24172.93.131.0/24172.93.136.0/24172.93.139.0/24172.93.143.0/24172.93.144.0/20172.93.144.0/24172.93.145.0/24172.93.146.0/24172.93.147.0/24172.93.148.0/24172.93.149.0/24172.93.150.0/24172.93.151.0/24172.93.152.0/24172.93.153.0/24172.93.154.0/24172.93.155.0/24172.93.156.0/24172.93.157.0/24172.93.158.0/24172.93.159.0/24172.93.179.0/24172.93.194.0/24172.93.196.0/24172.93.197.0/24172.93.214.0/24172.93.224.0/20172.93.224.0/24172.93.225.0/24172.93.226.0/24172.93.227.0/24172.93.228.0/24172.93.229.0/24172.93.230.0/24172.93.231.0/24172.93.232.0/24172.93.233.0/24172.93.234.0/24172.93.235.0/24172.93.236.0/24172.93.237.0/24172.93.238.0/242602:ffc8::/482602:ffc8:1::/482602:ffc8:2::/482602:ffc8:4::/482602:ffc8:5::/482602:ffc8:6::/482602:ffc8:3e4::/482602:ffc8:3e7::/482602:ffc8:3e8::/482602:ffc8:3d10::/442602:ffc8:3d30::/442602:ffc8:3d40::/442602:ffc8:b000::/36

Visibilitas global

Perlu perbaikan
10/10

274 dari 283 prefix terlihat oleh sedikitnya separuh feed full table route collector dunia.

Prefix yang hanya terlihat sebagian biasanya tertahan filter (tanpa ROA atau route object), terlalu spesifik, atau memang hanya diumumkan ke IX domestik.

Cara memperbaiki
  1. Periksa ROA dan route object prefix tersebut, dan pastikan panjangnya paling kecil /24 untuk IPv4 atau /48 untuk IPv6.
Prefix dengan visibilitas rendah (9)

IPv6

Baik
10/10

16 prefix IPv6 diumumkan.

Sebagian besar pengguna seluler dan layanan besar sudah memakai IPv6.

PeeringDB

Baik
10/10

Profil ada, terdaftar di 8 IX.

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

Agregasi prefix

Bermasalah
1/5

267 prefix IPv4 bisa diringkas menjadi 79.

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)

Catatan

Terlihat meneruskan 4 rute RPKI invalid milik jaringan lain di jalur sampel. Ini tanda AS ini belum menolak semua rute invalid, misalnya yang datang dari pelanggannya.

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

Cara memperbaiki
  1. Jalankan validator RPKI (misalnya Routinator atau rpki-client) dan tolak rute berstatus invalid di sesi BGP. MikroTik RouterOS 7 mendukungnya lewat menu /routing rpki dan filter rpki-verify.
Contoh rute invalid (4)

Pasang lencana di situs Anda

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