Ubidots 中断历史

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

This incident has been resolved.

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.

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 will confirm full resolution shortly.

This incident has been resolved.

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.

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.

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

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

This incident has been resolved.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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.

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

This incident has been resolved.

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

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

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.