bgpreport

Network · data from 2026-11-12

AS136393 SYMPHONY-AS-AP - Symphony Communication (Thailand) PCL.

Registry name: SYMPHONY-AS-AP - Symphony Communication (Thailand) PCL., TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136393, 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.
146.88.36.0/24 Valid RIR databaseAPNIC 673 100% 68
96.30.68.0/22 Valid RIR databaseAPNIC, RADB 672 100% 68
96.30.72.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
96.30.79.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
96.30.84.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
96.30.100.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
96.30.108.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
119.110.227.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.37.0/24 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.38.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.44.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.46.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.52.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
146.88.54.0/24 Valid RIR databaseAPNIC 672 100% 68
161.82.186.0/23 Valid RIR databaseAPNIC, RADB 672 100% 68
2400:6280:18::/48 Valid RIR databaseAPNIC 635 100% 69
2400:6280:28::/48 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS136393 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 24 are in fix.csv.

  • Route object: not announced24

Route objects not announced

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

96.30.64.0/21APNIC, RADBValid
96.30.64.0/22APNICValid
96.30.64.0/23APNIC, RADBValid
96.30.64.0/24APNICValid
96.30.66.0/23APNIC, RADBValid
96.30.68.0/23APNIC, RADBValid
96.30.70.0/23APNIC, RADBValid
96.30.84.0/22APNIC, RADBValid
96.30.86.0/23APNIC, RADBValid
96.30.88.0/22APNICInvalid: origin
96.30.100.0/22APNIC, RADBValid
96.30.102.0/23APNIC, RADBValid
96.30.107.0/24APNIC, RADBValid
96.30.111.0/24APNIC, RADBValid
103.14.10.0/24APNIC, RADBValid
146.88.36.0/22APNIC, RADBValid
146.88.42.0/23APNIC, RADBValid
146.88.44.0/22APNIC, RADBValid
146.88.52.0/22APNIC, RADBValid
146.88.52.0/24APNICValid
146.88.53.0/24APNICValid
146.88.54.0/23APNIC, RADBValid
146.88.55.0/24APNICValid
2400:6280:19::/48APNICValid

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.