bgpreport

Network · data from 2026-11-12

AS17556 TRUE-SUB1-AS-AP - TRUE INTERNET Co.,Ltd.

Registry name: TRUE-SUB1-AS-AP - TRUE INTERNET Co.,Ltd., TH · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
7Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS17556, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17556, 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.
119.46.99.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
210.86.191.0/24 Valid RIR databaseAPNIC 667 99% 67
2001:fb1:3009:1::/64 Valid RIR databaseAPNIC 46 7%low visibility 29
2001:fb1:3009:2::/64 Valid RIR databaseAPNIC 46 7%low visibility 29
2001:fb1:3009:3::/64 Valid RIR databaseAPNIC 46 7%low visibility 29
2001:fb1:3009:7::/64 Valid RIR databaseAPNIC 46 7%low visibility 29
2001:fb1:3009:3e::/64 Valid RIR databaseAPNIC 46 7%low visibility 29
124.120.219.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
2001:fb0:10b2::/48 Valid RIR databaseAPNIC, RADB 1 0%low visibility 1

AS-SET

AS17556 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 10 are in fix.csv.

  • Route object: not announced10

Route objects not announced

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

58.97.124.0/24APNICValid
58.97.125.0/24APNICValid
114.109.249.0/24APNICValid
115.87.70.0/24APNICValid
115.87.71.0/24APNICValid
115.87.72.0/24APNICValid
115.87.73.0/24APNICValid
119.46.255.0/24APNICValid
2001:fb0:101::/48APNICValid
2001:fb0:102::/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.