Network · data from 2026-11-12

AS56120 TOT-MOBILE-AS-AP - TOT Public Company Limited

Registry name: TOT-MOBILE-AS-AP - TOT Public Company Limited, TH · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

28Route objects not announced registered with origin AS56120, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56120, 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.


1.20.127.0/24	No ROA	Other IRR onlyRADB	671 100%	66
1.20.123.0/24	Valid	RIR databaseAPNIC	671 100%	66
1.20.126.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	66

AS-SET

AS56120 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 30 are in fix.csv.

ROA: none1
Route object: RIR1
Route object: not announced28

Change	Prefix or set	Detail	Full-table peers
ROA: none	1.20.127.0/24	No ROA covers it. Add a ROA for AS56120, maxLength 24.	671 of 673
Route object: RIR	1.20.127.0/24	Route object only in RADB. Add it in the RIR database for the space.	671 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

1.20.127.0/24

No ROA covers it. Add a ROA for AS56120, maxLength 24.

671 of 673

Route object: RIR

1.20.127.0/24

Route object only in RADB. Add it in the RIR database for the space.

671 of 673

Route objects not announced

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


1.20.0.0/17	RADB	No ROA
1.20.0.0/18	RADB	No ROA
1.20.0.0/24	APNIC, RADB	Valid
1.20.1.0/24	APNIC, RADB	Valid
1.20.2.0/24	APNIC	Valid
1.20.3.0/24	APNIC	Valid
1.20.4.0/22	APNIC	Valid
1.20.8.0/21	APNIC	Valid
1.20.16.0/20	APNIC	Valid
1.20.32.0/20	APNIC	Valid
1.20.48.0/21	APNIC, RADB	Valid
1.20.56.0/22	APNIC	Valid
1.20.60.0/24	APNIC	Valid
1.20.61.0/24	APNIC	Valid
1.20.62.0/24	APNIC	Valid
1.20.63.0/24	APNIC	Valid
1.20.64.0/24	APNIC	Valid
1.20.65.0/24	APNIC	Valid
1.20.66.0/24	APNIC	Valid
1.20.117.0/24	APNIC, RADB	Valid
1.20.119.0/24	APNIC, RADB	Valid
1.20.120.0/24	APNIC, RADB	Valid
1.20.121.0/24	APNIC, RADB	Valid
1.20.122.0/24	APNIC	Valid
1.20.125.0/24	APNIC, RADB	Valid
180.210.216.0/22	RADB	No ROA
180.210.217.0/24	NTTCOM, RADB	No ROA
180.210.219.0/24	NTTCOM, RADB	No ROA

1.20.0.0/17

RADB

No ROA

1.20.0.0/18

RADB

No ROA

1.20.0.0/24

APNIC, RADB

Valid

1.20.1.0/24

APNIC, RADB

Valid

1.20.2.0/24

APNIC

Valid

1.20.3.0/24

APNIC

Valid

1.20.4.0/22

APNIC

Valid

1.20.8.0/21

APNIC

Valid

1.20.16.0/20

APNIC

Valid

1.20.32.0/20

APNIC

Valid

1.20.48.0/21

APNIC, RADB

Valid

1.20.56.0/22

APNIC

Valid

1.20.60.0/24

APNIC

Valid

1.20.61.0/24

APNIC

Valid

1.20.62.0/24

APNIC

Valid

1.20.63.0/24

APNIC

Valid

1.20.64.0/24

APNIC

Valid

1.20.65.0/24

APNIC

Valid

1.20.66.0/24

APNIC

Valid

1.20.117.0/24

APNIC, RADB

Valid

1.20.119.0/24

APNIC, RADB

Valid

1.20.120.0/24

APNIC, RADB

Valid

1.20.121.0/24

APNIC, RADB

Valid

1.20.122.0/24

APNIC

Valid

1.20.125.0/24

APNIC, RADB

Valid

180.210.216.0/22

RADB

No ROA

180.210.217.0/24

NTTCOM, RADB

No ROA

180.210.219.0/24

NTTCOM, RADB

No 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.