[us-west-1] High API latency currently causing delays
Front reports high API latency in us-west-1. The App, Real time events, and API and integrations components are degraded. Front applied a fix and reports that all systems have returned to normal, and monitoring continues.
State
Monitoring
Started
Ongoing for
1 h 11 min
Worst impact
Degraded
Timeline
4 updatesIdentified
21 min 29%
Monitoring
50 min 71%
Updates
Times in UTCAs posted by Front
All systems have returned to normal. API latency is back to normal levels and all queues have drained. We will continue monitoring to ensure stability.
Systems are returning to normal. Most processing queues have cleared, and API latency has recovered to normal levels. A few services are still working through remaining backlogs, so some customers may continue to experience delays. We are monitoring recovery closely.
We have applied a fix and currently monitoring our systems.
The issue has been identified and we are currently working to restore performance
Affected components
3Front in the last 90 days
Full historyIncidents in 90 days
8
Days with an incident
8
Median duration
1 h 8 min
This incident
About the median
Other Front incidents
All incidents
Front·Delays on generation of certain AI outputs
This incident has been resolved.
Front·[smtp] Problems with outbound sending on custom SMTP channels
This incident has been resolved.
Front·[us-west-2] Elevated API error rates may cause delays
The upstream issues causing delays in our system have been resolved.
Front·[office365] [gmail] delays in sending and receiving messages for customers in [us-west-1], [us-west-2], and [eu-west-1]
This incident has been resolved.
Front·[office365] Delays in sending and receiving messages for some customers in [us-west-1] and [us-west-2]
This incident has been resolved.
Follow Front
Your coding agent knows when Front is down, and tells you when a failure is theirs, not yours. You can also get Front incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "front" and tell me if Front has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=front/feed subscribe https://outages.live/feed.xml?providers=frontFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane