Spark driftsforstyrrelser

1. 1. september 2026 kl. 20.48 UTCinvestigating

   Berørt komponent: Tachyonenhedens forbindelse (SKU 'er: TACH4NA, TACH8NA, TACH8ROW) Start: I dag, 1: 22 PM PDT Beskrivelse: Vi undersøger i øjeblikket en forbindelse afbrydelse påvirker Tachyon enheder (SKU TACH4NA, TACH8NA, TACH8ROW). Partikelholdet undersøger aktivt problemet og vil sende opdateringer, efterhånden som flere oplysninger bliver tilgængelige. Ingen andre Partikelenhed type eller SKU er påvirket af denne hændelse.

2. 1. september 2026 kl. 21.14 UTCidentified

   Vi har identificeret årsagen til sammenkoblingen, der påvirker Tachyon-enheder. Vores team arbejder aktivt på at løse problemet. Vi vil fortsætte med at sende opdateringer, når der er gjort fremskridt. Ingen andre Partikelenhed type eller SKU er påvirket af denne hændelse.

3. 1. september 2026 kl. 21.43 UTCmonitoring

   Vi har set enheder komme sig og genetablere forbindelsen. Vores team fortsætter med at overvåge inddrivelse for at sikre fuld stabilisering på tværs af de resterende Tachyon enheder. Vi vil give en endelig opdatering, når alle enheder er fuldt tilsluttet, og hændelsen er løst.

4. 1. september 2026 kl. 23.01 UTCresolved

   Denne hændelse er blevet løst. Alle Tachyon- enheder er blevet genforbundet og forbindelsen er blevet genoprettet. Vores team identificerede årsagen og implementerede en rettelse, der bekræfter fuld genopretning på tværs af den berørte flåde. Ingen andre Particle enhed type eller SKU blev påvirket af denne hændelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 1. september 2026 kl. 17.40 UTCinvestigating

   Berørt komponent: Tachyonenhedens forbindelse (SKU 'er: TACH4NA, TACH8NA, TACH8ROW) Type: Uplanlagt hændelse Status: Undersøgelse Startet: I dag, 10: 30 AM PDT Vi undersøger i øjeblikket en forbindelse afbrydelse påvirker Tachyon enheder (SKU TACH4NA, TACH8NA, TACH8ROW). Problemet begyndte efter en rutinemæssig opdatering til vores tilslutningsinfrastruktur, som udløste en uventet høj mængde af samtidige enhedens gentilslutningsforsøg. Vores team arbejder aktivt på at genoprette service og stabilisere forbindelser. Vi vil sende opdateringer som vi har flere oplysninger. Ingen andre Partikelenhed type eller SKU er påvirket af denne hændelse.

2. 1. september 2026 kl. 18.42 UTCmonitoring

   De fleste Tachyon-enheder er blevet tilsluttet igen og er online igen. Vi fortsætter med at overvåge inddrivelse for at sikre fuld stabilisering på tværs af de resterende enheder. Vi vil give en endelig opdatering, når alle enheder er fuldt tilsluttet, og hændelsen er løst.

3. 1. september 2026 kl. 18.55 UTCresolved

   Denne hændelse er blevet løst. Alle Tachyon- enheder er blevet genforbundet og forbindelsen er blevet genoprettet. Ingen andre Particle enhed type eller SKU blev påvirket af denne hændelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 8. juni 2026 kl. 12.16 UTCinvestigating

   Particle undersøger flere rapporter om cellulære luftfartsselskaber i Sydafrika afviser eller ikke tillader data sessioner til at flyde. Spørgsmålet vedrører B524 og M524 enheder.

2. 9. juli 2026 kl. 22.11 UTCidentified

   Particle arbejder tæt sammen med vores cellulære partnere, deres regionale partnere og de lokale luftfartsselskaber for at løse dette problem. Den 27. juni blev en netværksændring gennemført, og enheder kommer online, da er i stand til at videregive data. Undersøgelsen af årsagen er i gang.

3. 14. juli 2026 kl. 20.27 UTCresolved

   Spørgsmålet betragtes som løst. Berørte enheder skal nulstilles eller strøm cykles for at genoptage forbindelse.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 21. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 01.00 UTCinvestigating

   We are continuing to investigate this issue.

3. 15. maj 2026 kl. 01.08 UTCmonitoring

   A fix has been implemented and devices are reconnecting.

4. 15. maj 2026 kl. 01.26 UTCresolved

   This incident has been resolved.

1. 6. maj 2026 kl. 00.02 UTCinvestigating

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

2. 6. maj 2026 kl. 00.41 UTCresolved

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

1. 1. maj 2026 kl. 18.16 UTCinvestigating

   Particle is investigating reports of EtherSIM connection instability.

2. 1. maj 2026 kl. 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. maj 2026 kl. 21.01 UTCresolved

   Connectivity has recovered.

1. 10. marts 2026 kl. 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. marts 2026 kl. 21.18 UTCresolved

   The issue was resolved

1. 8. marts 2026 kl. 08.15 UTCinvestigating

   Particle is investigating connectivity issues for devices connected on EtherSIM.

2. 8. marts 2026 kl. 08.28 UTCidentified

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

3. 8. marts 2026 kl. 10.09 UTCmonitoring

   Devices are recovering and Particle is monitoring the situation.

4. 8. marts 2026 kl. 10.50 UTCmonitoring

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

5. 8. marts 2026 kl. 11.39 UTCresolved

   Connectivity has recovered to normal levels.

1. 24. februar 2026 kl. 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. februar 2026 kl. 21.56 UTCmonitoring

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

3. 25. februar 2026 kl. 07.23 UTCresolved

   This incident has been resolved.

1. 6. januar 2026 kl. 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. januar 2026 kl. 19.00 UTCresolved

   This incident has been resolved.

1. 20. oktober 2025 kl. 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. oktober 2025 kl. 21.00 UTCinvestigating

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

3. 20. oktober 2025 kl. 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. oktober 2025 kl. 10.51 UTCresolved

   The incident has been resolved.

1. 20. oktober 2025 kl. 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. oktober 2025 kl. 01.25 UTCresolved

   Metrics for logic and integrations are back to normal.

1. 20. oktober 2025 kl. 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. oktober 2025 kl. 11.51 UTCmonitoring

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

3. 20. oktober 2025 kl. 13.53 UTCresolved

   The incident has resolved and services are back to normal.

1. 9. oktober 2025 kl. 15.45 UTCinvestigating

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

2. 9. oktober 2025 kl. 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. oktober 2025 kl. 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. oktober 2025 kl. 20.32 UTCmonitoring

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

5. 9. oktober 2025 kl. 22.06 UTCmonitoring

   Recovery is still underway.

6. 9. oktober 2025 kl. 23.35 UTCmonitoring

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

7. 10. oktober 2025 kl. 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. oktober 2025 kl. 01.56 UTCresolved

   Online devices count and behavior match our daily numbers.

1. 28. september 2025 kl. 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. september 2025 kl. 14.28 UTCmonitoring

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

3. 28. september 2025 kl. 14.54 UTCresolved

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

1. 18. september 2025 kl. 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. september 2025 kl. 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. september 2025 kl. 16.30 UTCresolved

   This incident has been resolved.

1. 18. august 2025 kl. 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 kl. 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 kl. 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 kl. 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 kl. 10.24 UTCresolved

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

1. 5. august 2025 kl. 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 kl. 18.08 UTCresolved

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

1. 24. juli 2025 kl. 16.53 UTCidentified

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

2. 24. juli 2025 kl. 17.18 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.