Customers in the APAC and EU regions were unable to access Pivot and were presented with a capacity-related error page instead of the application. Our engineers identified that the storage area used by the underlying database to record ongoing changes had reached its capacity limit, which prevented new activity from being written and caused database sessions to pause, halting the application's ability to serve requests. Initial analysis points to a scheduled routine that performs extensive monthly calculations and data processing having consumed that capacity; this is being validated through a formal Post-Incident Review before final confirmation. We restored service by releasing the blocked sessions and freeing space in the database logging area, after which processing resumed and full application

We are expanding the capacity of the database logging resources supporting Pivot — a fivefold increase has already been applied — to ensure normal and peak processing volumes can be absorbed without reaching a limit.

We are revising the scheduled monthly process that contributed to this event; it has been paused in production and is being redesigned into smaller, incremental components that will undergo stress testing in non-production environments before reintroduction.