Histórico de interrupções do Ubidots

1. 23 Gwengolo 2026 da 13:38 UTCidentified

   Identificamos um problema que afeta a entrega de notificações por e-mail, incluindo emails de alerta. Algumas mensagens podem chegar tarde ou ser filtradas em pastas de spam/lixo. A nossa equipa está a trabalhar activamente na reparação. SMS, webhook e outros canais de notificação não são afetados. Enquanto isso, recomendamos verificar sua pasta spam/lixo e adicionar [email protected] à sua lista de remetentes seguros. Publicaremos atualizações à medida que a situação progride.

2. 23 Gwengolo 2026 da 15:33 UTCmonitoring

   Uma correção foi implementada e a entrega de notificação por e-mail retornou ao normal. Estamos a acompanhar de perto para confirmar a estabilidade. Se você ainda não ver e-mails de alerta esperados, verifique sua pasta spam/lixo e adicione [email protected] à sua lista de remetentes seguros.

3. 23 Gwengolo 2026 da 16:36 UTCresolved

   Este incidente foi resolvido. Identificamos a causa raiz da degradação da entrega de e-mail e implantamos uma correção. As notificações por e-mail, incluindo e-mails de alerta, estão sendo entregues normalmente. Se ainda não vir os e-mails de alerta esperados, verifique sua pasta spam/lixo e adicione [email protected] à sua lista de remetentes seguros ou contacte nossa equipe de suporte.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 19:36 UTCinvestigating

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

2. 10 Gouere 2026 da 19:47 UTCmonitoring

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

3. 10 Gouere 2026 da 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 Gouere 2026 da 19:51 UTCresolved

   This incident has been resolved.

1. 10 Gouere 2026 da 01:09 UTCinvestigating

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

2. 10 Gouere 2026 da 01:20 UTCmonitoring

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

3. 10 Gouere 2026 da 14:39 UTCresolved

   This incident has been resolved.

1. 27 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 13:47 UTCresolved

   This incident has been resolved.

1. 26 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 13:15 UTCresolved

   This incident has been resolved.

1. 21 Mae 2026 da 12:41 UTCinvestigating

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

2. 21 Mae 2026 da 12:51 UTCmonitoring

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

3. 21 Mae 2026 da 20:34 UTCresolved

   This incident has been resolved.

1. 14 Mae 2026 da 13:12 UTCinvestigating

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

2. 14 Mae 2026 da 13:22 UTCmonitoring

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

3. 15 Mae 2026 da 14:13 UTCresolved

   This incident has been resolved.

1. 14 Mae 2026 da 13:11 UTCinvestigating

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

2. 14 Mae 2026 da 13:21 UTCmonitoring

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

3. 15 Mae 2026 da 14:13 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 06:14 UTCinvestigating

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

2. 13 Mae 2026 da 06:25 UTCmonitoring

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

3. 13 Mae 2026 da 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 Mae 2026 da 14:26 UTCresolved

   This incident has been resolved.

1. 6 Mae 2026 da 13:53 UTCinvestigating

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

2. 6 Mae 2026 da 14:03 UTCmonitoring

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

3. 7 Mae 2026 da 14:06 UTCresolved

   This incident has been resolved.

1. 6 Mae 2026 da 13:52 UTCinvestigating

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

2. 6 Mae 2026 da 14:03 UTCmonitoring

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

3. 7 Mae 2026 da 14:06 UTCresolved

   This incident has been resolved.

1. 21 Ebrel 2026 da 02:59 UTCinvestigating

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

2. 21 Ebrel 2026 da 04:00 UTCidentified

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

3. 21 Ebrel 2026 da 04:00 UTCmonitoring

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

4. 21 Ebrel 2026 da 04:28 UTCresolved

   This incident has been resolved.

1. 20 Ebrel 2026 da 23:43 UTCinvestigating

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

2. 20 Ebrel 2026 da 23:54 UTCmonitoring

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

3. 21 Ebrel 2026 da 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 Ebrel 2026 da 02:59 UTCresolved

   This incident has been resolved.

1. 16 Ebrel 2026 da 16:19 UTCinvestigating

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

2. 16 Ebrel 2026 da 16:30 UTCmonitoring

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

3. 16 Ebrel 2026 da 21:20 UTCresolved

   This incident has been resolved.

1. 16 Ebrel 2026 da 06:49 UTCinvestigating

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

2. 16 Ebrel 2026 da 07:04 UTCmonitoring

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

3. 16 Ebrel 2026 da 13:13 UTCresolved

   This incident has been resolved.

1. 15 Ebrel 2026 da 14:39 UTCinvestigating

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

2. 15 Ebrel 2026 da 14:50 UTCmonitoring

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

3. 15 Ebrel 2026 da 20:03 UTCresolved

   This incident has been resolved.

1. 10 Ebrel 2026 da 07:15 UTCinvestigating

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

2. 10 Ebrel 2026 da 07:26 UTCmonitoring

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

3. 10 Ebrel 2026 da 19:05 UTCresolved

   This incident has been resolved.

1. 4 Cʼhwevrer 2026 da 06:41 UTCinvestigating

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

2. 4 Cʼhwevrer 2026 da 06:59 UTCmonitoring

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

3. 4 Meurzh 2026 da 16:32 UTCresolved

   This incident has been resolved.

1. 28 Genver 2026 da 06:26 UTCinvestigating

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

2. 28 Genver 2026 da 07:05 UTCmonitoring

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

3. 28 Genver 2026 da 21:08 UTCresolved

   This incident has been resolved.

1. 26 Genver 2026 da 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 Genver 2026 da 20:06 UTCmonitoring

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

3. 27 Genver 2026 da 22:26 UTCresolved

   This incident has been resolved.