Looking for an update now? Check the current status, or follow Ubidots for future changes.
97.3%of 37 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
96.7%
30
1
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 2Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
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 no-reply@iot-notifications.com to your safe senders list.
identified
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 no-reply@iot-notifications.com to your safe senders list. We will post updates as the situation progresses.
Legacy Incident Archive
30 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
HTTP
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
Service Unavailable
Source not attested
Last archived state: resolved
View archived record details
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 ...
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.
Service Unavailable
Source not attested
Last archived state: resolved
View archived record details
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.
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.
MQTT
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
MQTT
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
MQTT
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
HTTP
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
MQTT
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
HTTP
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our HTTP data ingestion service and are currently looking into the issue.
MQTT
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We have identified an error with our MQTT publish service and are currently looking into the issue.
