Historial de interrupciones de Robin

1. 14 de julio de 2026 a las 13:12 UTCinvestigating

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

2. 14 de julio de 2026 a las 14:38 UTCinvestigating

   Seguimos investigando esta cuestión.

3. 14 de julio de 2026 a las 15:15 UTCidentified

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

4. 14 de julio de 2026 a las 15:34 UTCmonitoring

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

5. 14 de julio de 2026 a las 16:03 UTCresolved

   Este incidente ha sido resuelto.

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

1. 12 de junio de 2026 a las 1:39 UTCinvestigating

   We are currently investigating an issue with the Robin dashboard

2. 12 de junio de 2026 a las 1:46 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 de junio de 2026 a las 2:13 UTCmonitoring

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

4. 12 de junio de 2026 a las 2:46 UTCresolved

   This incident has been resolved.

1. 1 de junio de 2026 a las 20:23 UTCinvestigating

   We are currently investigating an issue with loading the Robin Platform

2. 1 de junio de 2026 a las 20:48 UTCmonitoring

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

3. 1 de junio de 2026 a las 21:01 UTCresolved

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

1. 17 de marzo de 2026 a las 13:30 UTCinvestigating

   We are currently investigating this issue.

2. 17 de marzo de 2026 a las 15:14 UTCidentified

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

3. 17 de marzo de 2026 a las 15:30 UTCmonitoring

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

4. 17 de marzo de 2026 a las 15:30 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 17 de marzo de 2026 a las 16:28 UTCresolved

   This incident has been resolved.

1. 12 de marzo de 2026 a las 21:07 UTCinvestigating

   We are currently investigating this issue.

2. 12 de marzo de 2026 a las 21:14 UTCidentified

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

3. 12 de marzo de 2026 a las 22:24 UTCmonitoring

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

4. 12 de marzo de 2026 a las 22:24 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 12 de marzo de 2026 a las 22:37 UTCresolved

   This incident has been resolved.

1. 10 de marzo de 2026 a las 0:10 UTCinvestigating

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

2. 10 de marzo de 2026 a las 1:52 UTCidentified

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

3. 10 de marzo de 2026 a las 2:56 UTCmonitoring

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

4. 10 de marzo de 2026 a las 2:56 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 10 de marzo de 2026 a las 3:16 UTCresolved

   This incident has been resolved.

1. 3 de marzo de 2026 a las 14:18 UTCinvestigating

   We are currently investigating this issue.

2. 3 de marzo de 2026 a las 14:38 UTCidentified

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

3. 3 de marzo de 2026 a las 14:52 UTCmonitoring

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

4. 3 de marzo de 2026 a las 16:39 UTCresolved

   This incident has been resolved.

1. 26 de febrero de 2026 a las 21:18 UTCinvestigating

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

2. 26 de febrero de 2026 a las 22:10 UTCmonitoring

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

3. 26 de febrero de 2026 a las 22:22 UTCresolved

   This incident has been resolved.

1. 19 de febrero de 2026 a las 13:56 UTCinvestigating

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

2. 19 de febrero de 2026 a las 14:04 UTCidentified

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

3. 19 de febrero de 2026 a las 14:11 UTCmonitoring

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

4. 19 de febrero de 2026 a las 14:20 UTCresolved

   This incident has been resolved.

1. 27 de agosto de 2025 a las 9:25 UTCinvestigating

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

2. 27 de agosto de 2025 a las 9:29 UTCidentified

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

3. 27 de agosto de 2025 a las 9:57 UTCmonitoring

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

4. 27 de agosto de 2025 a las 12:47 UTCmonitoring

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

5. 27 de agosto de 2025 a las 14:48 UTCmonitoring

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

6. 27 de agosto de 2025 a las 16:01 UTCresolved

   This incident has been resolved.

1. 21 de agosto de 2025 a las 17:51 UTCinvestigating

   We are currently investigating this issue.

2. 21 de agosto de 2025 a las 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 de agosto de 2025 a las 20:03 UTCmonitoring

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

4. 21 de agosto de 2025 a las 20:34 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2025 a las 14:29 UTCinvestigating

   We are currently investigating this issue.

2. 18 de junio de 2025 a las 14:50 UTCidentified

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

3. 18 de junio de 2025 a las 15:04 UTCmonitoring

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

4. 20 de junio de 2025 a las 15:06 UTCresolved

   This incident has been resolved.

1. 17 de junio de 2025 a las 9:45 UTCinvestigating

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

2. 17 de junio de 2025 a las 9:56 UTCidentified

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

3. 17 de junio de 2025 a las 10:15 UTCmonitoring

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

4. 17 de junio de 2025 a las 17:15 UTCresolved

   This incident has been resolved.

1. 12 de junio de 2025 a las 18:10 UTCinvestigating

   We are currently investigating this issue.

2. 12 de junio de 2025 a las 18:46 UTCmonitoring

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

3. 12 de junio de 2025 a las 19:16 UTCresolved

   This incident has been resolved.

1. 27 de mayo de 2025 a las 0:06 UTCinvestigating

   We are currently investigating this issue.

2. 27 de mayo de 2025 a las 0:52 UTCmonitoring

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

3. 27 de mayo de 2025 a las 1:07 UTCresolved

   This incident has been resolved.

1. 29 de abril de 2025 a las 15:22 UTCinvestigating

   We are currently investigating this issue.

2. 29 de abril de 2025 a las 15:58 UTCmonitoring

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

3. 29 de abril de 2025 a las 21:33 UTCresolved

   This incident has been resolved.

1. 16 de abril de 2025 a las 13:17 UTCinvestigating

   We are currently investigating this issue.

2. 16 de abril de 2025 a las 13:42 UTCmonitoring

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

3. 16 de abril de 2025 a las 14:20 UTCresolved

   This incident has been resolved.

1. 1 de abril de 2025 a las 21:51 UTCinvestigating

   We are currently investigating this issue.

2. 1 de abril de 2025 a las 22:10 UTCmonitoring

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

3. 1 de abril de 2025 a las 23:18 UTCresolved

   This incident has been resolved.

1. 10 de febrero de 2025 a las 14:32 UTCinvestigating

   We are currently investigating this issue.

2. 10 de febrero de 2025 a las 14:47 UTCidentified

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

3. 10 de febrero de 2025 a las 15:43 UTCidentified

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

4. 10 de febrero de 2025 a las 17:52 UTCresolved

   This incident has been resolved.

1. 30 de enero de 2025 a las 14:22 UTCidentified

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

2. 30 de enero de 2025 a las 14:51 UTCidentified

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

3. 30 de enero de 2025 a las 14:54 UTCmonitoring

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

4. 30 de enero de 2025 a las 17:33 UTCresolved

   This incident has been resolved.