Fluid Attacks Outage History

This confirms the incident reported by Checkly for the DATABASE check (Web Group, production tag) was a false alert. The cause was a change to the page title, which the e2e test compared against an exact match ("Fluid Attacks Database"). The database remained available throughout, with no real impact to the service.

This incident has been resolved. Between 06:52 and 07:12 UTC-5, monitoring detected a single degraded request out of 118 total checks (117 passing, 0 failing). Average response time remained stable at 702 ms, and overall availability held at 99%. The degradation was isolated to one query and did not represent a systemic issue or service disruption. No further degraded or failing requests have been observed since, and the AGENT is operating normally.

This incident has been resolved. Between 01:42 and 02:02 UTC-5, monitoring detected a single failing request out of 118 total checks (117 passing, 0 degraded). Average response time remained stable at 546 ms. The failure was isolated to one query and did not represent a systemic issue or a sustained service disruption. No further failing or degraded requests have been observed since, and the API is operating normally.

This incident has been resolved.