Istoricul incidentelor Ubidots

1. 23 septembrie 2026 la 13:38 UTCidentified

   Am identificat o problemă care afectează livrarea de notificări de e-mail, inclusiv e-mailuri de alertă. Unele mesaje pot ajunge târziu sau pot fi filtrate în dosare spam/junk. Echipa noastră lucrează activ la remediere. SMS, webhook și alte canale de notificare nu sunt afectate. Între timp, vă recomandăm verificarea folderul spam/junk și adăugarea no-reply@iot-notificări.com la lista de expeditori în condiții de siguranță. Vom posta actualizări pe măsură ce situaţia progresează.

2. 23 septembrie 2026 la 15:33 UTCmonitoring

   Un fix a fost implementat și notificarea prin e-mail a revenit la normal. Monitorizăm îndeaproape pentru a confirma stabilitatea. Dacă încă nu vedeți e-mailuri de alertă așteptate, vă rugăm să verificați dosarul spam/junk și să adăugați nici-reply@iot-notificări.com la lista de expeditori în condiții de siguranță.

3. 23 septembrie 2026 la 16:36 UTCresolved

   Acest incident a fost rezolvat. Am identificat cauza principală a degradării e-mail de livrare și a desfășurat o fix. Notificările prin e-mail, inclusiv e-mailurile de alertă, sunt livrate în mod normal. Dacă încă nu vedeți e-mailuri de alertă așteptate, vă rugăm să verificați dosarul spam/junk și adăugați nici-reply@iot-notificări.com la lista de expeditori în condiții de siguranță, sau contactați echipa noastră de sprijin.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 19:36 UTCinvestigating

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

2. 10 iulie 2026 la 19:47 UTCmonitoring

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

3. 10 iulie 2026 la 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 iulie 2026 la 19:51 UTCresolved

   This incident has been resolved.

1. 10 iulie 2026 la 01:09 UTCinvestigating

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

2. 10 iulie 2026 la 01:20 UTCmonitoring

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

3. 10 iulie 2026 la 14:39 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 21 mai 2026 la 12:41 UTCinvestigating

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

2. 21 mai 2026 la 12:51 UTCmonitoring

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

3. 21 mai 2026 la 20:34 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 la 13:12 UTCinvestigating

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

2. 14 mai 2026 la 13:22 UTCmonitoring

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

3. 15 mai 2026 la 14:13 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 la 13:11 UTCinvestigating

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

2. 14 mai 2026 la 13:21 UTCmonitoring

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

3. 15 mai 2026 la 14:13 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 la 06:14 UTCinvestigating

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

2. 13 mai 2026 la 06:25 UTCmonitoring

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

3. 13 mai 2026 la 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 mai 2026 la 14:26 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 la 13:53 UTCinvestigating

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

2. 6 mai 2026 la 14:03 UTCmonitoring

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

3. 7 mai 2026 la 14:06 UTCresolved

   This incident has been resolved.

1. 6 mai 2026 la 13:52 UTCinvestigating

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

2. 6 mai 2026 la 14:03 UTCmonitoring

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

3. 7 mai 2026 la 14:06 UTCresolved

   This incident has been resolved.

1. 21 aprilie 2026 la 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 aprilie 2026 la 04:00 UTCidentified

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

3. 21 aprilie 2026 la 04:00 UTCmonitoring

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

4. 21 aprilie 2026 la 04:28 UTCresolved

   This incident has been resolved.

1. 20 aprilie 2026 la 23:43 UTCinvestigating

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

2. 20 aprilie 2026 la 23:54 UTCmonitoring

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

3. 21 aprilie 2026 la 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 aprilie 2026 la 02:59 UTCresolved

   This incident has been resolved.

1. 16 aprilie 2026 la 16:19 UTCinvestigating

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

2. 16 aprilie 2026 la 16:30 UTCmonitoring

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

3. 16 aprilie 2026 la 21:20 UTCresolved

   This incident has been resolved.

1. 16 aprilie 2026 la 06:49 UTCinvestigating

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

2. 16 aprilie 2026 la 07:04 UTCmonitoring

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

3. 16 aprilie 2026 la 13:13 UTCresolved

   This incident has been resolved.

1. 15 aprilie 2026 la 14:39 UTCinvestigating

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

2. 15 aprilie 2026 la 14:50 UTCmonitoring

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

3. 15 aprilie 2026 la 20:03 UTCresolved

   This incident has been resolved.

1. 10 aprilie 2026 la 07:15 UTCinvestigating

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

2. 10 aprilie 2026 la 07:26 UTCmonitoring

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

3. 10 aprilie 2026 la 19:05 UTCresolved

   This incident has been resolved.

1. 4 februarie 2026 la 06:41 UTCinvestigating

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

2. 4 februarie 2026 la 06:59 UTCmonitoring

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

3. 4 martie 2026 la 16:32 UTCresolved

   This incident has been resolved.

1. 28 ianuarie 2026 la 06:26 UTCinvestigating

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

2. 28 ianuarie 2026 la 07:05 UTCmonitoring

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

3. 28 ianuarie 2026 la 21:08 UTCresolved

   This incident has been resolved.

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

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

3. 27 ianuarie 2026 la 22:26 UTCresolved

   This incident has been resolved.