Historial de interrupciones de Ubidots

1. 23 de septiembre de 2026 a las 13:38 UTCidentified

   Hemos identificado un problema que afecta la entrega de notificaciones de correo electrónico, incluyendo correos electrónicos de alerta. Algunos mensajes pueden llegar tarde o ser filtrados en carpetas de spam/junk. Nuestro equipo está trabajando activamente en la rehabilitación. SMS, webhook y otros canales de notificación no están afectados. Mientras tanto, recomendamos revisar su carpeta spam/junk y agregar [email protected] a su lista de envíos seguros. Publicaremos actualizaciones a medida que avance la situación.

2. 23 de septiembre de 2026 a las 15:33 UTCmonitoring

   Se ha aplicado una solución y la notificación de correo electrónico ha devuelto a la normalidad. Estamos monitoreando de cerca para confirmar la estabilidad. Si todavía no ve correos electrónicos de alerta esperados, por favor, compruebe su carpeta spam/junk y agregue [email protected] a su lista de envíos seguros.

3. 23 de septiembre de 2026 a las 16:36 UTCresolved

   Este incidente ha sido resuelto. Identificamos la causa raíz de la degradación de la entrega de correo electrónico y implementamos una solución. Las notificaciones por correo electrónico, incluidos los correos electrónicos de alerta, se envían normalmente. Si todavía no ve correos electrónicos de alerta esperados, por favor, compruebe su carpeta spam/junk y agregue [email protected] a su lista de envíos seguros, o contacte con nuestro equipo de soporte.

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

1. 10 de julio de 2026 a las 19:36 UTCinvestigating

   We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

2. 10 de julio de 2026 a las 19:47 UTCmonitoring

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

3. 10 de julio de 2026 a las 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 de julio de 2026 a las 19:51 UTCresolved

   This incident has been resolved.

1. 10 de julio de 2026 a las 1:09 UTCinvestigating

   We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

2. 10 de julio de 2026 a las 1:20 UTCmonitoring

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

3. 10 de julio de 2026 a las 14:39 UTCresolved

   This incident has been resolved.

1. 27 de mayo de 2026 a las 13:14 UTCinvestigating

   We are currently experiencing a service disruption affecting Ubidots (industrial.ubidots.com) and associated apps. Users may be seeing 503 Service Unavailable errors. Our team is actively investigating a connectivity issue between our connection pooler and the database cluster, following a scheduled PostgreSQL upgrade operation. We are working to restore full service as quickly as possible. We will provide updates every 15–20 minutes. We apologize for the inconvenience.

2. 27 de mayo de 2026 a las 13:32 UTCmonitoring

   The service has been restored and we are monitoring the platform for full stability. The issue was caused by a configuration incompatibility introduced during our PostgreSQL upgrade. The database server was requiring SSL connections, which prevented our connection pooler from establishing a successful connection. We resolved the issue by updating the database configuration and upgrading the connection pooler. If you are still experiencing issues, please reach out to [email protected]. We will confirm full resolution shortly.

3. 28 de mayo de 2026 a las 13:47 UTCresolved

   This incident has been resolved.

1. 26 de mayo de 2026 a las 15:35 UTCinvestigating

   We are currently experiencing an issue affecting Ubidots (industrial.ubidots.com) and associated apps. Users may be seeing 503 Service Unavailable errors. This is related to an ongoing database maintenance operation. Our team is actively working to restore full service. We will provide updates every 15–20 minutes. We apologize for the inconvenience.

2. 26 de mayo de 2026 a las 15:59 UTCmonitoring

   The database switchover has been completed and we are monitoring the platform for full recovery. Some users may still experience intermittent errors or degraded performance while the system stabilizes. We will confirm full resolution shortly. Thank you for your patience.

3. 27 de mayo de 2026 a las 13:15 UTCresolved

   This incident has been resolved.

1. 21 de mayo de 2026 a las 12:41 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 21 de mayo de 2026 a las 12:51 UTCmonitoring

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

3. 21 de mayo de 2026 a las 20:34 UTCresolved

   This incident has been resolved.

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

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 14 de mayo de 2026 a las 13:22 UTCmonitoring

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

3. 15 de mayo de 2026 a las 14:13 UTCresolved

   This incident has been resolved.

1. 14 de mayo de 2026 a las 13:11 UTCinvestigating

   We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

2. 14 de mayo de 2026 a las 13:21 UTCmonitoring

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

3. 15 de mayo de 2026 a las 14:13 UTCresolved

   This incident has been resolved.

1. 13 de mayo de 2026 a las 6:14 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 13 de mayo de 2026 a las 6:25 UTCmonitoring

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

3. 13 de mayo de 2026 a las 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 de mayo de 2026 a las 14:26 UTCresolved

   This incident has been resolved.

1. 6 de mayo de 2026 a las 13:53 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 6 de mayo de 2026 a las 14:03 UTCmonitoring

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

3. 7 de mayo de 2026 a las 14:06 UTCresolved

   This incident has been resolved.

1. 6 de mayo de 2026 a las 13:52 UTCinvestigating

   We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

2. 6 de mayo de 2026 a las 14:03 UTCmonitoring

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

3. 7 de mayo de 2026 a las 14:06 UTCresolved

   This incident has been resolved.

1. 21 de abril de 2026 a las 2:59 UTCinvestigating

   We have identified an error with our MQTT data ingestion service and Events engine are currently looking into the issue.

2. 21 de abril de 2026 a las 4:00 UTCidentified

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

3. 21 de abril de 2026 a las 4:00 UTCmonitoring

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

4. 21 de abril de 2026 a las 4:28 UTCresolved

   This incident has been resolved.

1. 20 de abril de 2026 a las 23:43 UTCinvestigating

   We have identified an error with our HTTP data ingestion service and are currently looking into the issue.

2. 20 de abril de 2026 a las 23:54 UTCmonitoring

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

3. 21 de abril de 2026 a las 2:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 de abril de 2026 a las 2:59 UTCresolved

   This incident has been resolved.

1. 16 de abril de 2026 a las 16:19 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 16 de abril de 2026 a las 16:30 UTCmonitoring

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

3. 16 de abril de 2026 a las 21:20 UTCresolved

   This incident has been resolved.

1. 16 de abril de 2026 a las 6:49 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 16 de abril de 2026 a las 7:04 UTCmonitoring

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

3. 16 de abril de 2026 a las 13:13 UTCresolved

   This incident has been resolved.

1. 15 de abril de 2026 a las 14:39 UTCinvestigating

   We have identified an error with our MQTT publish service and are currently looking into the issue.

2. 15 de abril de 2026 a las 14:50 UTCmonitoring

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

3. 15 de abril de 2026 a las 20:03 UTCresolved

   This incident has been resolved.

1. 10 de abril de 2026 a las 7:15 UTCinvestigating

   We have identified an error with our TCP data ingestion service and are currently looking into the issue.

2. 10 de abril de 2026 a las 7:26 UTCmonitoring

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

3. 10 de abril de 2026 a las 19:05 UTCresolved

   This incident has been resolved.

1. 4 de febrero de 2026 a las 6:41 UTCinvestigating

   We have identified an error with our TCP data ingestion service and are currently looking into the issue.

2. 4 de febrero de 2026 a las 6:59 UTCmonitoring

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

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

   This incident has been resolved.

1. 28 de enero de 2026 a las 6:26 UTCinvestigating

   We have identified an error with our TCP data ingestion service and are currently looking into the issue.

2. 28 de enero de 2026 a las 7:05 UTCmonitoring

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

3. 28 de enero de 2026 a las 21:08 UTCresolved

   This incident has been resolved.

1. 26 de enero de 2026 a las 17:08 UTCinvestigating

   Earlier today, we identified increased load on one of our underlying database nodes, which led to higher-than-usual latency across dashboards and Synthetic Variables processing in the US deployment. As a result, synthetic variable calculations and updates are delayed, and some dashboards may have experienced slower response times while corrective maintenance is performed to stabilize the platform. The system is gradually returning to normal operation, and we are closely monitoring performance to ensure stability and prevent further impact. We appreciate your patience and understanding.

2. 26 de enero de 2026 a las 20:06 UTCmonitoring

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

3. 27 de enero de 2026 a las 22:26 UTCresolved

   This incident has been resolved.