Incidents reported on status page for Serif Health https://status.serifhealth.com/ https://d1lppblt9t2x15.cloudfront.net/logos/a75afa22bf823bfa72cbc86e462e28cd.png https://status.serifhealth.com/ en https://status.serifhealth.com/incident/863396 Thu, 02 Apr 2026 13:28:00 -0000 https://status.serifhealth.com/incident/863396#fb61b3a9f528a196d6adb48a75749d42fec53369a26abadd5221c83fde9577e4 We attempted to mitigate TCP connection drops with our vendor and eventually migrated multiple databases into a new AZ. As of 8:50 last night, we haven't seen further TCP connection drops. We will continue monitoring the situation today and will reopen this incident if needed. https://status.serifhealth.com/incident/747451 Mon, 20 Oct 2025 21:51:00 -0000 https://status.serifhealth.com/incident/747451#2794dcedb22905f431feead99cfd1a3e05fa33ad5f332634173290f0510ebbb5 AWS has resolved all underlying issues and we haven't seen errors throughout our application or APIs since late afternoon EST. https://status.serifhealth.com/incident/747451 Mon, 20 Oct 2025 15:39:00 -0000 https://status.serifhealth.com/incident/747451#f3a5b467756807471a7e25e1234ccbd4e4a5bff339fdaad4e97f2801a1297e49 We are tracking an AWS outage and potential impact to our services. Some dependencies of our Signal and API products have experienced intermittent errors, but at this time, all Serif Health services are remaining within SLA. See https://health.aws.amazon.com/health/status for more details. https://status.serifhealth.com/incident/658704 Fri, 01 Aug 2025 19:00:00 -0000 https://status.serifhealth.com/incident/658704#573de7759589c991e5c2485a2ed33feb4f84c5bb836121918090e0b9d8250e6f Find Care data loads completed and the June rollback has been resolved. All data should be updated to July. https://status.serifhealth.com/incident/658704 Wed, 30 Jul 2025 19:02:00 -0000 https://status.serifhealth.com/incident/658704#797e2add365b9cafd42cd1074fe6ca771de918f7eed2bd3db7474025c6153abb Rollback has completed and we have a root cause - the issue was due to our underlying database engine reporting a completed import while in reality aborting the load too soon. Colocated cluster will remain on June data until we can completely repopulate the July table. https://status.serifhealth.com/incident/658704 Wed, 30 Jul 2025 18:07:00 -0000 https://status.serifhealth.com/incident/658704#ba7dccd3d7b8273a13fb32ef306530f94edfc4820885b18958c90a5cfa34eee4 Our Find Care colocated cluster swapped to July data last night, but data volume in the updated table is unexpectedly low. We are reverting the change and will hold the data pool back to June until we resolve and reload July data.