Ubidots Outage History

Ubidots is up right now

Ubidots had 9 outages in the last 2 years totaling 278h 49m of downtime — averaging 0.4 incidents per month.

There were 9 Ubidots outages since October 31, 2025 totaling 278h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.ubidots.com

Minor September 23, 2026

Degraded email notification delivery

Detected by Pingoru
Sep 23, 2026, 01:38 PM UTC
Resolved
Sep 23, 2026, 04:36 PM UTC
Duration
2h 57m
Affected: Events EngineEvents Engine
Timeline · 3 updates
  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

Detected by Pingoru
Jul 10, 2026, 07:37 PM UTC
Resolved
Jul 10, 2026, 08:00 PM UTC
Duration
22m
Timeline · 2 updates
  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

Detected by Pingoru
Jul 10, 2026, 07:36 PM UTC
Resolved
Jul 10, 2026, 07:51 PM UTC
Duration
14m
Affected: MQTT PublishTCPHTTP
Timeline · 4 updates
  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

Detected by Pingoru
Jul 10, 2026, 01:09 AM UTC
Resolved
Jul 10, 2026, 02:39 PM UTC
Duration
13h 30m
Timeline · 3 updates
  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

Detected by Pingoru
Jul 03, 2026, 06:50 AM UTC
Resolved
Jul 10, 2026, 07:30 PM UTC
Duration
7d 12h
Timeline · 3 updates
  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

Detected by Pingoru
May 27, 2026, 01:14 PM UTC
Resolved
May 28, 2026, 01:47 PM UTC
Duration
1d
Affected: Login Apps
Timeline · 3 updates
  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

Detected by Pingoru
Apr 21, 2026, 02:59 AM UTC
Resolved
Apr 21, 2026, 04:28 AM UTC
Duration
1h 28m
Affected: MQTT PublishMQTT SubscribeEvents Engine
Timeline · 4 updates
  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

Detected by Pingoru
Jan 26, 2026, 05:08 PM UTC
Resolved
Jan 27, 2026, 10:26 PM UTC
Duration
1d 5h
Affected: Synthetic Variables
Timeline · 3 updates
  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

Detected by Pingoru
Oct 31, 2025, 01:28 PM UTC
Resolved
Nov 01, 2025, 03:12 PM UTC
Duration
1d 1h
Affected: Functions
Timeline · 3 updates
  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 →