The incident has been resolved. Container image pulls have returned to normal, all affected system components have recovered, and cluster nodes are reporting a healthy Ready status. Services are operating normally, and no further impact is being observed. We will continue to review the incident and implement any necessary preventive measures to reduce the likelihood of similar occurrences in the future.

The rate limiting condition has subsided and image pulls are succeeding again. System components are recovering, affected pods are being recreated successfully, and nodes are returning to a Ready state. We are closely monitoring cluster health and workload recovery to ensure all services return to normal operation.

We have identified the root cause of the issue. Image pulls from the container registry were being rate limited, resulting in HTTP 429 (Too Many Requests) responses. Due to these image pull failures, critical system pods were unable to start, causing nodes to report NotReady status and impacting cluster functionality. We are monitoring recovery as image pull requests begin succeeding again.

We are currently investigating an issue affecting multiple Kubernetes clusters. Several nodes transitioned to a NotReady state, resulting in degraded cluster operations. During the investigation, we observed image pull failures across critical system components, preventing some workloads from starting successfully.

The issue has been resolved, and the server is now back online and operating normally. We apologize for any inconvenience or disruption this may have caused.

We are continuing to monitor the environment closely to ensure stability. Please reach out to team.support@fareye.com for any questions or concerns.

We have restarted the database after it became unresponsive. Once the database is back online and the application has fully recovered, traffic will start flowing normally.

We are continuing to monitor the situation closely. For any questions or concerns, please reach out to team.support@fareye.com.

We have determined that the database is down due to an issue on the Azure side. As a result, the affected applications are impacted, and users are unable to log in.

Our team is actively monitoring the situation and working towards resolution. For any questions or concerns, please reach out to team.support@fareye.com.

We are currently experiencing issue with database. Our team is working to identify the root cause and fix the issue. Users may be experiencing issue while login. Please reach out to team.support@fareye.com for any questions.