bgpreport

Network · data from 2026-11-12

AS134489 S. B Link Network

Registry name: SBLINKNETWORK-AS-AP - S. B Link Network, PK · PeeringDB

17IPv4 routes 76.5% RPKI valid · 88.2% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
2No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS134489, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134489, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
203.128.20.0/24 Invalid: origin Other origin only 1 0%low visibility 1
156.238.86.0/24 Invalid: origin RIR databaseAFRINIC 2 0%low visibility 3
203.128.24.0/24 No ROA Other origin only 1 0%low visibility 1
149.71.34.0/24 No ROA Other IRR onlyRADB 673 100% 66
103.161.48.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.161.49.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
111.92.147.0/24 Valid RIR databaseAPNIC 673 100% 66
111.92.148.0/24 Valid RIR databaseAPNIC 673 100% 66
111.92.155.0/24 Valid RIR databaseAPNIC 673 100% 66
111.92.156.0/24 Valid RIR databaseAPNIC 673 100% 66
116.90.105.0/24 Valid RIR databaseAPNIC 673 100% 66
122.129.86.0/24 Valid RIR databaseAPNIC 673 100% 66
160.30.104.0/24 Valid RIR databaseAPNIC 673 100% 66
160.30.105.0/24 Valid RIR databaseAPNIC 673 100% 66
203.128.10.0/24 Valid RIR databaseAPNIC 673 100% 66
111.92.146.0/24 Valid RIR databaseAPNIC 672 100% 66
116.90.100.0/24 Valid RIR databaseAPNIC 672 100% 67
2407:1b40::/32 Valid RIR databaseAPNIC 634 100% 67

AS-SET

AS134489's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • ROA: origin2
  • ROA: none2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: origin203.128.20.0/24ROAs covering it name AS17911, not AS134489. If AS134489 should announce it, add a ROA for AS134489.1 of 673
Route object: none203.128.20.0/24Route objects for it name AS17911. Add a route object with origin AS134489 in the RIR database for the space.1 of 673
ROA: origin156.238.86.0/24ROAs covering it name AS17561, AS139238, not AS134489. If AS134489 should announce it, add a ROA for AS134489.2 of 673
ROA: none203.128.24.0/24No ROA covers it. Add a ROA for AS134489, maxLength 24.1 of 673
Route object: none203.128.24.0/24Route objects for it name AS17911, AS38193. Add a route object with origin AS134489 in the RIR database for the space.1 of 673
ROA: none149.71.34.0/24No ROA covers it. Add a ROA for AS134489, maxLength 24.673 of 673
Route object: RIR149.71.34.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS134489 whose prefix no peer sees AS134489 announce. Many are kept on purpose (backup routes, space announced only in some places).

59.103.36.0/24APNICValid
59.103.37.0/24APNICValid
122.129.86.0/23RADBNo ROA
149.71.35.0/24RADBNo ROA
154.82.17.0/24AFRINICInvalid: origin
180.178.146.0/24RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.