Whoop driftsforstyrrelser

1. 7. september 2026 kl. 16.56 UTCinvestigating

   Vi undersøger i øjeblikket et problem med Whoop AI.

2. 7. september 2026 kl. 16.58 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 7. september 2026 kl. 17.16 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

4. 7. september 2026 kl. 17.54 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

5. 8. september 2026 kl. 03.33 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

6. 8. september 2026 kl. 13.13 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 3. september 2026 kl. 22.01 UTCinvestigating

   Vi er ved at undersøge problemer med konto skabelse og logge ind. Vores ingeniørhold arbejder på et fix.

2. 3. september 2026 kl. 22.28 UTCmonitoring

   Vi ser forbedringer og følger fortsat resultaterne.

3. 3. september 2026 kl. 23.03 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 11. juni 2026 kl. 16.24 UTCidentified

   We are investigating a delay in data uploads and activity processing. Our engineering team is actively working on a fix. Your data will not be lost and will be caught up shortly.

2. 11. juni 2026 kl. 23.25 UTCmonitoring

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

3. 12. juni 2026 kl. 00.20 UTCresolved

   This incident has been resolved.

1. 11. maj 2026 kl. 13.09 UTCinvestigating

   We are investigating an issue where optimal day strain is not present for users.

2. 11. maj 2026 kl. 13.09 UTCidentified

   The issue has been identified and a fix is being implemented

3. 11. maj 2026 kl. 14.07 UTCmonitoring

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

4. 11. maj 2026 kl. 14.49 UTCresolved

   This incident has been resolved.

1. 16. april 2026 kl. 19.24 UTCinvestigating

   We are currently investigating this issue.

2. 16. april 2026 kl. 19.52 UTCidentified

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

3. 16. april 2026 kl. 20.38 UTCmonitoring

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

4. 16. april 2026 kl. 20.46 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 16. april 2026 kl. 21.26 UTCresolved

   This incident has been resolved.

1. 24. marts 2026 kl. 06.58 UTCinvestigating

   We are currently investigating an issue that is causing intermittent issues with the Community feature

2. 24. marts 2026 kl. 07.06 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. marts 2026 kl. 08.27 UTCresolved

   This incident has been resolved.

1. 18. marts 2026 kl. 18.19 UTCidentified

   We are investigating a delay in workout processing. Our engineering team is actively working on a fix. Your data will not be lost and will be caught up shortly.

2. 18. marts 2026 kl. 19.15 UTCresolved

   This incident has been resolved.

1. 30. januar 2026 kl. 19.41 UTCidentified

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

2. 30. januar 2026 kl. 22.04 UTCresolved

   This incident has been resolved.

1. 26. januar 2026 kl. 20.56 UTCinvestigating

   We are currently investigating issues causing a degraded app experience

2. 26. januar 2026 kl. 20.57 UTCinvestigating

   We are continuing to investigate this issue.

3. 26. januar 2026 kl. 21.36 UTCresolved

   This incident has been resolved

1. 5. december 2025 kl. 09.41 UTCmonitoring

   Users may experience delays in data processing.

2. 5. december 2025 kl. 11.03 UTCresolved

   This incident has been resolved.

1. 28. oktober 2025 kl. 13.02 UTCinvestigating

   We’re currently experiencing an issue affecting membership tiers. Our team is investigating and working to resolve it as quickly as possible. Thanks for your patience.

2. 28. oktober 2025 kl. 17.25 UTCmonitoring

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

3. 28. oktober 2025 kl. 19.15 UTCresolved

   This incident has been resolved.

1. 11. oktober 2025 kl. 00.20 UTCinvestigating

   We are currently investigating this issue.

2. 11. oktober 2025 kl. 00.59 UTCmonitoring

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

3. 11. oktober 2025 kl. 01.12 UTCresolved

   This incident has been resolved.

1. 2. oktober 2025 kl. 17.28 UTCinvestigating

   We are currently investigating the issue.

2. 2. oktober 2025 kl. 19.10 UTCidentified

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

3. 2. oktober 2025 kl. 20.05 UTCidentified

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

4. 2. oktober 2025 kl. 21.44 UTCmonitoring

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

5. 3. oktober 2025 kl. 00.16 UTCresolved

   This incident has been resolved.

1. 16. april 2025 kl. 19.30 UTCinvestigating

   We are currently investigating this issue.

2. 16. april 2025 kl. 20.34 UTCidentified

   We have identified the issue and are working with our cloud providers to resolve it.

3. 16. april 2025 kl. 20.51 UTCmonitoring

   We have resolved the issue and data is now catching up and applications are restoring their health. Sleeps and Stress are a few minutes behind real time and are catching up.

4. 16. april 2025 kl. 21.10 UTCresolved

   The incident is resolved, data is caught up, no data was lost, all services are restored.

1. 16. april 2025 kl. 16.26 UTCidentified

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

2. 16. april 2025 kl. 16.29 UTCidentified

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

3. 16. april 2025 kl. 18.51 UTCmonitoring

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

4. 16. april 2025 kl. 18.59 UTCresolved

   This incident has been resolved.

1. 15. april 2025 kl. 20.57 UTCinvestigating

   We are currently investigating this issue.

2. 15. april 2025 kl. 21.07 UTCinvestigating

   We are continuing to investigate this issue.

3. 15. april 2025 kl. 21.17 UTCmonitoring

   We are recovering from the issue. App performance is healthy and data will be caught up shortly.

4. 15. april 2025 kl. 21.41 UTCresolved

   The incident has been resolved

1. 20. september 2024 kl. 11.40 UTCinvestigating

   We are investigating an issue disrupting the app. Our engineering team is actively working on a fix. Your data will not be lost and will be caught up shortly.

2. 20. september 2024 kl. 12.03 UTCidentified

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

3. 20. september 2024 kl. 12.53 UTCmonitoring

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

4. 20. september 2024 kl. 15.57 UTCresolved

   This incident has been resolved.

1. 23. august 2024 kl. 11.41 UTCinvestigating

   We are currently investigating this issue.

2. 23. august 2024 kl. 12.18 UTCinvestigating

   We are continuing to investigate this issue.

3. 23. august 2024 kl. 12.19 UTCinvestigating

   We are currently investigating errors when opening the app

4. 23. august 2024 kl. 16.18 UTCidentified

   The team identified the issue and a fix has been deployed. WHOOP data is catching up.

5. 23. august 2024 kl. 20.26 UTCresolved

   This incident has been resolved.

1. 17. juli 2024 kl. 09.24 UTCinvestigating

   The team is investigating a bug that is showing data catching up indicator in app stuck or behind in time. The team is investigating, know that your data is coming in and is currently available. Activities and Recoveries are still processing.

2. 17. juli 2024 kl. 10.06 UTCidentified

   We have found the bug and are currently deploying a fix

3. 17. juli 2024 kl. 10.19 UTCresolved

   This incident has been resolved.

1. 12. juli 2024 kl. 13.00 UTCinvestigating

   We are investigating a delay in strain processing. Our engineering team is actively working on a fix. Your data will not be lost and will be caught up shortly. You may experience latency in loading the app.

2. 12. juli 2024 kl. 15.50 UTCidentified

   Sleep and Strain calculations are behind in processing. Your data will be be saved and accessible after the issue is resolved but you may experience some delays in processing.

3. 12. juli 2024 kl. 17.24 UTCmonitoring

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

4. 12. juli 2024 kl. 17.54 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 12. juli 2024 kl. 18.13 UTCresolved

   This incident has been resolved.