Dispatch path
Madrid is handled through TYTEC dispatch with vetted local partner alignment once site, access, and evidence requirements are clear.
regional node
node: madridtier: 2coverage: partner ledstatus: vetted partner
Regional node console
Madrid node ready
Use the command router for a short operational readout, then continue into the local node profile below.
NODE: MADRID REGION: EUROPE FACILITY MAP: 3 VERIFIED FACILITY REFERENCES COVERAGE: PARTNER LED DISPATCH: VETTED PARTNER LANGUAGES: ENGLISH / SPANISH READY: LOCAL CAPABILITY PROFILE ONLINE
tytec.ai/cities> load-node madrid --tier 2 --coverage partner-led
Regional context
Madrid is Spain's primary datacenter and interconnection market, with carrier-neutral facilities and growing relevance for Iberian and southern Europe routing.
Command router
Madrid command surface
Type a command or use the chips below to load node status, geo, service, facility, and dispatch views for Madrid.
Operational city page
TYTEC in Madrid
Madrid is a TYTEC.ai city node for structured datacenter field execution in Spain, operating in partner led mode with vetted partner coordination and support in English and Spanish. Send facility, access, timing, and evidence requirements up front so TYTEC can confirm the dispatch path before work starts. TYTEC.ai is the operational layer; use TYTEC.se/contact for formal intake and reference the Madrid node in your request.
TYTEC.ai and TYTEC.se
TYTEC.ai is the operational engagement layer for Madrid. TYTEC.se remains the main company, trust, and formal inquiry site.
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.
This node is partner-led: TYTEC coordinates the request, confirms site and access details, and aligns vetted local delivery against explicit evidence requirements.
Services
Services this node supports
Use the same structured request model across all TYTEC nodes. Coverage type affects routing, not the clarity of the deliverable.
- Smart hands (guided on-site execution)
- Remote hands (repeatable field actions with evidence)
- Fiber and copper patching (including cross-connect support where permitted)
- Rack and stack (installs, swaps, staged rollouts)
- Break-fix and troubleshooting (hands + eyes, console notes, triage)
- Decommissioning (pulls, labeling, packing, chain-of-custody if required)
Required inputs
What to send before dispatch
Clear inputs produce reliable outputs. This is the fastest way to reduce back-and-forth and confirm the dispatch path.
- Facility or site name (and street address if ambiguous)
- Room / hall / cage / rack identifier
- Task definition and success criteria
- Approved window (local time) and urgency classification
- Access status (badge, pre-approval, escort, loading constraints)
- MOP / runbook link or attached steps (if applicable)
- Evidence requirements (photos, serials, labels, console outputs)
- Escalation contacts (primary + backup) and comms channel
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: Madrid | Remote hands | <site> | <rack> | <date/time local> City node: Madrid 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
What close-out should include
Evidence is part of the deliverable. Requests should define the expected close-out standard before work starts.
- Photos: wide shot for context, then close-ups for labels and ports
- Serial and asset capture: record exact serials for touched hardware
- Before/after: show state change for every action that matters
- Console observations: include timestamps, LEDs, error screens, and anomalies
- Handoff: one-paragraph summary plus evidence pack (zip or shared folder)
After-hours
After-hours dispatch rule set
After-hours requests are viable when access, timing, and evidence expectations are already clear.
After-hours work should include access status, local contact details, urgency, and expected evidence before the request is scheduled.
Datacenter context
Major infrastructure in and around Madrid
Relevant colocation and interconnection references for Madrid include Hispaweb Madrid1, Equinix MD2, Interxion MAD1. This is contextual market information for routing and engagement, not a claim that TYTEC operates those sites.
Facility reference layer
3 mapped facilities across 3 operators
- 0 TYTEC facility pages available
- 3 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
Hispaweb Madrid1
Calle de Miguel Yuste 11, 28037 Madrid, Spain
Datacenter reference
Equinix MD2
Calle de Augusto Rodin 4, 28020 Madrid, Spain
Datacenter reference
Interxion MAD1
Calle de Miguel Yuste 11, 28037 Madrid, Spain
Formal intake
How to send the request
Send the formal request via TYTEC.se/contact, reference the Madrid 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.