bgpreport

Network · data from 2026-11-12

AS135915 TLSOFT-AS-VN - 8 Floor, 96-98 Dao Duy Anh, Phu Nhuan, HCMC

Registry name: TLSOFT-AS-VN - 8 Floor, 96-98 Dao Duy Anh, Phu Nhuan, HCMC, VN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135915, 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.
103.56.164.0/22 No ROA Other IRR onlyNTTCOM 672 100% 66
103.92.24.0/22 No ROA RIR databaseAPNIC, NTTCOM 670 100% 66

AS-SET

AS135915 isn't in PeeringDB, where networks name their 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 16 are in fix.csv.

  • ROA: none2
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none103.56.164.0/22No ROA covers it. Add a ROA for AS135915, maxLength 22.672 of 673
Route object: RIR103.56.164.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none103.92.24.0/22No ROA covers it. Add a ROA for AS135915, maxLength 22.670 of 673

Route objects not announced

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

103.56.164.0/23NTTCOMNo ROA
103.56.164.0/24NTTCOMNo ROA
103.56.165.0/24NTTCOMNo ROA
103.56.166.0/23NTTCOMNo ROA
103.56.166.0/24APNIC, NTTCOMNo ROA
103.56.167.0/24NTTCOMNo ROA
103.92.24.0/23NTTCOMNo ROA
103.92.24.0/24NTTCOMNo ROA
103.92.25.0/24NTTCOMNo ROA
103.92.26.0/23NTTCOMNo ROA
103.92.26.0/24NTTCOMNo ROA
103.92.27.0/24NTTCOMNo ROA
2401:1c40::/48NTTCOMNo 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.