Ubidots Outage History

Ubidots is up right now

Pingoru has recorded 62 incidents for Ubidots: 33 in the last 12 months and 1 in the last 90 days.

Source: status.ubidots.com

62incidents recorded
33last 12 months
1last 90 days
37 hourstypical duration
Incidents per month
01020AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Ubidots in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026734 of 720 (5%)
May 202612113 of 744 (15%)
June 2026332 of 720 (4%)
July 20266194 of 744 (26%)
August 202600 of 744 (0%)
September 202613 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Minor September 23, 2026 Degraded email notification delivery 2h 57m Events Engine, Events Engine

Started Sep 23, 2026, 01:38 PM UTC· resolved Sep 23, 2026, 04:36 PM UTC

  1. identified Sep 23, 2026, 01:38 PM UTC

    We have identified an issue affecting the delivery of email notifications, including alert emails. Some messages may arrive late or be filtered into spam/junk folders. Our team is actively working on remediation. SMS, webhook and other notification channels are not affected. In the meantime, we recommend checking your spam/junk folder and adding [email protected] to your safe senders list. We will post updates as the situation progresses.

  2. monitoring Sep 23, 2026, 03:33 PM UTC

    A fix has been implemented and email notification delivery has returned to normal. We are monitoring closely to confirm stability. If you still don't see expected alert emails, please check your spam/junk folder and add [email protected] to your safe senders list.

  3. resolved Sep 23, 2026, 04:36 PM UTC

    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.

Read the full incident report →

Notice July 10, 2026 MQTT 22m

Started Jul 10, 2026, 07:37 PM UTC· resolved Jul 10, 2026, 08:00 PM UTC

  1. investigating Jul 10, 2026, 07:37 PM UTC

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

  2. monitoring Jul 10, 2026, 07:48 PM UTC

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

Read the full incident report →

Notice July 10, 2026 HTTP, MQTT & TCP 14m MQTT Publish, TCP, HTTP

Started Jul 10, 2026, 07:36 PM UTC· resolved Jul 10, 2026, 07:51 PM UTC

  1. investigating Jul 10, 2026, 07:36 PM UTC

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

  2. monitoring Jul 10, 2026, 07:47 PM UTC

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

  3. monitoring Jul 10, 2026, 07:50 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jul 10, 2026, 07:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 10, 2026 HTTP 13h 30m

Started Jul 10, 2026, 01:09 AM UTC· resolved Jul 10, 2026, 02:39 PM UTC

  1. investigating Jul 10, 2026, 01:09 AM UTC

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

  2. monitoring Jul 10, 2026, 01:20 AM UTC

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

  3. resolved Jul 10, 2026, 02:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 3, 2026 TCP 7d 12h

Started Jul 03, 2026, 06:50 AM UTC· resolved Jul 10, 2026, 07:30 PM UTC

  1. investigating Jul 03, 2026, 06:50 AM UTC

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

  2. monitoring Jul 03, 2026, 07:03 AM UTC

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

  3. monitoring Jul 10, 2026, 02:40 PM UTC

    We are continuing to monitor for any further issues.

Read the full incident report →

Notice May 27, 2026 Service Unavailable 1d Login Apps

Started May 27, 2026, 01:14 PM UTC· resolved May 28, 2026, 01:47 PM UTC

  1. investigating May 27, 2026, 01:14 PM UTC

    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. monitoring May 27, 2026, 01:32 PM UTC

    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. resolved May 28, 2026, 01:47 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 21, 2026 MQTT & EVENTS 1h 28m MQTT Publish, MQTT Subscribe, Events Engine

Started Apr 21, 2026, 02:59 AM UTC· resolved Apr 21, 2026, 04:28 AM UTC

  1. investigating Apr 21, 2026, 02:59 AM UTC

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

  2. identified Apr 21, 2026, 04:00 AM UTC

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

  3. monitoring Apr 21, 2026, 04:00 AM UTC

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

  4. resolved Apr 21, 2026, 04:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 26, 2026 Synthetic Variables – Increased Latency 1d 5h Synthetic Variables

Started Jan 26, 2026, 05:08 PM UTC· resolved Jan 27, 2026, 10:26 PM UTC

  1. investigating Jan 26, 2026, 05:08 PM UTC

    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. monitoring Jan 26, 2026, 08:06 PM UTC

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

  3. resolved Jan 27, 2026, 10:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 31, 2025 [UbiFunction] Module experiencing degradation 1d 1h Functions

Started Oct 31, 2025, 01:28 PM UTC· resolved Nov 01, 2025, 03:12 PM UTC

  1. investigating Oct 31, 2025, 01:28 PM UTC

    We’ve identified an issue affecting the UbiFunction module. Our DevOps team is currently investigating the root cause.

  2. monitoring Oct 31, 2025, 01:53 PM UTC

    We have restarted the load balancer for the UbiFunction module. This has restored the operation in the module.

  3. resolved Nov 01, 2025, 03:12 PM UTC

    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.

Read the full incident report →

Notice September 26, 2025 MQTT Subscription Disruption –

Started Sep 26, 2025, 12:00 AM UTC· resolved Sep 26, 2025, 12:00 AM UTC

  1. resolved Sep 26, 2025, 03:25 PM UTC

    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.

Read the full incident report →

Notice August 21, 2025 Issues loading ubidots.com website 33m

Started Aug 21, 2025, 07:23 PM UTC· resolved Aug 21, 2025, 07:57 PM UTC

  1. investigating Aug 21, 2025, 07:23 PM UTC

    We are investigating reports of intermittent issues loading our website at ubidots.com, stemming from a third-party provider.

  2. investigating Aug 21, 2025, 07:25 PM UTC

    Our third party website provider Webflow has declared an incident causing widespread outages across multiple websites they serve. As a result, our website (https://ubidots.com) is intermittent. This does not affect our application, blog, community, or documentation; only our website. We are closely monitoring this internally and will continue to provide updates as they become available

  3. resolved Aug 21, 2025, 07:57 PM UTC

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

Read the full incident report →

Minor August 18, 2025 Generalized platform latency Core and API 2h 32m Login Apps

Started Aug 18, 2025, 05:18 PM UTC· resolved Aug 18, 2025, 07:51 PM UTC

  1. investigating Aug 18, 2025, 05:18 PM UTC

    We've identified latencies in the platform. We're unsure of the reason at this moment. Out team is already investigating. We will publish an update in the next 30 minutes.

  2. identified Aug 18, 2025, 06:22 PM UTC

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

  3. resolved Aug 18, 2025, 07:51 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 13, 2025 HTML Canvas and Widget plugins not working 3h 24m Login Apps

Started Aug 13, 2025, 02:41 PM UTC· resolved Aug 13, 2025, 06:05 PM UTC

  1. identified Aug 13, 2025, 02:41 PM UTC

    We have received reports pointing out that the custom widgets built on top of the HTML canvas and Widget plugins module aren't working. The reason is that the CDN serving the built-in Ubidots library, that bridges the widgets with the dashboard controls and allows interaction with the dashboard, stopped working. We are: – Uploading the library to a new CDN – Replacing the URL in the HTML canvas widget and Widget plugin module.

  2. monitoring Aug 13, 2025, 03:30 PM UTC

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

  3. resolved Aug 13, 2025, 06:05 PM UTC

    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.

Read the full incident report →

Minor July 8, 2025 Generalized platform latency 40m Login Apps

Started Jul 08, 2025, 06:50 PM UTC· resolved Jul 08, 2025, 07:31 PM UTC

  1. investigating Jul 08, 2025, 06:50 PM UTC

    We've identified latencies in the platform. We're unsure of the reason at this moment. Out team is already investigating. We will publish an update in the next 30 minutes.

  2. resolved Jul 08, 2025, 07:31 PM UTC

    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.

Read the full incident report →

Minor June 10, 2025 Generalized latency 21h 40m Login Apps

Started Jun 10, 2025, 04:47 PM UTC· resolved Jun 11, 2025, 02:28 PM UTC

  1. investigating Jun 10, 2025, 04:47 PM UTC

    We're experiencing a generalized latency in the platform. Our DevOps team is already working on resolving this issue. We will provide additional information as it becomes available.

  2. resolved Jun 11, 2025, 02:28 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 7, 2025 [AU DEPLOYMENT] Outage 19h 45m

Started Apr 07, 2025, 03:30 AM UTC· resolved Apr 07, 2025, 11:15 PM UTC

  1. resolved Apr 07, 2025, 02:56 PM UTC

    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.

Read the full incident report →

Notice March 18, 2025 Apps with 404 error 1d

Started Mar 18, 2025, 04:00 AM UTC· resolved Mar 19, 2025, 04:41 AM UTC

  1. resolved Mar 18, 2025, 02:30 PM UTC

    Incident Summary: Between 11:00 PM and 4:41 AM UTC-5, some users experienced 404 errors when attempting to access applications deployed in our US region. Root Cause: The issue was traced to an unexpected behavior in our caching mechanism. As part of recent DDoS attack mitigation improvements, changes were made to the cache that inadvertently resulted in these 404 errors. Our apps' cache is set to expire every 7 days, and when the cache expired, the affected applications returned 404 errors. This behavior required manual intervention or periodic tasks to refresh the cache. Resolution: A fix has been deployed to ensure the cache is automatically updated moving forward. We have also implemented additional monitoring checks every 5 minutes to proactively identify and address similar issues. Next Steps: We are exploring additional improvements to further enhance reliability and reduce the risk of similar incidents in the future. We apologize for any inconvenience caused and appreciate your understanding as we continue to improve our systems.

Read the full incident report →

Notice February 28, 2025 Minor downtime: BD servers update –

Started Feb 28, 2025, 12:00 PM UTC· resolved Feb 28, 2025, 12:00 PM UTC

  1. resolved Feb 28, 2025, 03:25 PM UTC

    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.

Read the full incident report →

Minor January 25, 2025 Events 4h Events Engine

Started Jan 25, 2025, 01:30 AM UTC· resolved Jan 25, 2025, 05:30 AM UTC

  1. investigating Jan 25, 2025, 05:22 AM UTC

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

  2. monitoring Jan 25, 2025, 05:22 AM UTC

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

  3. resolved Jan 25, 2025, 11:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2024 MQTT, TCP & HTTP Ingestion [AU] 58m MQTT Publish, TCP, HTTP

Started Dec 09, 2024, 10:06 PM UTC· resolved Dec 09, 2024, 11:04 PM UTC

  1. investigating Dec 09, 2024, 10:06 PM UTC

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

  2. monitoring Dec 09, 2024, 10:17 PM UTC

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

  3. monitoring Dec 09, 2024, 11:04 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Dec 09, 2024, 11:04 PM UTC

    This incident has been resolved.

Read the full incident report →