Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Equinix Metal

    52 incidentes de Equinix Metal registrados desde abril de 2025, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    SV Metro Connectivity Issues

    Comenzó 17 de agosto de 2026 a las 15:38 UTC · 1h 33m

    OutageIncidente crítico
    Componentes afectados
    Silicon Valley (SV)
    1. 17 de agosto de 2026 a las 15:38 UTCinvestigating

      Hemos experimentado un nivel de outage que afecta a todos los servidores de clientes en el metro SV. Los ingenieros están investigando.

    2. 17 de agosto de 2026 a las 16:39 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    3. 17 de agosto de 2026 a las 17:10 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    AT INCIDENT INC0258173 MC DOWN

    Comenzó 30 de junio de 2026 a las 3:59 UTC · 1h 22m

    OutageIncidente mayor
    Componentes afectados
    Equinix Metal NetworkAtlanta (AT)
    1. 30 de junio de 2026 a las 3:59 UTCinvestigating

      Todos los enlaces entre AT4 y AT1 (PoP) están bajos. Como resultado, AT4 está actualmente aislado del resto de la red.

    2. 30 de junio de 2026 a las 4:05 UTCinvestigating

      Seguimos investigando esta cuestión.

    3. 30 de junio de 2026 a las 4:10 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    4. 30 de junio de 2026 a las 4:10 UTCmonitoring

      Continuamos monitoreando cualquier otro problema.

    5. 30 de junio de 2026 a las 5:21 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    PA Principal Interconnection Connectivity Issue

    Comenzó 25 de junio de 2026 a las 0:11 UTC · 1h 57m

    IssuesIncidente menor
    Componentes afectados
    Paris (PA)Equinix Metal Network
    1. 25 de junio de 2026 a las 0:11 UTCinvestigating

      Equinix Metal ha experimentado una falla que está afectando las interconexiones de tejido compartido en el metro de París. Los clientes con interconexiones redundantes están experimentando impacto a circuitos virtuales secundarios solamente. Los circuitos virtuales primarios de Redundant permanecen en funcionamiento. Los clientes con interconexiones no redundantes pueden experimentar un impacto mixto en sus circuitos virtuales. Por favor contacte a [email protected] con cualquier pregunta.

    2. 25 de junio de 2026 a las 0:14 UTCidentified

      Esto está relacionado con el incidente de refrigeración de Equinix INC0251416

    3. 25 de junio de 2026 a las 1:22 UTCmonitoring

      Se ha aplicado una solución y estamos monitoreando los resultados.

    4. 25 de junio de 2026 a las 2:08 UTCresolved

      Este incidente ha sido resuelto.

    Traducido automáticamente desde la actualización oficial del incidente.

    Down Fabric circuit on FR Metro

    Comenzó 9 de mayo de 2026 a las 6:10 UTC · 1d 17h

    Pending
    Componentes afectados
    Frankfurt (FR)
    1. 9 de mayo de 2026 a las 7:20 UTCinvestigating

      This is related to Maintenance of EQX CHG0125681.

    2. 9 de mayo de 2026 a las 7:21 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 9 de mayo de 2026 a las 20:32 UTCidentified

      We are currently working with our fiber provider to fully restore services. Customers with only primary ports at this time are impacted. Any customers with primary and secondary services will experience loss of redundancy

    4. 10 de mayo de 2026 a las 23:35 UTCresolved

      This incident has been resolved.

    Brief Network Disruption – Chicago (CH3)

    Comenzó 14 de abril de 2026 a las 16:25 UTC · 22m

    IssuesIncidente menor
    Componentes afectados
    Chicago (CH)Equinix Metal Network
    1. 14 de abril de 2026 a las 16:25 UTCinvestigating

      One of the network devices in Chicago (CH3) experienced an unexpected restart. The device has fully recovered, and all services are currently operating normally. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 14 de abril de 2026 a las 16:27 UTCidentified

      Customers in this rack with bonded interfaces should have only encountered a loss in redundancy and available through-put for their uplinks. Customers in an unbonded configuration, may have experienced some packet loss while the device recovered.

    3. 14 de abril de 2026 a las 16:48 UTCresolved

      At this time the device has recovered and MLAG bonds have been restored. The device has fully recovered, and all services are currently operating normally.

    PA Shared Interconnection Connectivity Issue

    Comenzó 6 de abril de 2026 a las 8:16 UTC · 7m

    IssuesIncidente menor
    Componentes afectados
    Paris (PA)Equinix Metal Network
    1. 6 de abril de 2026 a las 8:16 UTCinvestigating

      We are currently investigating a shared interconnection affecting some users on primary circuits in PA Metro. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 6 de abril de 2026 a las 8:20 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 6 de abril de 2026 a las 8:20 UTCmonitoring

      We are continuing to monitor for any further issues.

    4. 6 de abril de 2026 a las 8:23 UTCresolved

      This incident has been resolved.

    SV Metro Isolation

    Comenzó 6 de febrero de 2026 a las 12:34 UTC · 1h 14m

    OutageIncidente mayor
    Componentes afectados
    Silicon Valley (SV)
    1. 6 de febrero de 2026 a las 12:34 UTCinvestigating

      We are currently investigating an incident that impacted our Silicon Valley metro. Customers may have experienced a loss of connectivity during this issue.

    2. 6 de febrero de 2026 a las 12:44 UTCinvestigating

      We are continuing to investigate this issue.

    3. 6 de febrero de 2026 a las 12:46 UTCidentified

      We have identified the issue and it has stabilized on its own. We are still investigating the root cause.

    4. 6 de febrero de 2026 a las 13:01 UTCmonitoring

      At this time connectivity has remained stable and we are continuing to monitor.

    5. 6 de febrero de 2026 a las 13:47 UTCresolved

      This incident has been resolved.

    Packet Loss DC And SV Metro

    Comenzó 28 de enero de 2026 a las 16:33 UTC · 0m

    Pending
    Componentes afectados
    Equinix Metal NetworkSilicon Valley (SV)Washington DC (DC)
    1. 28 de enero de 2026 a las 16:33 UTCresolved

      Our monitoring systems detected DDoS attack patterns in SV metro (1200 - 1204 UTC) and DC metro (1208 - 1211 UTC) which caused brief period of packet loss while mitigation measures were activated. Traffic levels then stabilized to normal levels.

    DC10 Network Connectivity Issue

    Comenzó 22 de enero de 2026 a las 11:07 UTC · 2h 5m

    IssuesIncidente menor
    Componentes afectados
    Equinix Metal NetworkWashington DC (DC)
    1. 22 de enero de 2026 a las 11:07 UTCinvestigating

      We have identified an issue at our DC10 Facility, which impacted network stability in a limited number of hosts. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 22 de enero de 2026 a las 12:31 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 22 de enero de 2026 a las 12:52 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 22 de enero de 2026 a las 13:11 UTCresolved

      This incident has been resolved.

    Metadata service degradation in some facilities

    Comenzó 21 de enero de 2026 a las 12:20 UTC · 2h 13m

    Pending
    Componentes afectados
    Stockholm (SK)Paris (PA)Helsinki (HE)Frankfurt (FR)Madrid (MD)Device ProvisioningEquinix Metal APILondon (LD)Amsterdam (AM)
    1. 21 de enero de 2026 a las 12:20 UTCidentified

      We have identified an issue affecting the metadata service in select Equinix Metal facilities, including Amsterdam, Madrid, and Frankfurt. This issue may cause certain provisioning and deprovisioning operations to fail. Our engineering teams are actively working on implementing a fix.

    2. 21 de enero de 2026 a las 12:34 UTCidentified

      We are continuing to work on a fix for this issue.

    3. 21 de enero de 2026 a las 14:34 UTCresolved

      This incident has been resolved.

    SY4 Network Connectivity Issue

    Comenzó 20 de enero de 2026 a las 23:38 UTC · 18m

    Pending
    Componentes afectados
    Equinix Metal Network
    1. 20 de enero de 2026 a las 23:38 UTCmonitoring

      On January 20th, 2026 at 21:47 UTC, Equinix Metal customers with instances in Metro: SY4 Pod: 1 Rack: 15 may have experienced localized degradation or outage affecting network services. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 20 de enero de 2026 a las 23:55 UTCresolved

      This incident has been resolved.

    SV15 and SV16 outage

    Comenzó 15 de enero de 2026 a las 7:05 UTC · 59m

    OutageIncidente crítico
    Componentes afectados
    Silicon Valley (SV)
    1. 15 de enero de 2026 a las 7:05 UTCinvestigating

      We are currently investigating this issue.

    2. 15 de enero de 2026 a las 7:06 UTCidentified

      Equinix Metal has experienced a facility-wide outage that has affected all customer servers in our SV facilities. 3:03

    3. 15 de enero de 2026 a las 7:14 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 15 de enero de 2026 a las 8:04 UTCresolved

      This incident has been resolved.

    Customer provisioning issue in Silicon Valley Metro

    Comenzó 23 de diciembre de 2025 a las 16:14 UTC · 1h 0m

    Pending
    Componentes afectados
    Equinix Metal NetworkSilicon Valley (SV)
    1. 23 de diciembre de 2025 a las 16:14 UTCinvestigating

      We are currently addressing an issue with a switch that is part of a redundant pair in our Silicon Valley metro and will be performing emergency maintenance. This switch connects to customer facing servers and will require a reboot. Customers with servers in this rack will experience one of their physical ports dropping during the reload. Customers with split bond configurations may experience their servers going offline during this maintenance.

    2. 23 de diciembre de 2025 a las 17:14 UTCresolved

      This incident has been resolved.

    DC1 | Equinix Maintenance CHG0111322

    Comenzó 19 de diciembre de 2025 a las 7:57 UTC · 2h 4m

    Pending
    Componentes afectados
    Equinix Metal NetworkWashington DC (DC)
    1. 19 de diciembre de 2025 a las 7:57 UTCinvestigating

      We are currently investigating this issue.

    2. 19 de diciembre de 2025 a las 8:14 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 19 de diciembre de 2025 a las 8:24 UTCmonitoring

      We are tracking an ongoing Equinix Maintenance activity (CHG0111322) for the DC Metro Area. Our engineers are actively monitoring the situation and coordinating with the maintenance team to ensure service stability. We will continue to provide updates as the maintenance progresses. Thank you for your patience and understanding.

    4. 19 de diciembre de 2025 a las 10:01 UTCresolved

      This incident has been resolved.

    DC13 Network Connectivity Issue

    Comenzó 2 de diciembre de 2025 a las 2:47 UTC · 1h 20m

    IssuesIncidente menor
    Componentes afectados
    Equinix Metal NetworkWashington DC (DC)
    1. 2 de diciembre de 2025 a las 2:47 UTCinvestigating

      We have identified an issue affecting one of our backbone routers at our DC13 Facility, which impacted network stability in a limited number of hosts. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 2 de diciembre de 2025 a las 2:48 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 2 de diciembre de 2025 a las 3:38 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 2 de diciembre de 2025 a las 4:08 UTCresolved

      This incident has been resolved.

    Metal API Issue

    Comenzó 18 de noviembre de 2025 a las 14:26 UTC · 5h 25m

    OutageIncidente crítico
    Componentes afectados
    Equinix Metal API
    1. 18 de noviembre de 2025 a las 14:26 UTCinvestigating

      We are currently experiencing an outage affecting the Equinix Metal API and Console due to a Cloudflare service disruption. Our team is actively monitoring the situation and working to restore functionality as soon as possible.

    2. 18 de noviembre de 2025 a las 15:35 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    3. 18 de noviembre de 2025 a las 19:51 UTCresolved

      This incident has been resolved.

    Primary and Secondary Metal port impacted

    Comenzó 14 de noviembre de 2025 a las 12:04 UTC · 47m

    IssuesIncidente menor
    Componentes afectados
    Frankfurt (FR)Equinix Metal Network
    1. 14 de noviembre de 2025 a las 12:04 UTCinvestigating

      We have experienced a fault impacting Shared Fabric interconnections in the Frankfurt metro. This issue affected both primary and secondary virtual circuits for some customers. If you have any questions or need assistance, please contact us at [email protected].

    2. 14 de noviembre de 2025 a las 12:05 UTCinvestigating

      We are continuing to investigate this issue.

    3. 14 de noviembre de 2025 a las 12:05 UTCidentified

      The issue has been identified and a fix is being implemented.

    4. 14 de noviembre de 2025 a las 12:22 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    5. 14 de noviembre de 2025 a las 12:51 UTCresolved

      This incident has been resolved.

    Connectivity Issue Multiple Metros

    Comenzó 21 de octubre de 2025 a las 10:59 UTC · 4h 5m

    OutageIncidente mayor
    Componentes afectados
    Equinix Metal NetworkNew York (NY)
    1. 21 de octubre de 2025 a las 10:59 UTCinvestigating

      We are currently investigating a connectivity issue affecting stability in NY Metro. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 21 de octubre de 2025 a las 11:27 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 21 de octubre de 2025 a las 12:43 UTCidentified

      Connectivity is confirmed stable since 1046 UTC. There was a major event in the Equinix backbone network which is being investigated as part of a larger global incident.

    4. 21 de octubre de 2025 a las 13:13 UTCmonitoring

      All services remain stable. There has been confirmed mixed impact to Internet and interconnection services in multiple metros. The estimated period of impact is 1032-1047 UTC. Please reach out to [email protected] for further assistance.

    5. 21 de octubre de 2025 a las 15:03 UTCresolved

      All services remain stable and the the issue is deemed resolved. Root cause analysis is ongoing.

    Equinix Console Impact

    Comenzó 17 de octubre de 2025 a las 13:12 UTC · 41m

    OutageIncidente mayor
    Componentes afectados
    Equinix Metal PortalEquinix Metal API
    1. 17 de octubre de 2025 a las 13:46 UTCinvestigating

      We are currently experiencing a major outage affecting the Equinix Console . Please bear with us while we address this issue. Please visit status.equinixmetal.com for further updates or reach out to [email protected] for further assistance.

    2. 17 de octubre de 2025 a las 13:53 UTCresolved

      This incident has been resolved.

    Connectivity issue in Sao Paulo Metro

    Comenzó 16 de octubre de 2025 a las 18:55 UTC · 1h 6m

    Pending
    Componentes afectados
    Equinix Metal NetworkSao Paulo (SP)
    1. 16 de octubre de 2025 a las 18:55 UTCinvestigating

      We are currently investigating an issue in our Sao Paulo metro.

    2. 16 de octubre de 2025 a las 19:06 UTCidentified

      The issue has been identified and a fix is being implemented.

    3. 16 de octubre de 2025 a las 19:29 UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. 16 de octubre de 2025 a las 20:01 UTCresolved

      This incident has been resolved.