Resolution
Fix deployed, SLOs recovering, post-mortem
The config change that resolved the incident is documented here. Tracefox links the deployment event back to the open incident automatically — no manual ticket chasing required.
Recovery story
A single config change — db connection pool size increased — stopped the error cascade. Tracefox linked the deployment event to the open incident automatically, closing the loop without a manual update. The SLO returned to target within 2.6 hours of the fix landing.
Fix deployed
Increased the HikariCP connection pool size from 10 to 25 in payment-service. The pool had been exhausted under peak checkout load, causing all incoming requests to queue and eventually time out.
Alert cleared
SLO recovering
After the fix was deployed, the SLO burn rate fell from above-alert levels down to 1× baseline over 2.6 hours. The SLO window is no longer in breach and the error budget has begun recovering. No further action is required.