ROYAL-THAI-EMBASSY

BGP inherited
Cluster stats
Netblocks5
Registered in India (2) · Czechia (1) · United Kingdom (1)
All fragments 2,202 blocks across 6 clusters
Cluster ID215266961
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.20.71.16/28 ROYAL-THAI-EMBASSY RIPE ASSIGNED PA ● low
122.160.178.168/30 ROYAL_THAI_EMBASSY APNIC ALLOCATED NON-PORTABLE ● low
122.160.183.88/29 ROYAL_THAI_EMBASSY APNIC ALLOCATED NON-PORTABLE ● low
212.24.151.152/30 Royal-Thai-Embassy RIPE ASSIGNED PA ● low
2a00:2381:f5eb::/48 ROYAL-THAI-EMBASSY RIPE AGGREGATED-BY-LIR ● low

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (5 of 5)
Possible discrepancies (1)

These blocks are registered to ROYAL-THAI-EMBASSY but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:2381:f5eb::/48 /48 authorized for AS2856 — British Telecommunications Limited

NIC Handles

AS5089-MNT BTNET-MNT DEL2-AP DEL2-AP DIALTELECOM-MNT DUMY-RIPE DUMY-RIPE MAINT-IN-TELEMEDIA