Royal Thai Army

BGP inherited
Cluster stats
Netblocks10 · 2,297 IPv4 addresses
All fragments 2,201 blocks across 6 clusters
Cluster ID212123521
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.146.204.0/24 Royal Thai Army BGP ANNOUNCED ● high
103.146.204.0/23 Royal Thai Army BGP ANNOUNCED ● high
103.146.205.0/24 Royal Thai Army BGP ANNOUNCED ● high
103.151.252.0/23 Royal Thai Army APNIC ASSIGNED PORTABLE ● high
103.151.252.0/24 Royal Thai Army BGP ANNOUNCED ● high
103.151.253.0/24 Royal Thai Army BGP ANNOUNCED ● high
110.78.8.0/24 Royal Thai Army BGP ANNOUNCED ● high
2001:df3:c8c0::/48 Royal Thai Army BGP ANNOUNCED ● high
2001:df3:e480::/48 Royal Thai Army BGP ANNOUNCED ● high
2001:df3:e480::/48 Royal Thai Army APNIC ASSIGNED PORTABLE ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Royal Thai” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

what's this?
RPKI hygiene: F how networks compare →
10.0% of checked blocks have valid RPKI ROA coverage (1 of 10)
No discrepancies found among checked blocks.

NIC Handles

APNIC-HM AR829-AP AS140699 MAINT-NTPCL-TH ORG-RTA1-AP RTAA2-AP RTAA2-AP