Last updated: March 22, 2025 — 14:30 UTC · Subscribe to updates
No active incidents. All platform components performing within normal parameters.
Monitoring customers in the APAC Singapore region experienced elevated API response times (p95 > 2s vs SLA 500ms) due to a database connection pool exhaustion event triggered by a burst in concurrent metric writes. The root cause was a misconfigured connection pool limit introduced in the v4.2.1 deployment. The fix was deployed within 30 minutes of detection; full recovery confirmed at 11:42 UTC. Affected: ~340 customers. All data was preserved — no data loss occurred.
Planned maintenance window for platform upgrade to v4.3.0, including Automation Engine performance improvements, Compliance Report Engine upgrade to v8.2, and time-series database compression policy update. All services restored within the announced maintenance window. No data loss. Post-maintenance check confirmed all modules operational.