Historial de interrupciones de Robin

1. July 14, 2026 at 1:12 PM UTCinvestigating

   Actualmente estamos investigando un problema con el Robin Dashboard no cargando.

2. July 14, 2026 at 2:38 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 14, 2026 at 3:15 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. July 14, 2026 at 3:34 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. July 14, 2026 at 4:03 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 12, 2026 at 1:39 AM UTCinvestigating

   We are currently investigating an issue with the Robin dashboard

2. June 12, 2026 at 1:46 AM UTCinvestigating

   We are continuing to investigate this issue.

3. June 12, 2026 at 2:13 AM UTCmonitoring

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

4. June 12, 2026 at 2:46 AM UTCresolved

   This incident has been resolved.

1. June 1, 2026 at 8:23 PM UTCinvestigating

   We are currently investigating an issue with loading the Robin Platform

2. June 1, 2026 at 8:48 PM UTCmonitoring

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

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

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

1. March 17, 2026 at 1:30 PM UTCinvestigating

   We are currently investigating this issue.

2. March 17, 2026 at 3:14 PM UTCidentified

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

3. March 17, 2026 at 3:30 PM UTCmonitoring

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

4. March 17, 2026 at 3:30 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. March 17, 2026 at 4:28 PM UTCresolved

   This incident has been resolved.

1. March 12, 2026 at 9:07 PM UTCinvestigating

   We are currently investigating this issue.

2. March 12, 2026 at 9:14 PM UTCidentified

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

3. March 12, 2026 at 10:24 PM UTCmonitoring

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

4. March 12, 2026 at 10:24 PM UTCmonitoring

   We are continuing to monitor for any further issues.

5. March 12, 2026 at 10:37 PM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 12:10 AM UTCinvestigating

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

2. March 10, 2026 at 1:52 AM UTCidentified

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

3. March 10, 2026 at 2:56 AM UTCmonitoring

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

4. March 10, 2026 at 2:56 AM UTCmonitoring

   We are continuing to monitor for any further issues.

5. March 10, 2026 at 3:16 AM UTCresolved

   This incident has been resolved.

1. March 3, 2026 at 2:18 PM UTCinvestigating

   We are currently investigating this issue.

2. March 3, 2026 at 2:38 PM UTCidentified

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

3. March 3, 2026 at 2:52 PM UTCmonitoring

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

4. March 3, 2026 at 4:39 PM UTCresolved

   This incident has been resolved.

1. February 26, 2026 at 9:18 PM UTCinvestigating

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

2. February 26, 2026 at 10:10 PM UTCmonitoring

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

3. February 26, 2026 at 10:22 PM UTCresolved

   This incident has been resolved.

1. February 19, 2026 at 1:56 PM UTCinvestigating

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

2. February 19, 2026 at 2:04 PM UTCidentified

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

3. February 19, 2026 at 2:11 PM UTCmonitoring

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

4. February 19, 2026 at 2:20 PM UTCresolved

   This incident has been resolved.

1. August 27, 2025 at 9:25 AM UTCinvestigating

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

2. August 27, 2025 at 9:29 AM UTCidentified

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

3. August 27, 2025 at 9:57 AM UTCmonitoring

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

4. August 27, 2025 at 12:47 PM UTCmonitoring

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

5. August 27, 2025 at 2:48 PM UTCmonitoring

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

6. August 27, 2025 at 4:01 PM UTCresolved

   This incident has been resolved.

1. August 21, 2025 at 5:51 PM UTCinvestigating

   We are currently investigating this issue.

2. August 21, 2025 at 6:56 PM UTCidentified

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

3. August 21, 2025 at 8:03 PM UTCmonitoring

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

4. August 21, 2025 at 8:34 PM UTCresolved

   This incident has been resolved.

1. June 18, 2025 at 2:29 PM UTCinvestigating

   We are currently investigating this issue.

2. June 18, 2025 at 2:50 PM UTCidentified

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

3. June 18, 2025 at 3:04 PM UTCmonitoring

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

4. June 20, 2025 at 3:06 PM UTCresolved

   This incident has been resolved.

1. June 17, 2025 at 9:45 AM UTCinvestigating

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

2. June 17, 2025 at 9:56 AM UTCidentified

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

3. June 17, 2025 at 10:15 AM UTCmonitoring

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

4. June 17, 2025 at 5:15 PM UTCresolved

   This incident has been resolved.

1. June 12, 2025 at 6:10 PM UTCinvestigating

   We are currently investigating this issue.

2. June 12, 2025 at 6:46 PM UTCmonitoring

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

3. June 12, 2025 at 7:16 PM UTCresolved

   This incident has been resolved.

1. May 27, 2025 at 12:06 AM UTCinvestigating

   We are currently investigating this issue.

2. May 27, 2025 at 12:52 AM UTCmonitoring

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

3. May 27, 2025 at 1:07 AM UTCresolved

   This incident has been resolved.

1. April 29, 2025 at 3:22 PM UTCinvestigating

   We are currently investigating this issue.

2. April 29, 2025 at 3:58 PM UTCmonitoring

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

3. April 29, 2025 at 9:33 PM UTCresolved

   This incident has been resolved.

1. April 16, 2025 at 1:17 PM UTCinvestigating

   We are currently investigating this issue.

2. April 16, 2025 at 1:42 PM UTCmonitoring

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

3. April 16, 2025 at 2:20 PM UTCresolved

   This incident has been resolved.

1. April 1, 2025 at 9:51 PM UTCinvestigating

   We are currently investigating this issue.

2. April 1, 2025 at 10:10 PM UTCmonitoring

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

3. April 1, 2025 at 11:18 PM UTCresolved

   This incident has been resolved.

1. February 10, 2025 at 2:32 PM UTCinvestigating

   We are currently investigating this issue.

2. February 10, 2025 at 2:47 PM UTCidentified

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

3. February 10, 2025 at 3:43 PM UTCidentified

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

4. February 10, 2025 at 5:52 PM UTCresolved

   This incident has been resolved.

1. January 30, 2025 at 2:22 PM UTCidentified

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

2. January 30, 2025 at 2:51 PM UTCidentified

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

3. January 30, 2025 at 2:54 PM UTCmonitoring

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

4. January 30, 2025 at 5:33 PM UTCresolved

   This incident has been resolved.