Historial de interrupciones de Spark

1. September 1, 2026 at 8:48 PM UTCinvestigating

   Componente afectado: Conectividad de dispositivo de taquión (SKUs: TACH4NA, TACH8NA, TACH8ROW) Inicio: Hoy, 22 PM PDT Descripción: Actualmente estamos investigando una perturbación de conectividad que afecta a los dispositivos Tachyon (SKUs TACH4NA, TACH8NA, TACH8ROW). El equipo de partículas está investigando activamente la cuestión y publicará actualizaciones a medida que se disponga de más información. Ningún otro tipo de dispositivo de partículas o SKU se ve afectado por este incidente.

2. September 1, 2026 at 9:14 PM UTCidentified

   Hemos identificado la causa de la perturbación de conectividad que afecta a los dispositivos Tachyon. Nuestro equipo está trabajando activamente en una solución para resolver el problema. Seguiremos publicando actualizaciones a medida que se avance. Ningún otro tipo de dispositivo de partículas o SKU se ve afectado por este incidente.

3. September 1, 2026 at 9:43 PM UTCmonitoring

   Hemos observado dispositivos recuperando y reconectando. Nuestro equipo sigue monitoreando la recuperación para asegurar la estabilización completa en los dispositivos Tachyon restantes. Proporcionaremos una actualización final una vez que todos los dispositivos estén completamente conectados y el incidente se resuelva.

4. September 1, 2026 at 11:01 PM UTCresolved

   Este incidente ha sido resuelto. Todos los dispositivos Tachyon han reconectado con éxito y la conectividad ha sido completamente restaurada. Nuestro equipo identificó la causa raíz e implementó una solución, confirmando la recuperación completa en toda la flota afectada. Ningún otro tipo de dispositivo de partículas o SKU fue afectado por este incidente.

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

1. September 1, 2026 at 5:40 PM UTCinvestigating

   Componente afectado: Conectividad de dispositivo de taquión (SKUs: TACH4NA, TACH8NA, TACH8ROW) Tipo: Incidente no planeado Estado: Investigación Inicio: Hoy, 10:30 AM PDT Actualmente estamos investigando una perturbación de conectividad que afecta a los dispositivos Tachyon (SKUs TACH4NA, TACH8NA, TACH8ROW). El problema comenzó tras una actualización rutinaria de nuestra infraestructura de conectividad, que provocó un volumen inesperadamente alto de intentos de reconexión de dispositivos simultáneos. Nuestro equipo está trabajando activamente para restaurar el servicio y estabilizar las reconexiones. Publicaremos actualizaciones ya que tenemos más información. Ningún otro tipo de dispositivo de partículas o SKU se ve afectado por este incidente.

2. September 1, 2026 at 6:42 PM UTCmonitoring

   La mayoría de los dispositivos de Tachyon han reconectado y están de vuelta en línea. Seguimos monitoreando la recuperación para asegurar la plena estabilización en los dispositivos restantes. Proporcionaremos una actualización final una vez que todos los dispositivos estén completamente conectados y el incidente se resuelva.

3. September 1, 2026 at 6:55 PM UTCresolved

   Este incidente ha sido resuelto. Todos los dispositivos Tachyon han reconectado con éxito y la conectividad ha sido completamente restaurada. Ningún otro tipo de dispositivo de partículas o SKU fue afectado por este incidente.

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

1. June 8, 2026 at 12:16 PM UTCinvestigating

   La partícula está investigando múltiples informes de portadores celulares en Sudáfrica rechazando o no permitiendo que fluyan las sesiones de datos. La cuestión se refiere a los dispositivos B524 y M524.

2. July 9, 2026 at 10:11 PM UTCidentified

   La partícula está colaborando estrechamente con nuestros socios celulares, sus asociados regionales y los transportistas locales para abordar esta cuestión. El 27 de junio se implementó un cambio de redes, y los dispositivos en línea ya que son capaces de pasar datos. Se está investigando la causa raíz.

3. July 14, 2026 at 8:27 PM UTCresolved

   La cuestión se considera resuelta. Los dispositivos afectados tendrán que ser reiniciados o ciclos de energía para reanudar la conectividad.

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

1. May 21, 2026 at 3:07 PM UTCinvestigating

   We are currently investigating an issue impacting cellular connectivity for some devices on our MVNO network. Our engineering and carrier teams are actively working to identify the root cause and restore normal service as quickly as possible.

2. May 21, 2026 at 3:44 PM UTCidentified

   We are seeing initial signs of recovery as connectivity is being restored for a portion of affected devices. Our teams continue to closely monitor the situation and work with carrier partners to ensure full service restoration.

3. May 21, 2026 at 6:09 PM UTCmonitoring

   Connectivity has largely recovered and we are continuing to monitor the situation closely to ensure service stability across the affected MVNO network. At this time, most devices should be operating normally, though a small number of customers may still experience intermittent issues as recovery completes. We will continue monitoring and provide a final update once we confirm the incident is fully resolved.

4. May 21, 2026 at 8:17 PM UTCresolved

   The issue impacting cellular connectivity on our MVNO network has been resolved. Services have remained stable following recovery, and our teams have confirmed normal operation across affected systems.

1. May 15, 2026 at 1:00 AM UTCinvestigating

   Particle is investigating issues with device connectivity to the Particle cloud. This affects all devices except legacy devices (Photon/P1). The cause is still under investigation.

2. May 15, 2026 at 1:00 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 15, 2026 at 1:08 AM UTCmonitoring

   A fix has been implemented and devices are reconnecting.

4. May 15, 2026 at 1:26 AM UTCresolved

   This incident has been resolved.

1. May 6, 2026 at 12:02 AM UTCinvestigating

   Particle is investigating reports of unstable integrations and the event stream.

2. May 6, 2026 at 12:41 AM UTCresolved

   Particle has deployed a fix, and services are back to baseline.

1. May 1, 2026 at 6:16 PM UTCinvestigating

   Particle is investigating reports of EtherSIM connection instability.

2. May 1, 2026 at 7:34 PM UTCmonitoring

   Our partners have identified the cause of the disruptions, and are observing recovery. We'll continue to monitor the situation.

3. May 1, 2026 at 9:01 PM UTCresolved

   Connectivity has recovered.

1. March 10, 2026 at 5:00 PM UTCinvestigating

   We are aware of a signaling issue impacting 4G data sessions for a small percentage of devices. We are closely monitoring the issue and working with our provider to resolve it.

2. March 10, 2026 at 9:18 PM UTCresolved

   The issue was resolved

1. March 8, 2026 at 8:15 AM UTCinvestigating

   Particle is investigating connectivity issues for devices connected on EtherSIM.

2. March 8, 2026 at 8:28 AM UTCidentified

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

3. March 8, 2026 at 10:09 AM UTCmonitoring

   Devices are recovering and Particle is monitoring the situation.

4. March 8, 2026 at 10:50 AM UTCmonitoring

   Online counts have recovered to expected levels, and reconnections have dropped. We’ll continue to monitor the situation.

5. March 8, 2026 at 11:39 AM UTCresolved

   Connectivity has recovered to normal levels.

1. February 24, 2026 at 9:24 PM UTCinvestigating

   Particle is currently investigating reports of Tachyon devices that are unable to connect to the Particle cloud. Tachyon connectivity is not affected.

2. February 24, 2026 at 9:56 PM UTCmonitoring

   A fix has been implemented and the team is monitoring devices.

3. February 25, 2026 at 7:23 AM UTCresolved

   This incident has been resolved.

1. January 6, 2026 at 3:53 PM UTCidentified

   Particle is aware that some SIM activations are currently facing extended delays. Our cellular partners are actively working on a fix.

2. January 6, 2026 at 7:00 PM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 7:47 PM UTCinvestigating

   Particle is investigating issues with device connectivity to the Particle cloud. This affects all devices, both WiFi and Cellular. The cause is still under investigation.

2. October 20, 2025 at 9:00 PM UTCinvestigating

   The issue is ongoing, and the team is still investigating.

3. October 20, 2025 at 10:08 PM UTCmonitoring

   We identified that our cloud services were impacted by the ongoing AWS outage. Our team has applied some changes that allows the cloud services to auto recover when needed. Periodic disruptions are still expected, but the data to/from the cloud should improve.

4. October 21, 2025 at 10:51 AM UTCresolved

   The incident has been resolved.

1. October 20, 2025 at 4:59 PM UTCidentified

   Particle has identified several services that are still affected after this morning's outage. This includes some logic executions, and Integrations which rely on secrets stored in the Particle cloud. The majority of logic functions, and integrations (that do not use secrets) are not impacted.

2. October 21, 2025 at 1:25 AM UTCresolved

   Metrics for logic and integrations are back to normal.

1. October 20, 2025 at 10:35 AM UTCidentified

   From UTC 08:30 Integrations and Logic and Ledger was impacted by an AWS outage. Integrations have started to recover, but integration relying on saved secrets are still failing.

2. October 20, 2025 at 11:51 AM UTCmonitoring

   Services have recovered and normal operations resumed. The team continues to monitor the situation.

3. October 20, 2025 at 1:53 PM UTCresolved

   The incident has resolved and services are back to normal.

1. October 9, 2025 at 3:45 PM UTCinvestigating

   Particle is investigating elevated levels of cellular rejections for devices connected on EtherSIM.

2. October 9, 2025 at 3:58 PM UTCidentified

   Our cellular partners have confirmed an outage on their end, and are working to restore connectivity. A subset of devices connected via EtherSIM is affected. We will provide more information as soon as it becomes available.

3. October 9, 2025 at 5:54 PM UTCidentified

   The situation has stabilised, but apart from a small batch of devices, recovery is not yet underway. We continue to work with our partners to understand the outage, and will provide an ETA to full recovery as soon as it's available.

4. October 9, 2025 at 8:32 PM UTCmonitoring

   We have observed strong signs of recovery and expect devices to reconnect soon.

5. October 9, 2025 at 10:06 PM UTCmonitoring

   Recovery is still underway.

6. October 9, 2025 at 11:35 PM UTCmonitoring

   Device recovery continues. Recovery is at 80% pre-outage levels.

7. October 10, 2025 at 12:35 AM UTCmonitoring

   The number of online devices is now within our daily baseline; we expect devices to have recovered and are waiting for confirmation from our partners that the problem is resolved.

8. October 10, 2025 at 1:56 AM UTCresolved

   Online devices count and behavior match our daily numbers.

1. September 28, 2025 at 1:56 PM UTCinvestigating

   We detected connectivity drops in the past few minutes, primarily affecting devices on AT&T in the US. Our MVNO partner has been notified and is actively investigating. Our team will continue to monitor the situation until it is resolved.

2. September 28, 2025 at 2:28 PM UTCmonitoring

   Connectivity has recovered to pre-outage levels. We will continue monitoring the fleet to ensure stability.

3. September 28, 2025 at 2:54 PM UTCresolved

   The incident was resolved. Fleet numbers reached pre-outage levels and are stable.

1. September 18, 2025 at 2:21 PM UTCinvestigating

   The Particle team has identified connectivity issues affecting devices located in South Africa (ZA). Devices in this region may experience difficulties establishing or maintaining cellular connections. The Particle team is actively working with cellular partners to investigate the issue and gather more details. Updates will be provided as soon as more information becomes available.

2. September 18, 2025 at 3:09 PM UTCmonitoring

   Particle team has observed that devices in South Africa (ZA) are back online and connections are stable. We will continue monitoring closely to ensure ongoing reliability.

3. September 18, 2025 at 4:30 PM UTCresolved

   This incident has been resolved.

1. August 18, 2025 at 6:48 AM UTCinvestigating

   We have detected a degradation affecting Ethersim connectivity. The impact is most notable in the USA, but effects have also been observed in other regions worldwide. Our provider is currently investigating the issue.

2. August 18, 2025 at 7:24 AM UTCinvestigating

   Our provider is continuing to investigate the issue with their downstream partner. In the meantime, we observe a gradual recovery as devices reattach using alternate routes. We continue to monitor the situation closely.

3. August 18, 2025 at 8:28 AM UTCidentified

   Data sessions continue to recover gradually. Our provider is working with their downstream partner to minimize impact and restore service as quickly as possible. We continue to monitor the issue closely.

4. August 18, 2025 at 9:16 AM UTCmonitoring

   A big part of the impacted devices has recovered by now. We will continue monitoring until full recovery is confirmed.

5. August 18, 2025 at 10:24 AM UTCresolved

   The provider solved the issue, and the fleet recovered to values similar to before the outage

1. August 5, 2025 at 6:02 PM UTCidentified

   Particle is aware of and addressing an issue with the latest console deployment. Devices and the Particle event stream is unaffected. A rollback of the console changes is in progress.

2. August 5, 2025 at 6:08 PM UTCresolved

   The change has been rolled back, and the console is fully functional.

1. July 24, 2025 at 4:53 PM UTCidentified

   Particle is aware that the console event stream is currently not loading for new sessions. The team is actively engaged.

2. July 24, 2025 at 5:18 PM UTCresolved

   A rollback was performed, and the console is showing events. Impact was 8:56am PST to 10:10am PST; events continued to be delivered to Webhooks and devices. Impact was limited to the console's debug event view.