JT-MCP
Handle
Cluster stats
| Netblocks | 6 |
| All fragments | 12 blocks across 7 clusters |
| Cluster ID | 193006087 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 46.31.246.0/23 | JT-MCP | RIPE | ASSIGNED PA | ● low |
| 92.43.208.0/23 | JT_MCP | RIPE | ASSIGNED PA | ● low |
| 92.43.211.0/24 | JT-MCP | RIPE | ASSIGNED PA | ● low |
| 195.226.132.0/24 | JT-MCP | RIPE | ASSIGNED PA | ● low |
| 195.226.146.0/24 | JT-MCP | RIPE | ASSIGNED PA | ● low |
| 195.226.153.0/24 | JT-MCP | 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
WAVE-TEL-MNT