Permanent-Mission-of-Singapore

BGP inherited

Cluster stats

Netblocks	1
All fragments	13 blocks across 7 clusters
Cluster ID	204771876
Registry	RIPE
Customers	find customers using this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 3 shared RIR contact/maintainer handles
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
212.186.232.104/29	Permanent-Mission-of-Singapore	RIPE	ASSIGNED PA	● medium

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Permanent Mission of” — 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.

PERMANENT-MISSION-OF-ROMANIA 3 blocks
Permanent-Mission-of-Turkey 3 blocks
PERMANENT_MISSION_OF_VENEZUELA_TO_THE_OP 2 blocks
Permanent-Mission-of-China 2 blocks
Permanent-Mission-of-the 1 blocks
PERMANENT-MISSION-OF-SLOVENIA 1 blocks

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.

Permanent-Mission-of-the via T-Mobile Austria GmbH sub-allocation
Embassy And Permanent Mission via COLT Technology Services Group Limited sub-allocation
Botschaft-Permanent-Mission via T-Mobile Austria GmbH sub-allocation
Mission Permanente Autriche Aupres Ocd via Orange S.A. sub-allocation
PERMANENT-MISSION-OF-SLOVENIA via T-Mobile Austria GmbH sub-allocation
MISSION-PERMANENTE-DU-JAPON-NET via Swisscom (Schweiz) AG sub-allocation
Mission Permanente Rep Slovaqu via Orange S.A. sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PRIO-MNT