[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.
The latest update from Front.
State
Resolved
Started
40 d ago
2026-09-23 10:38 UTC
Lasted
4 h 23 min
until 2026-09-23 15:01 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
2 h 9 min 49%
Monitoring
2 h 14 min 51%
Updates
Times in UTCAs posted by Front
This incident has been resolved.
We have deployed a fix and delivery times are returning to normal. Some channels are still catching up on a backlog of messages. We are continuing to monitor the health of our systems.
We are continuing to investigate the issue.
We are experiencing delays in processing Office 365 and Gmail messages. Both sending and receiving are impacted. We are investigating.
Affected components
2Front in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
7
Median duration
1 h 8 min
This incident
3.9× 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] Delays in sending and receiving messages for some customers in [us-west-1] and [us-west-2]
This incident has been resolved.
Front·Application performance degraded
This incident has been resolved, and all activities have caught up to realtime. Front will continue to monitor application performance.
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