GLOVO

BGP inherited

Cluster stats

Netblocks	7
All fragments	8 blocks across 2 clusters
Cluster ID	210240569
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

7 0 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
194.224.32.48/29	GLOVO	RIPE	ASSIGNED PA	● low
195.53.121.184/29	GLOVO	RIPE	ASSIGNED PA	● low
195.53.254.184/29	GLOVO	RIPE	ASSIGNED PA	● low
195.57.18.176/29	GLOVO	RIPE	ASSIGNED PA	● low
195.76.199.128/29	GLOVO	RIPE	ASSIGNED PA	● low
195.77.42.224/29	GLOVO	RIPE	ASSIGNED PA	● low
195.235.52.112/29	GLOVO	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

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

GLOVO_APP_23 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.

Parglovo sub-allocation
Glovoapp23 Sl via COLT Technology Services Group Limited sub-allocation
Mediterranean Shipping Kompani Rus Scheglovo via PJSC MegaFon sub-allocation
Glovoapp23 Sa via COLT Technology Services Group Limited sub-allocation
GLOVO_APP_23 via TELEFONICA DE ESPANA S.A.U. sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

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

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE MAINT-AS3352