https://status.optilogic.app/affected/databases/Incident historygithub.com/cstateen2026-05-13T13:55:00+00:002026-05-13T13:55:00+00:00https://status.optilogic.app/issues/2026-05-13-slow-api-performance/Wed, 13 May 2026 13:55:00 +0000https://status.optilogic.app/issues/2026-05-13-slow-api-performance/2026-05-13 16:17:00Degraded Performance, Investigating - We were alerted to high latency on API calls centered around database storage endpoints. We are investigating the issue. (13:55 UTC — May 13) Degraded Performance, Identified - We have identified CPU pressure as the cause of the API latency and are working on mitigation strategies. (14:10 UTC — May 13) Degraded Performance, Mitigating - Several mitigation strategies have had no effect on the elevated CPU pressure.<p><em>Degraded Performance, Investigating</em> - We were alerted to high latency on API calls centered around database storage endpoints. We are investigating the issue. <span class="faded">(13:55 UTC — May 13)</span> </p> <p><em>Degraded Performance, Identified</em> - We have identified CPU pressure as the cause of the API latency and are working on mitigation strategies. <span class="faded">(14:10 UTC — May 13)</span> </p> <p><em>Degraded Performance, Mitigating</em> - Several mitigation strategies have had no effect on the elevated CPU pressure. We are moving query traffic over to a larger metadata server to provide pressure relief. <span class="faded">(15:59 UTC — May 13)</span> </p> <p><em>Operational, Monitoring</em> - The traffic move is complete, CPU pressure has been reduced, and request performance has dropped to normal levels. We will continue to monitor the system. <span class="faded">(16:17 UTC — May 13)</span> </p>