Historia awarii Ubidots

1. 23 września 2026 13:38 UTCidentified

   Zidentyfikowaliśmy problem dotyczący dostarczania powiadomień e-mail, w tym alarmowych e-maili. Niektóre wiadomości mogą pojawić się późno lub być filtrowane do folderów spam / śmieci. Nasz zespół aktywnie pracuje nad remediacją. Nie ma to wpływu na kanały SMS, webhook i inne kanały powiadamiania. W międzyczasie zalecamy sprawdzenie folderu spam / śmieci i dodanie no- response @ iot- notifications.com do listy bezpiecznych nadawców. Będziemy publikować aktualizacje w miarę rozwoju sytuacji.

2. 23 września 2026 15:33 UTCmonitoring

   Fix został wdrożony i e-mail powiadomienia dostawy wrócił do normy. Monitorujemy dokładnie, aby potwierdzić stabilność. Jeśli nadal nie widzisz oczekiwanych wiadomości alarmowych, sprawdź swój folder spam / śmieci i dodaj no- response @ iot- notifications.com do listy bezpiecznych nadawców.

3. 23 września 2026 16:36 UTCresolved

   Ten incydent został rozwiązany. Zidentyfikowaliśmy przyczynę degradacji e-maili i wprowadziliśmy rozwiązanie. Powiadomienia e-mail, w tym e-maile alarmowe, są dostarczane normalnie. Jeśli nadal nie widzisz oczekiwanych wiadomości alarmowych, sprawdź swój folder spam / śmieci i dodaj no- response @ iot- notifications.com do listy bezpiecznych nadawców lub skontaktuj się z naszym zespołem wsparcia.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 10 lipca 2026 19:36 UTCinvestigating

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

2. 10 lipca 2026 19:47 UTCmonitoring

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

3. 10 lipca 2026 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10 lipca 2026 19:51 UTCresolved

   This incident has been resolved.

1. 10 lipca 2026 01:09 UTCinvestigating

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

2. 10 lipca 2026 01:20 UTCmonitoring

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

3. 10 lipca 2026 14:39 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 21 maja 2026 12:41 UTCinvestigating

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

2. 21 maja 2026 12:51 UTCmonitoring

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

3. 21 maja 2026 20:34 UTCresolved

   This incident has been resolved.

1. 14 maja 2026 13:12 UTCinvestigating

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

2. 14 maja 2026 13:22 UTCmonitoring

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

3. 15 maja 2026 14:13 UTCresolved

   This incident has been resolved.

1. 14 maja 2026 13:11 UTCinvestigating

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

2. 14 maja 2026 13:21 UTCmonitoring

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

3. 15 maja 2026 14:13 UTCresolved

   This incident has been resolved.

1. 13 maja 2026 06:14 UTCinvestigating

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

2. 13 maja 2026 06:25 UTCmonitoring

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

3. 13 maja 2026 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13 maja 2026 14:26 UTCresolved

   This incident has been resolved.

1. 6 maja 2026 13:53 UTCinvestigating

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

2. 6 maja 2026 14:03 UTCmonitoring

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

3. 7 maja 2026 14:06 UTCresolved

   This incident has been resolved.

1. 6 maja 2026 13:52 UTCinvestigating

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

2. 6 maja 2026 14:03 UTCmonitoring

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

3. 7 maja 2026 14:06 UTCresolved

   This incident has been resolved.

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

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

3. 21 kwietnia 2026 04:00 UTCmonitoring

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

4. 21 kwietnia 2026 04:28 UTCresolved

   This incident has been resolved.

1. 20 kwietnia 2026 23:43 UTCinvestigating

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

2. 20 kwietnia 2026 23:54 UTCmonitoring

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

3. 21 kwietnia 2026 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21 kwietnia 2026 02:59 UTCresolved

   This incident has been resolved.

1. 16 kwietnia 2026 16:19 UTCinvestigating

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

2. 16 kwietnia 2026 16:30 UTCmonitoring

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

3. 16 kwietnia 2026 21:20 UTCresolved

   This incident has been resolved.

1. 16 kwietnia 2026 06:49 UTCinvestigating

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

2. 16 kwietnia 2026 07:04 UTCmonitoring

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

3. 16 kwietnia 2026 13:13 UTCresolved

   This incident has been resolved.

1. 15 kwietnia 2026 14:39 UTCinvestigating

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

2. 15 kwietnia 2026 14:50 UTCmonitoring

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

3. 15 kwietnia 2026 20:03 UTCresolved

   This incident has been resolved.

1. 10 kwietnia 2026 07:15 UTCinvestigating

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

2. 10 kwietnia 2026 07:26 UTCmonitoring

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

3. 10 kwietnia 2026 19:05 UTCresolved

   This incident has been resolved.

1. 4 lutego 2026 06:41 UTCinvestigating

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

2. 4 lutego 2026 06:59 UTCmonitoring

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

3. 4 marca 2026 16:32 UTCresolved

   This incident has been resolved.

1. 28 stycznia 2026 06:26 UTCinvestigating

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

2. 28 stycznia 2026 07:05 UTCmonitoring

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

3. 28 stycznia 2026 21:08 UTCresolved

   This incident has been resolved.

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

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

3. 27 stycznia 2026 22:26 UTCresolved

   This incident has been resolved.