JSC TC Megapolis
JSC TC "Megapolis"
Data as of 2026-07-26
BGP inherited
Limited data: only 2 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 2 · 256 IPv4 addresses |
| IPv6 | 1 prefix (largest 2001:678:630::/48) |
| Cluster ID | 213404600 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 91.223.108.0/24 | JSC TC "Megapolis" | RIPE | ASSIGNED PI | ● high |
| 2001:678:630::/48 | JSC TC "Megapolis" | RIPE | ASSIGNED PI | ● high |
IPv6 ranges (1)
| CIDR |
|---|
| 2001:678:630::/48 |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ORG-ZTCM1-RIPE
RIPE-NCC-END-MNT
ROSPRINT-NCC
TCMEGAPOLIS-MNT