Robin driftsforstyrrelser

1. 14. juli 2026 kl. 13.12 UTCinvestigating

   Vi undersøger et problem, hvor Robin Dashboardet ikke læsser.

2. 14. juli 2026 kl. 14.38 UTCinvestigating

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

3. 14. juli 2026 kl. 15.15 UTCidentified

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

4. 14. juli 2026 kl. 15.34 UTCmonitoring

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

5. 14. juli 2026 kl. 16.03 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 12. juni 2026 kl. 01.39 UTCinvestigating

   We are currently investigating an issue with the Robin dashboard

2. 12. juni 2026 kl. 01.46 UTCinvestigating

   We are continuing to investigate this issue.

3. 12. juni 2026 kl. 02.13 UTCmonitoring

   A fix has been implemented for the Robin dashboard and we are continuing to monitor the platform.

4. 12. juni 2026 kl. 02.46 UTCresolved

   This incident has been resolved.

1. 1. juni 2026 kl. 20.23 UTCinvestigating

   We are currently investigating an issue with loading the Robin Platform

2. 1. juni 2026 kl. 20.48 UTCmonitoring

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

3. 1. juni 2026 kl. 21.01 UTCresolved

   We've pushed out a fix for the dashboard issue and the platform is working as expected.

1. 17. marts 2026 kl. 13.30 UTCinvestigating

   We are currently investigating this issue.

2. 17. marts 2026 kl. 15.14 UTCidentified

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

3. 17. marts 2026 kl. 15.30 UTCmonitoring

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

4. 17. marts 2026 kl. 15.30 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 17. marts 2026 kl. 16.28 UTCresolved

   This incident has been resolved.

1. 12. marts 2026 kl. 21.07 UTCinvestigating

   We are currently investigating this issue.

2. 12. marts 2026 kl. 21.14 UTCidentified

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

3. 12. marts 2026 kl. 22.24 UTCmonitoring

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

4. 12. marts 2026 kl. 22.24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 12. marts 2026 kl. 22.37 UTCresolved

   This incident has been resolved.

1. 10. marts 2026 kl. 00.10 UTCinvestigating

   We are currently investigating an issue preventing logging into the Robin dashboard.

2. 10. marts 2026 kl. 01.52 UTCidentified

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

3. 10. marts 2026 kl. 02.56 UTCmonitoring

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

4. 10. marts 2026 kl. 02.56 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 10. marts 2026 kl. 03.16 UTCresolved

   This incident has been resolved.

1. 3. marts 2026 kl. 14.18 UTCinvestigating

   We are currently investigating this issue.

2. 3. marts 2026 kl. 14.38 UTCidentified

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

3. 3. marts 2026 kl. 14.52 UTCmonitoring

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

4. 3. marts 2026 kl. 16.39 UTCresolved

   This incident has been resolved.

1. 26. februar 2026 kl. 21.18 UTCinvestigating

   There is currently an issue preventing desk booking. We are investigating the isssue.

2. 26. februar 2026 kl. 22.10 UTCmonitoring

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

3. 26. februar 2026 kl. 22.22 UTCresolved

   This incident has been resolved.

1. 19. februar 2026 kl. 13.56 UTCinvestigating

   We are currently investigating an issue related to SAML login which may impact logging into the Robin Platform.

2. 19. februar 2026 kl. 14.04 UTCidentified

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

3. 19. februar 2026 kl. 14.11 UTCmonitoring

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

4. 19. februar 2026 kl. 14.20 UTCresolved

   This incident has been resolved.

1. 27. august 2025 kl. 09.25 UTCinvestigating

   We're investigating elevated error rates and loading issues across the platform.

2. 27. august 2025 kl. 09.29 UTCidentified

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

3. 27. august 2025 kl. 09.57 UTCmonitoring

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

4. 27. august 2025 kl. 12.47 UTCmonitoring

   We are experiencing extremely high traffic load and are continuing to implement additional measures to address it.

5. 27. august 2025 kl. 14.48 UTCmonitoring

   We have mitigated the high traffic and applications are working as expected again. We will continue to monitor closely.

6. 27. august 2025 kl. 16.01 UTCresolved

   This incident has been resolved.

1. 21. august 2025 kl. 17.51 UTCinvestigating

   We are currently investigating this issue.

2. 21. august 2025 kl. 18.56 UTCidentified

   We have identified ongoing networking issues with third party providers including CloudFlare and AWS and are attempting to work around them.

3. 21. august 2025 kl. 20.03 UTCmonitoring

   We have applied internal fixes to work around the provider issues and have restored service and will continue monitoring.

4. 21. august 2025 kl. 20.34 UTCresolved

   This incident has been resolved.

1. 18. juni 2025 kl. 14.29 UTCinvestigating

   We are currently investigating this issue.

2. 18. juni 2025 kl. 14.50 UTCidentified

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

3. 18. juni 2025 kl. 15.04 UTCmonitoring

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

4. 20. juni 2025 kl. 15.06 UTCresolved

   This incident has been resolved.

1. 17. juni 2025 kl. 09.45 UTCinvestigating

   We're investigating increased API latency in Robin's EU region.

2. 17. juni 2025 kl. 09.56 UTCidentified

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

3. 17. juni 2025 kl. 10.15 UTCmonitoring

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

4. 17. juni 2025 kl. 17.15 UTCresolved

   This incident has been resolved.

1. 12. juni 2025 kl. 18.10 UTCinvestigating

   We are currently investigating this issue.

2. 12. juni 2025 kl. 18.46 UTCmonitoring

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

3. 12. juni 2025 kl. 19.16 UTCresolved

   This incident has been resolved.

1. 27. maj 2025 kl. 00.06 UTCinvestigating

   We are currently investigating this issue.

2. 27. maj 2025 kl. 00.52 UTCmonitoring

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

3. 27. maj 2025 kl. 01.07 UTCresolved

   This incident has been resolved.

1. 29. april 2025 kl. 15.22 UTCinvestigating

   We are currently investigating this issue.

2. 29. april 2025 kl. 15.58 UTCmonitoring

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

3. 29. april 2025 kl. 21.33 UTCresolved

   This incident has been resolved.

1. 16. april 2025 kl. 13.17 UTCinvestigating

   We are currently investigating this issue.

2. 16. april 2025 kl. 13.42 UTCmonitoring

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

3. 16. april 2025 kl. 14.20 UTCresolved

   This incident has been resolved.

1. 1. april 2025 kl. 21.51 UTCinvestigating

   We are currently investigating this issue.

2. 1. april 2025 kl. 22.10 UTCmonitoring

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

3. 1. april 2025 kl. 23.18 UTCresolved

   This incident has been resolved.

1. 10. februar 2025 kl. 14.32 UTCinvestigating

   We are currently investigating this issue.

2. 10. februar 2025 kl. 14.47 UTCidentified

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

3. 10. februar 2025 kl. 15.43 UTCidentified

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

4. 10. februar 2025 kl. 17.52 UTCresolved

   This incident has been resolved.

1. 30. januar 2025 kl. 14.22 UTCidentified

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

2. 30. januar 2025 kl. 14.51 UTCidentified

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

3. 30. januar 2025 kl. 14.54 UTCmonitoring

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

4. 30. januar 2025 kl. 17.33 UTCresolved

   This incident has been resolved.