Request focus
What strong requests include
Riga requests should name the Delska or Tet facility, confirm the local access procedure, and flag any high-density, cross-connect, or after-hours dependencies before dispatch.
Smart hands · remote hands · Riga
Datacenter smart hands in Riga, Latvia
TYTEC coordinates datacenter smart hands and structured onsite execution across Riga. The city's mix of enterprise colocation, an underground facility, and newly operational high-density capacity makes exact campus, building, rack, power, and access details essential before dispatch.
TYTEC.ai and TYTEC.se
This TYTEC.ai page is the canonical operational source for Riga. TYTEC.se remains TYTEC AB's company, trust, and formal inquiry site.
Riga operating context
The operational midpoint of the Baltic infrastructure corridor
City-specific context for infrastructure teams planning smart hands, remote hands, rack work, and controlled field changes.
Riga is the central metro in a north-south Baltic operating plan. Delska's network links Tallinn and Vilnius onward to Warsaw, Berlin, and Frankfurt, while the local facility market spans conventional enterprise footprints, physically distinct campuses, and infrastructure designed for AI and HPC density.
Several Delska facilities share the Čuibes iela campus, so an operator name alone is not a usable dispatch address. Strong requests identify LV DC1 or LV DC2 explicitly, state whether the task touches standard or high-density power, and confirm the exact security and loading path.
TYTEC uses these facility references for accurate scoping and routing. They are independent operator sites; publication here does not imply ownership, permanent staffing, or unrestricted access.
Tier 1 operating stance
Operational context for Riga
Riga is a central Baltic infrastructure market and the midpoint of the regional fiber corridor linking Tallinn, Vilnius, Warsaw, and northern Europe.
Execution fit
Where this node is strongest
- Delska's EU North Riga campus provides multiple facilities for enterprise, high-density, AI, and HPC-oriented infrastructure.
- The city sits on the Baltic Highway route between Tallinn, Vilnius, Warsaw, Berlin, and Frankfurt.
- Riga is a practical coordination point for work that spans Latvia and the broader Baltic region.
Datacenter context
Datacenters in and around Riga
Relevant colocation and interconnection references for Riga include Delska EU North Riga LV DC1, Delska EU North Riga LV DC2, Delska EU North Riga LV DC3, Tet Dattum. This is contextual market information for routing and engagement, not a claim that TYTEC operates those sites.
Facility reference layer
4 mapped facilities across 2 operators
- 0 TYTEC facility pages available
- 4 external facility sources linked
- 0 references currently resolved through city-node context
Routing use
How these references are used
- Validate facility naming before dispatch and reduce site ambiguity
- Clarify whether the operator has a TYTEC facility page, an external source, or only city-level context
- Support better request scoping for campus, room, cage, and rack handoff
Datacenter reference
Delska EU North Riga LV DC1
Delska's operational 10 MW, 1,000-rack facility is designed for enterprise, AI, and HPC workloads, with standard racks up to 20 kW and engineered high-density options up to 250 kW per rack.
Čuibes iela 17, Riga, LV-1063, Latvia
Datacenter reference
Delska EU North Riga LV DC2
On the same Čuibes iela campus, LV DC2 provides 2 MW and 240 racks for enterprise colocation, with up to 10 kW per rack and infrastructure built in accordance with EN 50600 Class 3.
Čuibes iela 17, Riga, LV-1063, Latvia
Datacenter reference
Delska EU North Riga LV DC3
LV DC3 is Delska's underground Riga facility: a 1 MW, 80-rack site designed to EN 50600-2 with an emphasis on physical security.
Jāņa Asara iela 24, Riga, LV-1009, Latvia
Datacenter reference
Tet Dattum
Tet identifies Dattum at Kleistu iela 5 as part of its Riga datacenter and cloud portfolio. Treat Tet access, service boundaries, and the exact work location as separate intake items.
Kleistu iela 5, Riga, Latvia
Regional identity
Baltic reach, Nordic coordination
Riga is one of TYTEC's three published Baltic operating nodes, connected to Tallinn, Riga, Vilnius, Helsinki, Stockholm, and Warsaw planning routes.
Services
Riga smart hands and remote hands services
These are the strongest Riga use cases. Every task remains subject to scope, facility rules, access, and technician confirmation.
- Smart hands diagnostics for power, hardware, cabling, and console state
- Remote hands with ordered execution and a decision-ready evidence pack
- Copper, fiber, and cross-connect support where the operator permits it
- Rack deployment support for enterprise, GPU, AI, and HPC infrastructure
- Component swaps, structured break-fix triage, and remote engineering bridges
- Baltic rollout coordination across Riga, Tallinn, Vilnius, and Warsaw
Coverage model
How this node is operated
Coverage type, team status, and language support are shown in the node console and hero. This section defines what the operating model means in practice.
Riga is a strategic TYTEC market coordinated through regional dispatch. Facility identity, access, power context, task risk, and the evidence package are validated before the local execution path is confirmed.
Required inputs
What to send for Riga dispatch
Use this Riga intake list to prevent facility ambiguity and reduce avoidable dispatch delay.
- Exact Riga facility code and address—operator name alone is insufficient on shared campuses
- Hall, cage, rack, RU, power feed, and both endpoints for any connectivity change
- Visitor approval, named escort, security procedure, and loading or delivery constraints
- EET/EEST work window, workload risk, change freeze, and rollback authority
- Approved MOP with separate instructions for standard or high-density equipment
- Evidence matrix covering photos, serials, ports, power state, and final acceptance
After-hours
After-hours support in Riga
After-hours feasibility depends on the named facility, approved access, technician availability, and an authorized remote decision path.
For Riga after-hours work, identify LV DC1, LV DC2, LV DC3, Dattum, or the exact alternative site; include local EET/EEST timing, campus entry instructions, escort status, bridge contact, and rollback authority.
Riga FAQ
Datacenter smart hands questions
Direct answers for teams preparing a Riga field-support request.
Can TYTEC support high-density datacenter work in Riga?
TYTEC can scope guided onsite tasks for high-density environments when the operator permits the work and the customer supplies an approved MOP, equipment requirements, access path, remote engineering contact, and clear stop conditions.
Why must a Riga request include the facility code?
Delska LV DC1 and LV DC2 share the Čuibes iela campus, while LV DC3 and Tet Dattum are separate locations. The facility code prevents the wrong access, loading, or technical assumptions from entering the dispatch.
Can Riga be coordinated as part of a Baltic rollout?
Yes. Riga is a practical midpoint for programs spanning Tallinn, Vilnius, and Warsaw. TYTEC scopes each site separately, then aligns work windows, evidence, escalation, and handoff across the program.
Example request
Copy-paste request template
Use this format when opening a formal request. It makes the TYTEC operating model explicit and reduces handoff friction.
Subject: Riga | Remote hands | <site> | <rack> | <date/time local> City node: Riga Site / facility: <facility name> (<address>) Location: <room/hall/cage/rack> Task: <one sentence> Steps / MOP: <link or attached> Access: <badge/escort/loading/security> Evidence needed: <photos/serials/labels/console outputs> Escalation: <name + phone + email> Close-out format: <single summary + evidence bundle>
Evidence standards
Riga close-out evidence
Evidence is part of the Riga deliverable and should be approved before physical work begins.
- Confirm the facility code in the first close-out line to prevent Riga campus ambiguity
- Capture rack, asset, serial, cable, and power-feed identifiers before execution
- For high-density work, record only approved power and cooling observations—never infer capacity
- Timestamp each state change and document the remote approver for any deviation
- Return completed steps, exceptions, rollback status, and a structured evidence bundle
Regional node console
Riga node ready
Use the command router for a short operational readout, then continue into the local node profile below.
NODE: RIGA REGION: EUROPE FACILITY MAP: 4 VERIFIED FACILITY REFERENCES COVERAGE: STRATEGIC DISPATCH: REGIONAL DISPATCH LANGUAGES: ENGLISH / LATVIAN READY: LOCAL CAPABILITY PROFILE ONLINE
tytec.ai/cities> load-node riga --tier 1 --coverage strategic
Dispatch path
Riga work is routed through TYTEC regional dispatch after the exact facility, access method, density or power context, work window, and close-out expectations are confirmed.
Regional context
Latvia's central datacenter market and the midpoint of the Baltic corridor, with enterprise colocation, an underground facility, and high-density AI/HPC capacity.
Command router
Riga command surface
Type a command or use the chips below to load node status, geo, service, facility, and dispatch views for Riga.
Formal intake
How to send the request
Send the formal request via TYTEC.se/contact, reference the Riga node, and include the structured request template above.
Related cities
Related nodes
Use related nodes when a runbook spans multiple metros or when the nearest viable execution path sits outside a single city.