Live  /  Front  /  Incident

Front: [us-west-1] High API latency currently causing delays

Front · frontapp.comMinor incidentResolved2026-11-04 17:50 UTC
Public — what happened

Summary

Front reported a minor incident in its us-west-1 region beginning at 16:24 UTC on 2026-11-04, in which slower API responses and delays in processing messages meant new messages could take longer to show up in inboxes and some actions were held up. Front said it identified the issue within a couple of minutes and applied a fix by 16:42 UTC. By 16:45 UTC it said most backlogs had cleared, though a few services were still catching up, and at 17:11 UTC it said everything was back to normal. The incident was marked resolved at 17:50 UTC.

Affected

App, Real time events, API and integrations

As listed on Front’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Front against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Front: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Front report →

More from Front

Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.

The full archive is on the Front status & history page.

Related: Front status & history. SquidGrid is not affiliated with Front.