JT_MOBILE_CORE
Data as of 2026-08-16
Handle
Cluster stats
| Netblocks | 6 · 3,584 IPv4 addresses |
| Cluster ID | 223917917 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 · report an issue | |
Footprint over time
7 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-08-16
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 37.156.38.0/24 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
| 37.156.39.0/24 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
| 87.237.128.0/22 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
| 87.237.132.0/22 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
| 185.158.120.0/23 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
| 185.158.122.0/23 | JT_MOBILE_CORE | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
RPKI-inferred operator
JT (Jersey) Limited
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
JE-TEL-MNT