Ubidots driftsforstyrrelser

1. 23. september 2026 kl. 13.38 UTCidentified

   Vi har identificeret et problem, der påvirker leveringen af e-mail-meddelelser, herunder alarme-mails. Nogle beskeder kan ankomme sent eller blive filtreret ind i spam / junk mapper. Vores team arbejder aktivt på oprydning. SMS, webhook og andre meddelelseskanaler berøres ikke. I mellemtiden anbefaler vi at tjekke din spam / junk mappe og tilføje no- reply @ iot- notifications.com til din sikker afsenderliste. Vi vil sende opdateringer som situationen skrider frem.

2. 23. september 2026 kl. 15.33 UTCmonitoring

   En rettelse er blevet gennemført og e-mail-meddelelse levering er vendt tilbage til normal. Vi overvåger nøje for at bekræfte stabiliteten. Hvis du stadig ikke kan se forventede alarm e-mails, skal du tjekke din spam / junk mappe og tilføje no-reply @ iot- notifications.com til din sikker afsenderliste.

3. 23. september 2026 kl. 16.36 UTCresolved

   Denne hændelse er blevet løst. Vi identificerede årsagen til nedbrydningen af e-mail-levering og sendte et fix. E-mail-meddelelser, herunder alarme-mails, leveres normalt. Hvis du stadig ikke kan se forventede alarm e-mails, skal du tjekke din spam / junk mappe og tilføje no- reply @ iot- notifications.com til din sikker afsenderliste, eller kontakte vores support team.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 19.36 UTCinvestigating

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

2. 10. juli 2026 kl. 19.47 UTCmonitoring

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

3. 10. juli 2026 kl. 19.50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. juli 2026 kl. 19.51 UTCresolved

   This incident has been resolved.

1. 10. juli 2026 kl. 01.09 UTCinvestigating

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

2. 10. juli 2026 kl. 01.20 UTCmonitoring

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

3. 10. juli 2026 kl. 14.39 UTCresolved

   This incident has been resolved.

1. 27. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 13.47 UTCresolved

   This incident has been resolved.

1. 26. maj 2026 kl. 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. maj 2026 kl. 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. maj 2026 kl. 13.15 UTCresolved

   This incident has been resolved.

1. 21. maj 2026 kl. 12.41 UTCinvestigating

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

2. 21. maj 2026 kl. 12.51 UTCmonitoring

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

3. 21. maj 2026 kl. 20.34 UTCresolved

   This incident has been resolved.

1. 14. maj 2026 kl. 13.12 UTCinvestigating

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

2. 14. maj 2026 kl. 13.22 UTCmonitoring

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

3. 15. maj 2026 kl. 14.13 UTCresolved

   This incident has been resolved.

1. 14. maj 2026 kl. 13.11 UTCinvestigating

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

2. 14. maj 2026 kl. 13.21 UTCmonitoring

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

3. 15. maj 2026 kl. 14.13 UTCresolved

   This incident has been resolved.

1. 13. maj 2026 kl. 06.14 UTCinvestigating

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

2. 13. maj 2026 kl. 06.25 UTCmonitoring

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

3. 13. maj 2026 kl. 14.26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13. maj 2026 kl. 14.26 UTCresolved

   This incident has been resolved.

1. 6. maj 2026 kl. 13.53 UTCinvestigating

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

2. 6. maj 2026 kl. 14.03 UTCmonitoring

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

3. 7. maj 2026 kl. 14.06 UTCresolved

   This incident has been resolved.

1. 6. maj 2026 kl. 13.52 UTCinvestigating

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

2. 6. maj 2026 kl. 14.03 UTCmonitoring

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

3. 7. maj 2026 kl. 14.06 UTCresolved

   This incident has been resolved.

1. 21. april 2026 kl. 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. april 2026 kl. 04.00 UTCidentified

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

3. 21. april 2026 kl. 04.00 UTCmonitoring

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

4. 21. april 2026 kl. 04.28 UTCresolved

   This incident has been resolved.

1. 20. april 2026 kl. 23.43 UTCinvestigating

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

2. 20. april 2026 kl. 23.54 UTCmonitoring

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

3. 21. april 2026 kl. 02.58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21. april 2026 kl. 02.59 UTCresolved

   This incident has been resolved.

1. 16. april 2026 kl. 16.19 UTCinvestigating

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

2. 16. april 2026 kl. 16.30 UTCmonitoring

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

3. 16. april 2026 kl. 21.20 UTCresolved

   This incident has been resolved.

1. 16. april 2026 kl. 06.49 UTCinvestigating

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

2. 16. april 2026 kl. 07.04 UTCmonitoring

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

3. 16. april 2026 kl. 13.13 UTCresolved

   This incident has been resolved.

1. 15. april 2026 kl. 14.39 UTCinvestigating

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

2. 15. april 2026 kl. 14.50 UTCmonitoring

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

3. 15. april 2026 kl. 20.03 UTCresolved

   This incident has been resolved.

1. 10. april 2026 kl. 07.15 UTCinvestigating

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

2. 10. april 2026 kl. 07.26 UTCmonitoring

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

3. 10. april 2026 kl. 19.05 UTCresolved

   This incident has been resolved.

1. 4. februar 2026 kl. 06.41 UTCinvestigating

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

2. 4. februar 2026 kl. 06.59 UTCmonitoring

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

3. 4. marts 2026 kl. 16.32 UTCresolved

   This incident has been resolved.

1. 28. januar 2026 kl. 06.26 UTCinvestigating

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

2. 28. januar 2026 kl. 07.05 UTCmonitoring

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

3. 28. januar 2026 kl. 21.08 UTCresolved

   This incident has been resolved.

1. 26. januar 2026 kl. 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. januar 2026 kl. 20.06 UTCmonitoring

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

3. 27. januar 2026 kl. 22.26 UTCresolved

   This incident has been resolved.