PLAY2GO - FZCO

ORG-PF140-RIPE
Data as of 2026-09-06
Registry
This organisation
Netblocks16 · 4,096 IPv4 addresses
Record ID240754524
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.27.200.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.201.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.202.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.203.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.204.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.205.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.206.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
2.27.207.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.208.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.209.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.210.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.211.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.212.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.213.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.214.0/24 UNKNOWN RIPE ASSIGNED PA ● medium
177.3.215.0/24 UNKNOWN RIPE ASSIGNED PA ● medium

Footprint over time

3 weekly snapshots · JSON
16 +4 netblocks since 2026-08-23
2026-08-23 peak 16 2026-09-06

Network trust

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

These blocks are registered to PLAY2GO - FZCO 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.

177.3.210.0/24 /24 authorized for AS203154 — MITELIS SECURITY LIMITED

NIC Handles

DUMY-RIPE DUMY-RIPE mitelis-mnt play2go-mnt