AwanCerahBGP
Autonomous System

Hosted Backbone

AS14713Amerika SerikatARIN · sejak 2015Cable/DSL/ISPEnterprisePeering: Open

HBL-35-14713

D44/100Kurang

Rapor BGP

Peringkat 13.205 dari 19.165 jaringan di Amerika Serikat, peringkat 1.870 dari 2.091 ISP dan transit. Peringkat dunia 74.307.

  • RPKI ROA0/30
  • Route object IRR2/20
  • Redundansi upstream15/15
  • Visibilitas global6/10
  • IPv610/10
  • PeeringDB10/10
  • Agregasi prefix1/5

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

Riwayat nilai

RPKI ROA

Bermasalah
0/30

13 dari 222 prefix punya ROA yang cocok (valid). 119 invalid, 90 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 (119)
46.70.0.0/22origin46.70.4.0/22origin46.70.8.0/22origin46.70.12.0/22origin46.70.16.0/22origin46.70.20.0/22origin46.70.24.0/22origin46.70.28.0/22origin46.70.32.0/22origin46.70.36.0/22origin46.70.40.0/22origin46.70.44.0/22origin46.70.48.0/22origin46.70.52.0/22origin46.70.56.0/22origin46.70.60.0/22origin46.70.64.0/22origin46.70.68.0/22origin46.70.72.0/22origin46.70.76.0/22origin46.70.80.0/22origin46.70.84.0/22origin46.70.88.0/22origin46.70.92.0/22origin46.70.96.0/22origin46.70.100.0/22origin46.70.104.0/22origin46.70.108.0/22origin46.70.112.0/22origin46.70.116.0/22origin46.70.120.0/22origin46.70.124.0/22origin46.70.128.0/20origin46.70.144.0/20origin46.70.160.0/20origin46.70.176.0/20origin64.8.240.0/24origin64.8.241.0/24origin64.8.242.0/24origin64.8.243.0/24origin64.8.244.0/24origin64.8.245.0/24origin64.8.246.0/24origin64.8.247.0/24origin87.192.32.0/22origin87.192.81.0/24origin87.192.82.0/23origin87.192.222.0/23origin87.232.192.0/24origin87.232.194.0/23origin87.232.225.0/24origin89.124.1.0/24origin173.0.120.0/23origin173.0.120.0/24origin173.0.121.0/24origin173.0.122.0/24origin173.0.123.0/24origin173.0.124.0/24origin173.0.125.0/24origin173.0.126.0/24origin173.0.127.0/24origin194.179.160.0/22origin194.179.164.0/22origin194.179.168.0/22origin194.179.172.0/22origin194.179.176.0/22origin194.179.180.0/22origin194.179.184.0/22origin194.179.188.0/22origin194.179.224.0/22origin194.179.228.0/22origin194.179.232.0/22origin194.179.236.0/22origin194.179.240.0/22origin194.179.244.0/22origin194.179.248.0/22origin194.179.252.0/22origin205.201.176.0/24origin205.201.177.0/24origin205.201.178.0/24origin205.201.179.0/24origin205.201.180.0/24origin205.201.181.0/24origin205.201.182.0/24origin205.201.183.0/24origin205.201.184.0/24origin205.201.185.0/24origin205.201.186.0/24origin205.201.187.0/24origin205.201.188.0/24origin205.201.189.0/24origin205.201.190.0/24origin205.201.191.0/24origin207.251.16.0/24origin207.251.17.0/24origin207.251.18.0/24origin207.251.19.0/24origin207.251.20.0/24origin207.251.21.0/24origin207.251.22.0/24origin207.251.23.0/24origin207.251.24.0/24origin207.251.25.0/24origin207.251.26.0/24origin207.251.27.0/24origin207.251.28.0/24origin207.251.29.0/24origin207.251.30.0/24origin207.251.31.0/24origin209.166.32.0/24origin209.166.33.0/24origin209.166.34.0/24origin209.166.35.0/24origin209.166.36.0/24origin209.166.37.0/24origin209.166.38.0/24origin209.166.39.0/24origin209.250.64.0/20origin209.250.80.0/20origin
Prefix tanpa ROA (90)

Route object IRR

Bermasalah
2/20

16 prefix punya route object yang persis, 4 tercakup route object yang lebih besar, 152 hanya punya route object dengan origin lain, 50 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 (50)
Route object dengan origin lain (152)
46.70.0.0/2246.70.4.0/2246.70.8.0/2246.70.12.0/2246.70.16.0/2246.70.20.0/2246.70.24.0/2246.70.28.0/2246.70.32.0/2246.70.36.0/2246.70.40.0/2246.70.44.0/2246.70.48.0/2246.70.52.0/2246.70.56.0/2246.70.60.0/2246.70.64.0/2246.70.68.0/2246.70.72.0/2246.70.76.0/2246.70.80.0/2246.70.84.0/2246.70.88.0/2246.70.92.0/2246.70.96.0/2246.70.100.0/2246.70.104.0/2246.70.108.0/2246.70.112.0/2246.70.116.0/2246.70.120.0/2246.70.124.0/2246.70.128.0/2046.70.144.0/2046.70.160.0/2046.70.176.0/2064.8.240.0/2464.8.241.0/2464.8.242.0/2464.8.243.0/2464.8.244.0/2464.8.245.0/2464.8.246.0/2464.8.247.0/2487.192.32.0/2287.192.52.0/2287.192.56.0/2287.192.60.0/2287.192.81.0/2487.192.82.0/2387.192.222.0/2387.232.192.0/2487.232.194.0/2387.232.225.0/2489.124.2.0/2389.124.4.0/2289.124.240.0/2389.124.245.0/24139.171.0.0/22139.171.4.0/22139.171.8.0/22139.171.12.0/22139.171.16.0/22139.171.20.0/22139.171.24.0/22139.171.28.0/22139.171.32.0/22139.171.36.0/22139.171.40.0/22139.171.52.0/22139.171.56.0/22139.171.64.0/22139.171.72.0/22139.171.88.0/22139.171.100.0/22139.171.104.0/22139.171.108.0/22139.171.112.0/22139.171.116.0/22139.171.120.0/24139.171.121.0/24139.171.122.0/24139.171.123.0/24173.0.120.0/23173.0.120.0/24173.0.121.0/24173.0.122.0/24173.0.123.0/24173.0.124.0/24173.0.125.0/24173.0.126.0/24173.0.127.0/24194.179.160.0/22194.179.164.0/22194.179.168.0/22194.179.172.0/22194.179.176.0/22194.179.180.0/22194.179.184.0/22194.179.188.0/22194.179.224.0/22194.179.228.0/22194.179.232.0/22194.179.236.0/22194.179.240.0/22194.179.244.0/22194.179.248.0/22194.179.252.0/22205.201.176.0/24205.201.177.0/24205.201.178.0/24205.201.179.0/24205.201.180.0/24205.201.181.0/24205.201.182.0/24205.201.183.0/24205.201.184.0/24205.201.185.0/24205.201.186.0/24205.201.187.0/24205.201.188.0/24205.201.189.0/24205.201.190.0/24205.201.191.0/24206.223.118.0/23207.251.16.0/24207.251.17.0/24207.251.18.0/24207.251.19.0/24207.251.20.0/24207.251.21.0/24207.251.22.0/24207.251.23.0/24207.251.24.0/24207.251.25.0/24207.251.26.0/24207.251.27.0/24207.251.28.0/24207.251.29.0/24207.251.30.0/24207.251.31.0/24208.250.80.0/20209.166.32.0/24209.166.33.0/24209.166.34.0/24209.166.35.0/24209.166.36.0/24209.166.37.0/24209.166.38.0/24209.166.39.0/24209.250.64.0/20209.250.80.0/20
Tercakup route object yang lebih besar (4)

Redundansi upstream

Baik
15/15

17 upstream, 29 peer, 9 downstream.

Dengan satu upstream, gangguan di upstream itu memutus seluruh jaringan Anda dari internet.

Upstream (17)

Visibilitas global

Perlu perbaikan
6/10

131 dari 222 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 (91)
46.70.128.0/200,1%46.70.144.0/200,1%64.112.184.0/220,3%87.192.0.0/221,9%87.192.4.0/221,9%87.192.8.0/221,9%87.192.12.0/221,9%87.192.16.0/221,9%87.192.20.0/221,9%87.192.24.0/221,9%87.192.28.0/221,9%87.192.36.0/221,9%87.192.40.0/221,9%87.192.44.0/221,9%87.192.48.0/221,9%87.192.52.0/222,0%87.192.56.0/221,9%87.192.60.0/222,0%87.192.82.0/230,4%87.192.84.0/222,1%87.192.216.0/222,1%87.192.222.0/230,4%87.232.192.0/240,4%87.232.194.0/230,4%87.232.196.0/222,1%87.232.228.0/222,1%89.124.1.0/240,4%89.124.4.0/222,3%89.127.0.0/221,9%89.127.4.0/221,9%89.127.8.0/221,9%89.127.12.0/221,9%89.127.16.0/221,9%89.127.20.0/221,9%89.127.24.0/221,9%89.127.28.0/221,9%89.127.32.0/221,9%89.127.36.0/221,9%89.127.40.0/221,9%89.127.44.0/221,9%89.127.48.0/221,9%89.127.52.0/221,9%89.127.56.0/221,9%89.127.60.0/221,9%89.127.64.0/221,9%89.127.68.0/221,9%89.127.72.0/221,9%89.127.76.0/221,9%89.127.80.0/221,9%89.127.84.0/221,9%89.127.88.0/221,9%89.127.92.0/221,9%89.127.96.0/221,9%89.127.100.0/221,9%89.127.104.0/221,9%89.127.108.0/221,9%89.127.112.0/221,9%89.127.116.0/221,9%89.127.120.0/221,9%89.127.124.0/221,9%89.127.248.0/222,1%139.171.0.0/221,9%139.171.4.0/221,9%139.171.8.0/221,9%139.171.12.0/221,9%139.171.16.0/221,9%139.171.20.0/221,9%139.171.24.0/221,9%139.171.28.0/221,9%139.171.32.0/221,9%139.171.36.0/221,9%139.171.40.0/221,9%139.171.52.0/221,9%139.171.56.0/221,9%139.171.64.0/221,9%139.171.72.0/221,9%139.171.88.0/221,9%139.171.100.0/221,9%139.171.104.0/221,9%139.171.108.0/221,9%139.171.112.0/221,9%139.171.116.0/221,9%139.171.120.0/241,9%139.171.121.0/241,9%139.171.122.0/241,9%139.171.123.0/241,9%173.0.120.0/230,1%204.150.247.0/240,5%208.250.80.0/201,9%209.250.64.0/200,1%209.250.80.0/200,1%

IPv6

Baik
10/10

2 prefix IPv6 diumumkan.

Sebagian besar pengguna seluler dan layanan besar sudah memakai IPv6.

PeeringDB

Baik
10/10

Profil ada, terdaftar di 3 IX.

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

Agregasi prefix

Bermasalah
1/5

220 prefix IPv4 bisa diringkas menjadi 52.

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 1.557 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 AS14713Lencana diperbarui otomatis setiap snapshot.
HTML
<a href="https://bgp.awancerah.cloud/AS14713/rapor"><img src="https://bgp.awancerah.cloud/AS14713/rapor.svg" alt="Rapor BGP AS14713"></a>
Markdown
[![Rapor BGP AS14713](https://bgp.awancerah.cloud/AS14713/rapor.svg)](https://bgp.awancerah.cloud/AS14713/rapor)