Istoricul incidentelor Spark

1. 21 septembrie 2026 la 18:07 UTCinvestigating

   Investigăm o problemă de infrastructură care afectează dispozitivele Tachyon. Unele dispozitive pot experimenta conexiuni întârziate sau intermitente la Cloud dispozitiv. Alte tipuri de dispozitive nu sunt afectate.

2. 21 septembrie 2026 la 18:28 UTCidentified

   Am identificat sursa problemei infrastructurii care afectează dispozitivele Tachyon. Echipa noastră de inginerie lucrează activ la un fix și va oferi o actualizare de îndată ce este implementat.

3. 21 septembrie 2026 la 21:03 UTCmonitoring

   A fost implementat un fix şi monitorizăm rezultatele. Conectivitatea tahionică se stabilizează în regiunile afectate. Vom continua să urmărim îndeaproape înainte de a marca acest lucru rezolvat.

4. 21 septembrie 2026 la 21:45 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 1 septembrie 2026 la 20:48 UTCinvestigating

   Componenta afectată: Conectivitatea dispozitivelor tahionice (SKU: TACH4NA, TACH8NA, TACH8row) Start: Astăzi, 1:22 PM PDT Descriere: Investigăm în prezent o perturbare a conectivității care afectează dispozitivele Tachyon (SKU TACH4NA, TACH8NA, TACH8row). Echipa Particule investighează în mod activ problema și va posta actualizări pe măsură ce mai multe informații devin disponibile. Niciun alt tip de dispozitiv de particule sau SKU nu este afectat de acest incident.

2. 1 septembrie 2026 la 21:14 UTCidentified

   Am identificat cauza întreruperii conexiunii care afectează dispozitivele Tachyon. Echipa noastră lucrează activ la o rezolvare a problemei. Vom continua să postăm actualizări pe măsură ce se fac progrese. Niciun alt tip de dispozitiv de particule sau SKU nu este afectat de acest incident.

3. 1 septembrie 2026 la 21:43 UTCmonitoring

   Am observat dispozitive de recuperare și reconectare. Echipa noastră continuă să monitorizeze recuperarea pentru a asigura stabilizarea completă pe dispozitivele Tachyon rămase. Vom oferi o actualizare finală odată ce toate dispozitivele au reconectat complet și incidentul este rezolvat.

4. 1 septembrie 2026 la 23:01 UTCresolved

   Acest incident a fost rezolvat. Toate dispozitivele Tachyon s-au reconectat cu succes și conectivitatea a fost complet restaurată. Echipa noastră a identificat cauza principală şi a implementat un fix, confirmând recuperarea completă a flotei afectate. Niciun alt tip de dispozitiv de particule sau SKU nu a fost afectat de acest incident.

Traducere automată din actualizarea oficială a incidentului.

1. 1 septembrie 2026 la 17:40 UTCinvestigating

   Componenta afectată: Conectivitatea dispozitivelor tahionice (SKU: TACH4NA, TACH8NA, TACH8row) Tip: Incident neplanificat Stare: Investigare Start: Astăzi, 10:30 AM PDT Investigăm în prezent o perturbare a conectivității care afectează dispozitivele Tachyon (SKU TACH4NA, TACH8NA, TACH8row). Problema a început în urma unei actualizări de rutină a infrastructurii noastre de conectivitate, care a declanșat un volum neașteptat de mare de încercări simultane de reconectare a dispozitivului. Echipa noastră lucrează activ pentru a restabili serviciul şi a stabiliza reconectările. Vom posta actualizări deoarece avem mai multe informații. Niciun alt tip de dispozitiv de particule sau SKU nu este afectat de acest incident.

2. 1 septembrie 2026 la 18:42 UTCmonitoring

   Majoritatea dispozitivelor Tachyon au reconectat și sunt din nou online. Continuăm să monitorizăm recuperarea pentru a asigura stabilizarea completă a celorlalte dispozitive. Vom oferi o actualizare finală odată ce toate dispozitivele au reconectat complet și incidentul este rezolvat.

3. 1 septembrie 2026 la 18:55 UTCresolved

   Acest incident a fost rezolvat. Toate dispozitivele Tachyon s-au reconectat cu succes și conectivitatea a fost complet restaurată. Niciun alt tip de dispozitiv de particule sau SKU nu a fost afectat de acest incident.

Traducere automată din actualizarea oficială a incidentului.

1. 8 iunie 2026 la 12:16 UTCinvestigating

   Particulele investighează mai multe rapoarte ale transportatorilor celulari din Africa de Sud care resping sau nu permit fluxul de date. Problema se referă la dispozitivele B524 și M524.

2. 9 iulie 2026 la 22:11 UTCidentified

   Particulele colaborează îndeaproape cu partenerii noştri celulari, cu partenerii lor regionali şi cu transportatorii locali pentru a aborda această problemă. Pe 27 iunie a fost pusă în aplicare o schimbare în rețea, iar dispozitivele care vin online de atunci pot transmite date. Ancheta în cauza rădăcină este în curs de desfășurare.

3. 14 iulie 2026 la 20:27 UTCresolved

   Problema este considerată rezolvată. Dispozitivele afectate vor trebui resetate sau cu ciclul de alimentare pentru a relua conectivitatea.

Traducere automată din actualizarea oficială a incidentului.

1. 21 mai 2026 la 15:07 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. 21 mai 2026 la 15:44 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. 21 mai 2026 la 18:09 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. 21 mai 2026 la 20:17 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. 15 mai 2026 la 01:00 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. 15 mai 2026 la 01:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 mai 2026 la 01:08 UTCmonitoring

   A fix has been implemented and devices are reconnecting.

4. 15 mai 2026 la 01:26 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 la 00:02 UTCinvestigating

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

2. 6 mai 2026 la 00:41 UTCresolved

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

1. 1 mai 2026 la 18:16 UTCinvestigating

   Particle is investigating reports of EtherSIM connection instability.

2. 1 mai 2026 la 19:34 UTCmonitoring

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

3. 1 mai 2026 la 21:01 UTCresolved

   Connectivity has recovered.

1. 10 martie 2026 la 17:00 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. 10 martie 2026 la 21:18 UTCresolved

   The issue was resolved

1. 8 martie 2026 la 08:15 UTCinvestigating

   Particle is investigating connectivity issues for devices connected on EtherSIM.

2. 8 martie 2026 la 08:28 UTCidentified

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

3. 8 martie 2026 la 10:09 UTCmonitoring

   Devices are recovering and Particle is monitoring the situation.

4. 8 martie 2026 la 10:50 UTCmonitoring

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

5. 8 martie 2026 la 11:39 UTCresolved

   Connectivity has recovered to normal levels.

1. 24 februarie 2026 la 21:24 UTCinvestigating

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

2. 24 februarie 2026 la 21:56 UTCmonitoring

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

3. 25 februarie 2026 la 07:23 UTCresolved

   This incident has been resolved.

1. 6 ianuarie 2026 la 15:53 UTCidentified

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

2. 6 ianuarie 2026 la 19:00 UTCresolved

   This incident has been resolved.

1. 20 octombrie 2025 la 19:47 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. 20 octombrie 2025 la 21:00 UTCinvestigating

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

3. 20 octombrie 2025 la 22:08 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. 21 octombrie 2025 la 10:51 UTCresolved

   The incident has been resolved.

1. 20 octombrie 2025 la 16:59 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. 21 octombrie 2025 la 01:25 UTCresolved

   Metrics for logic and integrations are back to normal.

1. 20 octombrie 2025 la 10:35 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. 20 octombrie 2025 la 11:51 UTCmonitoring

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

3. 20 octombrie 2025 la 13:53 UTCresolved

   The incident has resolved and services are back to normal.

1. 9 octombrie 2025 la 15:45 UTCinvestigating

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

2. 9 octombrie 2025 la 15:58 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. 9 octombrie 2025 la 17:54 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. 9 octombrie 2025 la 20:32 UTCmonitoring

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

5. 9 octombrie 2025 la 22:06 UTCmonitoring

   Recovery is still underway.

6. 9 octombrie 2025 la 23:35 UTCmonitoring

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

7. 10 octombrie 2025 la 00:35 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. 10 octombrie 2025 la 01:56 UTCresolved

   Online devices count and behavior match our daily numbers.

1. 28 septembrie 2025 la 13:56 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. 28 septembrie 2025 la 14:28 UTCmonitoring

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

3. 28 septembrie 2025 la 14:54 UTCresolved

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

1. 18 septembrie 2025 la 14:21 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. 18 septembrie 2025 la 15:09 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. 18 septembrie 2025 la 16:30 UTCresolved

   This incident has been resolved.

1. 18 august 2025 la 06:48 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. 18 august 2025 la 07:24 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. 18 august 2025 la 08:28 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. 18 august 2025 la 09:16 UTCmonitoring

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

5. 18 august 2025 la 10:24 UTCresolved

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

1. 5 august 2025 la 18:02 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. 5 august 2025 la 18:08 UTCresolved

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