UMPLAY TELECOM
Cluster stats
| Netblocks | 18 |
| Cluster ID | 191331188 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 2 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
18
0 netblocks since 2026-07-05
2026-07-05
peak 18
2026-07-06
IP Ranges (18)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.72.97/32 | UMPLAY TELECOM | PEERINGDB | ASSIGNED | ● high |
| 170.84.76.0/22 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 170.84.76.0/24 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 170.84.77.0/24 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 170.84.78.0/24 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 170.84.79.0/24 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 187.16.212.250/32 | UMPLAY TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8::212:250/128 | UMPLAY TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:9::97/128 | UMPLAY TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2804:3130::/32 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 2804:3130::/34 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 2804:3130:4000::/34 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 2804:3130:8000::/34 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 2804:3130:c000::/34 | UMPLAY TELECOM | BGP | ANNOUNCED | ● high |
| 170.84.78.0/28 | UNKNOWN | LACNIC | reassigned | ● medium |
| 170.84.78.24/29 | UNKNOWN | LACNIC | reassigned | ● medium |
| 2804:3130::/32 | UNKNOWN | LACNIC | allocated | ● medium |
| 2804:3130:100::/40 | UNKNOWN | LACNIC | reassigned | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(18 of 18)
No discrepancies found among checked blocks.
NIC Handles
AS264999
AS264999