pingoru pingoru UI Bakery had 8 outages in the last 2 years totaling 106h 37m of downtime, averaging 0.3 incidents per month.
There were 8 UI Bakery outages since January 21, 2025 totaling 106h 37m of downtime. Each is summarised below. Incident details, duration, and resolution information.
Issues with access to AI vendor (Anthropic): https://status.claude.com/incidents/437swp24nrf4
The issue has been identified and a fix is being implemented by Anthropic.
Anthropic resolved the incident.
We're currently investigating the issue. Please expect a hotfix soon.
The issue has been identified, and a hotfix is on the way.
The license controller has been fixed. Access to Google SSO has been restored.
We are currently investigating the issue.
Incident has been resolved: blocking database migrations and optimizations have been postponed.
Root cause identified, fix has been implemented.
The issue has been identified, the team is working on the hotfix.
The EU Data Source service has been successfully restored. We are committed to thoroughly analyzing its performance and will take proactive steps to enhance its stability in the future.
UI Bakery's billing service was under a card testing attack. We temporarily disabled payments on the cloud instance to mitigate risks. System operation is not affected, and data is secure. The payment system will be activated later.
Billing service is up and running.
We are currently experiencing low performance in our cloud infrastructure, which may affect your services and applications. As a result, Audit Logs are temporarily unavailable. Our team is actively investigating the issue and working to restore normal functionality as quickly as possible. We appreciate your patience and understanding during this time. Please stay tuned for further updates.
The following Audit Logs are temporarily disabled: - Action: request performance metrics - Action: success System performance is back to normal.
All systems nominal.
We are experiencing issues with database queries on the cloud instance. Our team is actively working on identifying and resolving the root cause to restore normal operation.
The database is now operational, and we will continue monitoring its performance.
Since the recent hotfix, we have not detected any errors, indicating improved stability. We are investigating the DB access issues that occurred and planning enhancements.