bgpreport

Network · data from 2026-11-12

AS150300 TPSMOTOT-AS-AP - The Permanent Secretary, Ministry of Transport of Thailand

Registry name: TPSMOTOT-AS-AP - The Permanent Secretary, Ministry of Transport of Thailand, TH · not in PeeringDB

4IPv4 routes 75.0% 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
4Route objects not announced registered with origin AS150300, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS150300, 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.215.232.0/23 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
87.124.91.0/24 Valid RIR databaseAPNIC 672 100% 66
87.124.92.0/24 Valid RIR databaseAPNIC 672 100% 66
87.124.93.0/24 Valid RIR databaseAPNIC 672 100% 66

AS-SET

AS150300 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 6 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none103.215.232.0/23No ROA covers it. Add a ROA for AS150300, maxLength 23.672 of 673
Route object: RIR103.215.232.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

43.249.63.0/24APNIC, RADBValid
103.215.232.0/24NTTCOM, RADBNo ROA
103.215.233.0/24NTTCOM, RADBNo ROA
2001:df1:3ec0::/48RADBNo 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.