OGPS-GO-LAN

BGP inherited

Cluster stats

Netblocks	9
All fragments	10 blocks across 2 clusters
Cluster ID	210487678
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

Footprint over time

5 weekly snapshots · JSON

9 0 netblocks since 2026-07-05

2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
84.204.134.196/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
84.204.140.240/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
84.204.140.244/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
84.204.140.248/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
84.204.140.252/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
93.153.148.84/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
93.153.148.240/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
109.124.110.152/29	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low
212.44.67.84/30	OGPS-GO-LAN	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “OGPS GO” — 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.

OGPS-GO-LAN2-LAN 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.

EQUIPAMIENTOGPSAURIAGASL via TELEFONICA DE ESPANA S.A.U. sub-allocation
STUDIOGPSSRL sub-allocation
OGPS-GO-LAN2-LAN via PJSC MegaFon sub-allocation
TAIPOGPS-HK sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE PSTAR-MNT