# App not responding - Provider: [Front](https://down.guide/front) - Level: confirmed - Impact: Major outage - lasted 3h 54m - started 2025-12-19 17:29 UTC - App - eu, eu-west-1, us, us-west-1 - id: DWN-b2247fcab8 - Official page: https://stspg.io/xnc95k7qyppy ## Updates from Front ### 2025-12-19 15:13 UTC: investigating We are currently investigating the issue. \[us-west-1\], \[us-west-2\] ### 2025-12-19 16:06 UTC: investigating We are continuing to investigate this issue. ### 2025-12-19 16:47 UTC: identified The issue has been identified and a fix is being implemented. ### 2025-12-19 17:29 UTC: monitoring A fix has been implemented and we are monitoring the results. We are seeing recovery but continuing to close out remaining recovery items. ### 2025-12-19 17:57 UTC: monitoring We are continuing to monitor and close our our remaining recovery items for \[us-west-2\] customers. Other regions are recovered. ### 2025-12-19 18:23 UTC: monitoring Front is operational for all customers. We are continuing to backfill any missed messages and application webhooks. ### 2025-12-19 21:23 UTC: resolved All backfills complete ### 2025-12-19 23:21 UTC: postmortem On Friday, Dec 19, at 14:50 UTC \\(6:50am PST\\), customers backed in our US-West-2 data center experienced dramatically increased API latency, resulting in the website failing to load and messages being queued in the backend. This continued until 18:10 UTC \\(10:10am PST\\). During this time no messages were lost, though there may have been a significant delay for messages to appear in customer inboxes. All queued messages were delivered by 21:00 \\(1:00pm PST\\). ‌ Customers based in Front’s EU-West-1 and US-West-1 datacenters may have experienced some delays during this time, as some systems are interdependent, but this impact was intermittent and uncommon. ‌ The root cause of this issue was the failure of a caching system. There are several database systems that support the Front application, which are supported by caching to improve performance. A recent change increased the size of some objects in the cache layer. This is not inherently wrong, and did not have any immediate impact. On Friday the 19th the caching layer in US-West-2 crossed a new threshold of data volume which triggered a large number of evictions, particularly of other data that is necessary for most application activity. Besides putting additional load on the databases, there was simply not enough room in the cache for all the data we needed to store there. This caused a high amount of thrashing that significantly increased latency for all systems. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).