[UbiFunction] Module experiencing degradation

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.

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

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