AwanCerahBGP
Autonomous System

Research Organization of Information and Systems, National Institute of Informatics

AS2907JepangAPNIC · sejak 2002Educational/ResearchPeering: Selective

SINET-AS

sinet.ad.jp
Research Organization of Information and Systems, National Institute of Informatics website
B70/100Baik

Rapor BGP

Peringkat 372 dari 754 jaringan di Jepang, peringkat 92 dari 131 ISP dan transit. Peringkat dunia 43.799.

  • RPKI ROA2/30
  • Route object IRR19/20
  • Redundansi upstream15/15
  • Visibilitas global9/10
  • IPv610/10
  • PeeringDB10/10
  • Agregasi prefix5/5

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

Riwayat nilai

RPKI ROA

Perlu perbaikan
2/30

41 dari 668 prefix punya ROA yang cocok (valid). 627 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 (627)
103.164.74.0/23103.164.166.0/23103.164.168.0/23103.180.128.0/23130.34.0.0/16130.153.0.0/16131.206.0.0/16133.7.0.0/16133.8.0.0/16133.10.0.0/16133.12.0.0/16133.14.0.0/16133.15.0.0/16133.16.0.0/16133.17.0.0/16133.17.7.0/24133.17.10.0/24133.20.0.0/16133.21.0.0/16133.23.0.0/16133.29.0.0/16133.30.0.0/16133.32.100.0/22133.34.0.0/16133.35.0.0/16133.38.0.0/16133.39.0.0/16133.44.0.0/16133.45.0.0/16133.46.0.0/16133.46.248.0/21133.48.0.0/16133.49.0.0/16133.52.0.0/16133.54.0.0/18133.54.64.0/21133.54.76.0/24133.54.77.0/24133.54.78.0/23133.54.80.0/20133.54.96.0/19133.54.128.0/17133.55.0.0/16133.57.0.0/16133.58.0.0/16133.60.0.0/16133.62.0.0/16133.63.0.0/16133.65.0.0/16133.68.0.0/16133.72.0.0/16133.73.0.0/16133.74.0.0/16133.74.192.0/18133.77.0.0/16133.78.0.0/16133.78.28.192/27133.78.28.224/28133.81.0.0/16133.82.0.0/16133.83.0.0/16133.84.0.0/16133.85.0.0/16133.86.0.0/16133.86.207.0/24133.86.208.0/24133.86.246.0/24133.86.247.0/24133.86.248.0/24133.86.250.0/24133.86.252.70/32133.86.252.71/32133.88.224.0/24133.88.225.0/24133.88.226.0/24133.89.0.0/16133.94.0.0/16133.95.0.0/16133.96.0.0/16133.98.0.0/16133.99.0.0/16133.102.0.0/16133.103.0.0/16133.104.0.0/16133.106.0.0/21133.187.0.0/16133.220.0.0/16134.160.186.0/24134.160.187.0/24134.160.188.0/24134.160.189.0/24136.187.0.0/16144.213.0.0/16147.157.0.0/17147.157.85.0/24147.157.128.0/17150.7.0.0/16150.7.28.0/24150.7.250.0/24150.9.254.0/23150.12.0.0/16150.15.0.0/16150.22.0.0/22150.42.0.0/16150.43.0.0/16150.46.0.0/16150.46.0.0/17150.46.128.0/17150.54.0.0/16150.59.0.0/16150.69.0.0/16150.83.0.0/16150.84.0.0/16150.86.0.0/16150.86.248.0/21150.89.0.0/17150.89.128.0/17150.89.160.0/20150.97.0.0/16157.6.0.0/16157.7.0.0/19157.13.0.0/16157.13.129.0/24157.16.0.0/16157.17.0.0/19157.19.0.0/16157.63.0.0/16157.76.0.0/16157.80.0.0/16157.102.0.0/16157.105.0.0/16157.111.0.0/16157.111.0.0/20157.111.16.0/24157.114.0.0/16158.203.0.0/16158.208.0.0/16158.210.0.0/16158.215.0.0/16160.11.0.0/16160.12.0.0/16160.15.0.0/16160.18.2.0/24160.18.100.0/24160.18.128.0/24160.18.136.0/23160.18.148.0/23160.18.216.0/23160.18.220.0/23160.18.224.0/24160.18.225.0/24160.28.0.0/16160.28.8.0/24160.28.9.0/24160.28.202.0/23160.28.204.0/23160.28.206.0/23160.28.208.0/23160.28.212.0/23160.28.214.0/23160.28.216.0/23160.28.218.0/23160.28.222.0/23160.28.224.0/23160.28.226.0/23160.28.228.0/23160.190.0.0/16160.193.0.0/16160.194.0.0/16160.198.0.0/16160.202.0.0/21160.204.0.0/16160.237.0.0/18160.237.192.0/18160.238.1.0/24160.238.2.0/24160.238.3.0/24160.238.4.0/24160.238.5.0/24160.238.6.0/24160.238.7.0/24160.238.8.0/24160.238.9.0/24160.238.10.0/24160.238.20.0/24160.238.30.0/24160.238.32.0/24160.238.40.0/24160.238.51.0/24160.238.56.0/24160.238.62.0/24160.238.100.0/24160.245.112.0/24160.247.0.0/16160.252.0.0/16163.42.0.0/16163.47.1.0/24163.47.2.0/23163.51.0.0/16163.51.161.0/24

Route object IRR

Perlu perbaikan
19/20

529 prefix punya route object yang persis, 138 tercakup route object yang lebih besar, 1 hanya punya route object dengan origin lain, 0 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.
Route object dengan origin lain (1)
Tercakup route object yang lebih besar (138)
133.17.7.0/24133.46.248.0/21133.54.0.0/18133.54.64.0/21133.54.76.0/24133.54.77.0/24133.54.78.0/23133.54.80.0/20133.54.96.0/19133.54.128.0/17133.78.28.192/27133.78.28.224/28133.86.252.70/32133.86.252.71/32134.160.189.0/24150.7.28.0/24150.7.250.0/24150.89.160.0/20157.13.129.0/24157.111.0.0/20157.111.16.0/24160.28.202.0/23160.28.204.0/23160.28.206.0/23160.28.208.0/23160.28.212.0/23160.28.214.0/23160.28.216.0/23160.28.218.0/23160.28.222.0/23160.28.224.0/23160.28.226.0/23160.28.228.0/23163.51.161.0/24163.51.162.0/24163.51.163.0/24163.51.164.0/24163.51.165.0/24163.51.166.0/24163.51.167.0/24163.51.168.0/24163.51.169.0/24163.51.170.0/24163.51.171.0/24163.51.172.0/24163.51.173.0/24163.51.174.0/24163.212.29.0/24192.42.103.0/26192.153.95.160/27202.23.64.0/22202.26.224.0/24202.34.192.0/20202.34.242.0/24202.34.243.0/24202.35.199.0/24202.145.16.0/24202.145.17.0/24202.145.18.0/23202.145.24.0/24202.145.25.0/24202.211.0.0/20202.211.16.0/20202.220.21.250/32202.236.107.32/27202.236.107.96/28202.236.143.224/27202.237.255.0/24202.240.8.0/24202.240.9.0/24202.240.10.0/24202.240.11.0/24202.240.12.0/24202.240.13.0/24202.240.14.0/24202.240.15.0/24202.240.15.10/32202.240.15.11/32202.240.15.12/32202.240.15.13/32202.240.15.14/32202.240.15.15/32202.240.15.16/32202.240.15.17/32202.240.15.18/32202.240.15.19/32202.240.15.20/32202.240.15.21/32202.240.15.22/32202.240.15.23/32202.240.15.24/32202.240.15.25/32202.240.15.26/32202.240.15.27/32202.240.15.28/32202.240.15.29/32202.240.15.30/32202.240.15.31/32202.240.15.32/32202.240.15.33/32202.240.15.34/32202.240.15.35/32202.240.15.36/32202.240.15.37/32202.240.15.48/28202.240.15.190/32202.240.15.191/32202.240.15.192/32202.240.15.193/32202.240.15.194/32202.240.15.195/32202.240.15.196/32202.240.15.197/32202.240.15.198/32202.240.15.199/32202.240.15.200/32202.240.15.202/32202.240.15.204/32202.240.15.205/32202.240.15.206/32202.240.15.207/32202.240.15.209/32202.240.15.210/32202.240.15.212/32202.240.15.246/32202.240.15.247/32202.242.14.0/24202.242.120.0/24202.242.121.0/24202.245.104.0/23202.246.131.0/24202.246.132.64/26202.246.136.0/24202.251.201.0/24202.251.202.0/24202.251.203.0/24202.254.230.0/24210.137.12.0/22

Redundansi upstream

Baik
15/15

14 upstream, 31 peer, 109 downstream.

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

Upstream (14)

Visibilitas global

Perlu perbaikan
9/10

606 dari 668 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 (62)

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 7 IX.

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

Agregasi prefix

Baik
5/5

666 prefix IPv4 bisa diringkas menjadi 466.

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

Penolakan rute invalid (ROV)

Catatan

Terlihat meneruskan 2 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 (2)

Pasang lencana di situs Anda

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