Ubidots Outage History

This incident has been resolved. We identified the root cause of the email delivery degradation and deployed a fix. Email notifications, including alert emails, are being delivered normally. If you still don't see expected alert emails, please check your spam/junk folder and add [email protected] to your safe senders list, or contact our support team.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

Summary: We identified an issue that limited the number of active connections to one of our servers. The root cause was a kernel-level restriction on the maximum number of open files (file descriptors), which also affects network sockets. Impact: The limitation caused a temporary reduction in the number of simultaneous connections the server could handle, potentially affecting availability for some users. Resolution: The kernel and system-level limits for open files were increased to ensure sufficient capacity for concurrent connections. After applying the changes and restarting the affected services, the system returned to normal operation. Preventive Actions: We’ve updated our configuration management to enforce higher default limits across all environments, preventing similar constraints in the future. Status: This incident has been fully resolved, and all systems are operating normally.

Incident window: September 25, 2025 – 7:00 PM (UTC-5) to September 26, 2025 – 4:20 AM (UTC-5) Impact: During the incident window, MQTT subscriptions experienced disruptions that prevented data from being delivered in real time. Devices attempting to subscribe or maintain subscriptions may have encountered failures, delays, or missing data. Resolution: Our engineering team identified abnormal connection behavior that led to message queue saturation within the MQTT service. To restore functionality, queues were purged, affected MQTT clients were reset, and supporting services were restarted. Service was fully restored by 4:20 AM (UTC-5) on September 26. Current Status: The MQTT service is operating normally, and monitoring has been reinforced to ensure stability.

Webflow has implemented a fix which mean our website (ubidots.com) is working as expected.

This incident has been resolved.

We have replaced old CDN links, serving libraries used in the HTML canvas widget, Widget plugins and Pages, for new one that do not error.

The platform is back operational. The latency was raise because of an unexpected spike in request to create variables. Our team quickly caught this situation in order to prevent further spreading of the latency. There are measures being taken to prevent this from happening again, particularly, we will isolate those variable creation request in a dedicated infraestrucutre.

This incident has been resolved.

The AU deployment experienced an outage because of a sudden spike in data reception, which overloaded the servers and hence the web app was slow to read and display data. Start time: 10:30 PM UTC-5 End time: 11:15 PM UTC-5 Total time: 45 min During this time: – All data was correctly saved. – Real time update in dashboard was interrupted. – The events engine was taking up to 4 minutes to trigger events.

Our DevOps team ran a maintenance task consisting of updating our servers packages. This is standard procedure to guarantee the instances are up to day with the latest security patches or package versions. This task took about 5 minutes to complete, where reading data was slow. No data was lost during this time window.

This incident has been resolved.

This incident has been resolved.