Ubidots Outage History
Uptime record, past incidents, and downtime history for Ubidots.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| June 2026 | 0% | 27 | 27 |
| May 2026 | 0% | 31 | 31 |
| April 2026 | 0% | 30 | 30 |
| March 2026 | 33.3% | 3 | 2 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Mar 29
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
June 2026
TCP
Started: Jun 10, 6:47 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 10, 7:10 AM
investigating
We have identified an error with our TCP data ingestion service and are currently looking into the issue.
Jun 10, 6:47 AM
MQTT
Started: Jun 3, 11:45 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 3, 12:03 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Jun 3, 11:45 AM
HTTP
Started: Jun 3, 11:44 AM
monitoring
A fix has been implemented and we are monitoring the results.
Jun 3, 11:55 AM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
Jun 3, 11:44 AM
May 2026
MQTT
Started: May 27, 3:32 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 27, 3:42 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 27, 3:32 PM
HTTP
Started: May 27, 3:31 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 27, 3:41 PM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
May 27, 3:31 PM
Service Unavailable
Started: May 27, 1:14 PM
monitoring
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 support@ubidots.com. We ...
May 27, 1:32 PM
investigating
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.
May 27, 1:14 PM
Service Unavailable
Started: May 26, 3:35 PM
monitoring
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.
May 26, 3:59 PM
investigating
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.
May 26, 3:35 PM
MQTT
Started: May 21, 12:41 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 21, 12:51 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 21, 12:41 PM
MQTT
Started: May 20, 9:54 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 20, 10:05 AM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 20, 9:54 AM
MQTT
Started: May 14, 1:12 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 14, 1:22 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 14, 1:12 PM
HTTP
Started: May 14, 1:11 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 14, 1:21 PM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
May 14, 1:11 PM
MQTT
Started: May 13, 6:14 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 13, 6:25 AM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 13, 6:14 AM
HTTP
Started: May 13, 6:13 AM
monitoring
A fix has been implemented and we are monitoring the results.
May 13, 6:23 AM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
May 13, 6:13 AM
MQTT
Started: May 6, 1:53 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 6, 2:03 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
May 6, 1:53 PM
HTTP
Started: May 6, 1:52 PM
monitoring
A fix has been implemented and we are monitoring the results.
May 6, 2:03 PM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
May 6, 1:52 PM
April 2026
MQTT & EVENTS
Started: Apr 21, 2:59 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 21, 4:00 AM
identified
The issue has been identified and a fix is being implemented.
Apr 21, 4:00 AM
investigating
We have identified an error with our MQTT data ingestion service and Events engine are currently looking into the issue.
Apr 21, 2:59 AM
HTTP
Started: Apr 20, 11:43 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 20, 11:54 PM
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
Apr 20, 11:43 PM
MQTT
Started: Apr 20, 11:14 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 20, 11:25 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 20, 11:14 PM
MQTT
Started: Apr 16, 4:19 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 16, 4:30 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 16, 4:19 PM
MQTT
Started: Apr 16, 6:49 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 16, 7:04 AM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 16, 6:49 AM
MQTT
Started: Apr 15, 2:39 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 15, 2:50 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 15, 2:39 PM
MQTT
Started: Apr 14, 3:58 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 14, 4:08 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 14, 3:58 PM
MQTT
Started: Apr 10, 4:00 PM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 4:12 PM
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
Apr 10, 4:00 PM
TCP
Started: Apr 10, 7:15 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 10, 7:26 AM
investigating
We have identified an error with our TCP data ingestion service and are currently looking into the issue.
Apr 10, 7:15 AM