[gmail] Delays on calendar events synchronizing
Front reports delays on calendar events synchronizing in the Calendar component. Front identified the problem, applied a fix, and monitored the results. The incident is resolved and lasted 61 minutes.
State
Resolved
Started
Lasted
1 h 1 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
30 min 49%
Identified
21 min 34%
Monitoring
10 min 16%
Updates
Times in UTCAs posted by Front
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are scaling up our calendar workers and are seeing improvements in syncing delays.
We are seeing delays of a few minutes for new or updated calendar events to sync. We are currently investigating.
Affected components
1Front in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
1 h 26 min
This incident
29% shorter than the median
Other Front incidents
All incidents
Front·[by_company_00015] Delays on channel imports for a subset of us-west-1 customers
Front reports delays on channel imports for the Other channels component. The issue affects a subset of us-west-1 customers. Front states that the incident is resolved and that it lasted about 5 hours and 10 minutes.
Front·Front mobile SSO login degraded
Front mobile SSO login did not work on the latest version of the mobile app. Front reported the incident as resolved. The outage lasted about 4 hours and 22 minutes.
Front·[us-west-1] High API latency currently causing delays
Front reported high API latency in the us-west-1 region. The App, Real time events, and API and integrations components had degraded performance. Front reported the incident resolved after 86 minutes.
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.
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