Störungsverlauf von Ubidots

1. 23. September 2026 um 13:38 UTCidentified

   Wir haben ein Problem identifiziert, das die Zustellung von E-Mail-Benachrichtigungen, einschließlich Alarm-E-Mails, beeinflusst. Einige Nachrichten können verspätet ankommen oder in Spam / Junk-Ordner gefiltert werden. Unser Team arbeitet aktiv an der Sanierung. SMS, Webhook und andere Benachrichtigungskanäle sind nicht betroffen. In der Zwischenzeit empfehlen wir Ihnen, Ihren Spam- / Junk-Ordner zu überprüfen und [email protected] zu Ihrer sicheren Absenderliste hinzuzufügen. Wir werden Updates veröffentlichen, wenn die Situation fortschreitet.

2. 23. September 2026 um 15:33 UTCmonitoring

   Ein Fix wurde implementiert und die E-Mail-Benachrichtigungszustellung ist wieder normal. Wir beobachten genau, um die Stabilität zu bestätigen. Wenn Sie immer noch keine erwarteten Benachrichtigungen sehen, überprüfen Sie bitte Ihren Spam / Junk-Ordner und fügen Sie [email protected] zu Ihrer sicheren Absenderliste hinzu.

3. 23. September 2026 um 16:36 UTCresolved

   Dieser Vorfall wurde behoben. Wir haben die Ursache für die Verschlechterung der E-Mail-Zustellung identifiziert und einen Fix bereitgestellt. E-Mail-Benachrichtigungen, einschließlich Alarm-E-Mails, werden normal zugestellt. Wenn Sie immer noch keine erwarteten Benachrichtigungen sehen, überprüfen Sie bitte Ihren Spam- / Junk-Ordner und fügen Sie [email protected] zu Ihrer sicheren Absenderliste hinzu oder kontaktieren Sie unser Support-Team.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 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 um 19:47 UTCmonitoring

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

3. 10. Juli 2026 um 19:50 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 10. Juli 2026 um 19:51 UTCresolved

   This incident has been resolved.

1. 10. Juli 2026 um 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 um 01:20 UTCmonitoring

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

3. 10. Juli 2026 um 14:39 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

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

   This incident has been resolved.

1. 21. Mai 2026 um 12:41 UTCinvestigating

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

2. 21. Mai 2026 um 12:51 UTCmonitoring

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

3. 21. Mai 2026 um 20:34 UTCresolved

   This incident has been resolved.

1. 14. Mai 2026 um 13:12 UTCinvestigating

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

2. 14. Mai 2026 um 13:22 UTCmonitoring

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

3. 15. Mai 2026 um 14:13 UTCresolved

   This incident has been resolved.

1. 14. Mai 2026 um 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 um 13:21 UTCmonitoring

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

3. 15. Mai 2026 um 14:13 UTCresolved

   This incident has been resolved.

1. 13. Mai 2026 um 06:14 UTCinvestigating

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

2. 13. Mai 2026 um 06:25 UTCmonitoring

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

3. 13. Mai 2026 um 14:26 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 13. Mai 2026 um 14:26 UTCresolved

   This incident has been resolved.

1. 6. Mai 2026 um 13:53 UTCinvestigating

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

2. 6. Mai 2026 um 14:03 UTCmonitoring

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

3. 7. Mai 2026 um 14:06 UTCresolved

   This incident has been resolved.

1. 6. Mai 2026 um 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 um 14:03 UTCmonitoring

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

3. 7. Mai 2026 um 14:06 UTCresolved

   This incident has been resolved.

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

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

3. 21. April 2026 um 04:00 UTCmonitoring

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

4. 21. April 2026 um 04:28 UTCresolved

   This incident has been resolved.

1. 20. April 2026 um 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 um 23:54 UTCmonitoring

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

3. 21. April 2026 um 02:58 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 21. April 2026 um 02:59 UTCresolved

   This incident has been resolved.

1. 16. April 2026 um 16:19 UTCinvestigating

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

2. 16. April 2026 um 16:30 UTCmonitoring

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

3. 16. April 2026 um 21:20 UTCresolved

   This incident has been resolved.

1. 16. April 2026 um 06:49 UTCinvestigating

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

2. 16. April 2026 um 07:04 UTCmonitoring

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

3. 16. April 2026 um 13:13 UTCresolved

   This incident has been resolved.

1. 15. April 2026 um 14:39 UTCinvestigating

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

2. 15. April 2026 um 14:50 UTCmonitoring

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

3. 15. April 2026 um 20:03 UTCresolved

   This incident has been resolved.

1. 10. April 2026 um 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 um 07:26 UTCmonitoring

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

3. 10. April 2026 um 19:05 UTCresolved

   This incident has been resolved.

1. 4. Februar 2026 um 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 um 06:59 UTCmonitoring

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

3. 4. März 2026 um 16:32 UTCresolved

   This incident has been resolved.

1. 28. Januar 2026 um 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 um 07:05 UTCmonitoring

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

3. 28. Januar 2026 um 21:08 UTCresolved

   This incident has been resolved.

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

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

3. 27. Januar 2026 um 22:26 UTCresolved

   This incident has been resolved.