bgpreport

Network · data from 2026-11-12

AS135290 SAN-AS-AP - SAN-IDC

Registry name: SAN-AS-AP - SAN-IDC, TH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS135290, 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.212.180.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
2404:b680::/32 Valid RIR databaseAPNIC, RADB 632 99% 70
103.212.180.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4
103.212.181.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4
103.212.182.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4
103.212.183.0/24 Valid RIR databaseAPNIC, RADB 6 1%low visibility 4

AS-SET

AS135290 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS135290 is announced.

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.