Summary

  • WTC Moscow presents itself as a multifunctional business complex. RIPE separately identifies the company as the holder of AS39376 and the 62.148.0.0/19 IPv4 allocation.
  • A dated RIPEstat view showed 32 IPv4 announcements covering the same 8,192 addresses, two observed neighbours and no announced IPv6 space. Those facts describe public routing, not end-to-end continuity for tenants.

One front door, several control boundaries

The appeal of a business complex is coordination. Offices, meetings, hospitality and supporting services can be obtained within one estate. WTC Moscow’s own brochure describes a multifunctional complex and business-centre services. That is a useful statement about the commercial setting, but it says nothing by itself about the independence of fibre entrances, power systems, upstream carriers, DNS, applications or support teams.

This distinction matters because a tenant often encounters one service desk and one location while depending on several operators. A building owner may control risers and access rules. A network team may control routers and address space. Carriers may control upstream paths. Software suppliers may control authentication or collaboration systems. If contracts do not name those boundaries, integration can turn a fault into a search for responsibility.

The registry evidence maps one part of the picture. RIPE organisation ORG-JCWT1-RIPE identifies PUBLIC JOINT-STOCK COMPANY WORLD TRADE CENTER MOSCOW as a Russian Local Internet Registry. RIPE assigns AS39376, named WTCMOSCOW-NET-AS, to that organisation. The registered policy names AS3216 for import and export. The company also holds allocation 62.148.0.0/19, an IPv4 block of 8,192 addresses.

At 16:00 UTC on 5 September 2026, RIPEstat observed 32 IPv4 announcements covering 8,192 addresses, no announced IPv6 space and two neighbours. The route list consisted of the covering /19 plus 31 constituent /24s, all continuously visible in the captured two-week window. The neighbour view observed AS196695 and AS3216 on one side of AS39376.

The arithmetic must not be overread. Thirty-two announcements are not 32 independent networks, paths, sites or power domains. The public data does not explain why the more-specific routes exist or whether they receive distinct treatment. Likewise, two observed neighbours do not prove two physically diverse circuits. They may still share ducts, entrances, facilities, equipment, power or operational staff.

One positive control is visible. RIPEstat returned the /19 origin by AS39376 as RPKI valid under a matching route-origin authorisation with maximum length /19. That supports the authority of AS39376 to originate the covering route. It does not validate the /24 announcements under that ROA, whose maximum length is /19, and it does not establish service availability, path separation or recovery time.

The useful due-diligence question is therefore not whether WTC Moscow “has a network.” It is which party controls each dependency for the tenant’s exact service. Evidence should identify the building demarcation, fibre entrances, active and standby upstreams, power autonomy, escalation owners, restoration targets and compensation terms. It should also state whether internet access, voice, event systems and critical building services share equipment or recovery teams.

Public sources do not supply that operating map. They establish identity, allocation, registered policy and a dated routing observation. Physical diversity, capacity headroom, failover tests, tenant-level SLA performance and incident ownership remain unknown. That boundary is the conclusion, not a deficiency to fill with assumptions.

Sources