JSC TimeWeb
Cluster stats
| Netblocks | 30 |
| All fragments | 26,741 blocks across 11,731 clusters |
| Cluster ID | 191871573 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
30
0 netblocks since 2026-07-05
2026-07-05
peak 30
2026-07-06
IP Ranges (30)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 31.28.18.212/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 31.28.19.33/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 62.89.200.148/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 80.81.195.23/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 80.249.215.13/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 109.239.136.74/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 109.239.137.8/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 178.18.225.33/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 178.18.225.197/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 185.0.14.71/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 185.1.152.66/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 193.106.113.159/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 193.106.113.167/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 193.239.119.210/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 193.239.119.240/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 195.208.209.212/32 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8::23a3:0:1/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:1::a500:9123:1/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a500:9123:1/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a500:9123:2/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:20:101::209:212/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:e6::23a3:1/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::136:74/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2001:b28:3ff::137:8/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a00:13c0:3:1::1f1c:1321/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a00:13c0:3:2::1f1c:12d4/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a00:1b30::a159/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a00:1b30::a167/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:33/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
| 2a03:5f80:4::225:197/128 | JSC TimeWeb | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
60.0%
of checked blocks have valid RPKI ROA coverage
(18 of 30)
No discrepancies found among checked blocks.
NIC Handles
AS9123