Front Outage History

Started Nov 04, 2026, 04:24 PM UTC· resolved Nov 04, 2026, 05:50 PM UTC

1. investigating Nov 04, 2026, 04:24 PM UTC

   We are experiencing elevated API latency and delays in message processing. As a result, new messages may take longer than expected to appear in inboxes, and some operations may be delayed due to backlogs in our processing queues.

2. identified Nov 04, 2026, 04:26 PM UTC

   The issue has been identified and we are currently working to restore performance

3. monitoring Nov 04, 2026, 04:42 PM UTC

   We have applied a fix and currently monitoring our systems.

4. monitoring Nov 04, 2026, 04:45 PM UTC

   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.

5. monitoring Nov 04, 2026, 05:11 PM UTC

   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.

6. resolved Nov 04, 2026, 05:50 PM UTC

   The incident has been resolved

Read the full incident report →

Started Oct 06, 2026, 03:19 PM UTC· resolved Oct 06, 2026, 03:53 PM UTC

1. investigating Oct 06, 2026, 03:19 PM UTC

   We are experiencing a backlog with regards to the generation of certain AI outputs, including conversation summary and Smart QA/CSAT reviews. Some of these may take a few minutes longer to appear than normal. We are working on clearing the backlog.

2. investigating Oct 06, 2026, 03:20 PM UTC

   We are continuing to investigate this issue.

3. monitoring Oct 06, 2026, 03:31 PM UTC

   Backlog has reduced. We're continuing to monitor.

4. resolved Oct 06, 2026, 03:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 05, 2026, 07:42 AM UTC· resolved Oct 05, 2026, 09:45 AM UTC

1. investigating Oct 05, 2026, 07:42 AM UTC

   We are investigating a spike in failures for outbound sending on a subset of custom SMTP channels.

2. identified Oct 05, 2026, 08:34 AM UTC

   We believe we have identified the cause and are deploying a fix.

3. monitoring Oct 05, 2026, 09:13 AM UTC

   The fix is deployed and the problem appears to be resolved. We are continuing to monitor.

4. resolved Oct 05, 2026, 09:45 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 27, 2026, 01:49 AM UTC· resolved Sep 27, 2026, 02:04 AM UTC

1. investigating Sep 27, 2026, 01:49 AM UTC

   Our team is currently investigating elevated API error rates that may cause degraded performance or delays. We will provide updates shortly.

2. resolved Sep 27, 2026, 02:04 AM UTC

   The upstream issues causing delays in our system have been resolved.

Read the full incident report →

Started Sep 23, 2026, 10:38 AM UTC· resolved Sep 23, 2026, 03:01 PM UTC

1. investigating Sep 23, 2026, 10:38 AM UTC

   We are experiencing delays in processing Office 365 and Gmail messages. Both sending and receiving are impacted. We are investigating.

2. investigating Sep 23, 2026, 11:34 AM UTC

   We are continuing to investigate the issue.

3. monitoring Sep 23, 2026, 12:47 PM UTC

   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.

4. resolved Sep 23, 2026, 03:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 08:20 AM UTC· resolved Sep 14, 2026, 11:01 AM UTC

1. investigating Sep 14, 2026, 08:20 AM UTC

   We're observing some Office 365 channels experience delays in sending and receiving messages. We're currently investigating.

2. investigating Sep 14, 2026, 09:00 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 14, 2026, 09:39 AM UTC

   We have established that channel sync error rate is <1%, but remains above our expected baseline rate. We are continuing to investigate.

4. monitoring Sep 14, 2026, 10:13 AM UTC

   We are seeing error rates return to normal. We are continuing to monitor the health of our systems.

5. resolved Sep 14, 2026, 11:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 31, 2026, 03:43 PM UTC· resolved Aug 31, 2026, 04:51 PM UTC

1. monitoring Aug 31, 2026, 03:43 PM UTC

   Beginning at 14:00 UTC (7am PDT), Front application performance degraded as we were unable to add elastic infrastructure to support growing traffic on Monday morning. The root issue has been resolved, and infrastructure is now catching up to meet demand. We are monitoring the recovery, and will continue to provide updates.

2. resolved Aug 31, 2026, 04:51 PM UTC

   This incident has been resolved, and all activities have caught up to realtime. Front will continue to monitor application performance.

Read the full incident report →

Started Aug 15, 2026, 08:11 PM UTC· resolved Aug 15, 2026, 08:44 PM UTC

1. investigating Aug 15, 2026, 08:11 PM UTC

   We are currently investigating this issue.

2. investigating Aug 15, 2026, 08:12 PM UTC

   Some customers (cell 14) may see missing resource change events in their audit log due to a system error in that service. No customer message data is affected, only the audit log.

3. resolved Aug 15, 2026, 08:44 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 28, 2026, 06:24 PM UTC· resolved Jun 01, 2026, 11:35 PM UTC

1. investigating May 28, 2026, 06:24 PM UTC

   We are currently investing an issue where a subset of customers are seeing offline O365 channels.

2. identified May 28, 2026, 06:57 PM UTC

   We are attempting a mitigation step to get impacted channels back online.

3. identified May 28, 2026, 07:35 PM UTC

   Front continues to investigate paths to restore access for affected Office365 channels. Office reports internal errors, which we are trying to work around.

4. identified May 28, 2026, 11:36 PM UTC

   Front is partnering with Microsoft to investigate the channel sync failures and will continue to update here as we make progress. Manually re-authorizing the channel in Front's channel settings has worked in some cases, but not all. Please contact [email protected] for assistance.

5. identified May 29, 2026, 02:05 AM UTC

   Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 8 hours. Manually re-authorizing the channel in Front's channel settings has worked in some cases, but not all. Please contact [email protected] for assistance.

6. identified May 29, 2026, 10:42 AM UTC

   Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 6 hours. Manually re-authorizing the channel in Front's channel settings has worked in some cases, but not all. Please contact [email protected] for assistance.

7. identified May 29, 2026, 06:38 PM UTC

   Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 6 hours. Manually re-authorizing the channel in Front's channel settings has worked in some cases, but not all. Please contact [email protected] for assistance.

8. identified May 29, 2026, 11:40 PM UTC

   Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 6 hours. Manually re-authorizing the channel in Front's channel settings has worked in some cases, but not all. Please contact [email protected] for assistance.

9. identified May 30, 2026, 03:37 AM UTC

   Front is continuing to partner with Microsoft to investigate the decreasing volume of channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in most cases, but not all. Please contact [email protected] for assistance.

10. identified May 30, 2026, 04:04 PM UTC

    Front is continuing to partner with Microsoft to investigate the decreasing volume of channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in most cases, but not all. Please contact [email protected] for assistance.

11. identified May 31, 2026, 03:17 AM UTC

    Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in most cases, but not all. Please contact [email protected] for assistance.

12. identified May 31, 2026, 03:22 PM UTC

    Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in most cases, but not all. Please contact [email protected] for assistance.

13. identified Jun 01, 2026, 02:57 AM UTC

    Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in majority of cases, but not all. Please contact [email protected] for assistance.

14. identified Jun 01, 2026, 03:30 PM UTC

    Front is continuing to partner with Microsoft to investigate the channel sync failures. The next update will be within the next 12 hours. Manually re-authorizing the channel in Front's channel settings has worked in majority of cases, but not all. Please contact [email protected] for assistance.

15. resolved Jun 01, 2026, 11:35 PM UTC

    Front is continuing to partner with Microsoft on root cause of remaining channel sync failures. We added the ability to automatically bring these channels back online to prevent further customer impact.

Read the full incident report →

Started Apr 25, 2026, 06:37 PM UTC· resolved Apr 25, 2026, 07:09 PM UTC

1. investigating Apr 25, 2026, 06:37 PM UTC

   Counters (numbers in the navigation bar of the app) are updating with a delay for some customers [us-west-1]

2. resolved Apr 25, 2026, 07:09 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 14, 2026, 05:03 PM UTC· resolved Apr 14, 2026, 08:00 PM UTC

1. monitoring Apr 14, 2026, 05:03 PM UTC

   There was a delay in message delivery of up to an hour. Messages are now being delivered without delay. We are continuing to monitor

2. resolved Apr 14, 2026, 08:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 23, 2026, 03:17 PM UTC· resolved Feb 23, 2026, 06:10 PM UTC

1. investigating Feb 23, 2026, 03:17 PM UTC

   Some customers are experiencing delays in inbound messages being received from Gmail and Office channels (typically 2-4 minutes of delay). We are currently scaling up our systems to address this.

2. investigating Feb 23, 2026, 03:51 PM UTC

   Delays have been reduced, but remain slightly elevated. We are continuing to investigate.

3. investigating Feb 23, 2026, 04:36 PM UTC

   Office delays have been resolved. Gmail delays have reduced further (to approximately 1 minute).

4. monitoring Feb 23, 2026, 04:48 PM UTC

   Delays are resolved for both Gmail and Outlook channels. We're continuing to monitor to ensure we're at a stable steady-state.

5. resolved Feb 23, 2026, 06:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 18, 2026, 02:59 PM UTC· resolved Feb 18, 2026, 05:08 PM UTC

1. investigating Feb 18, 2026, 02:59 PM UTC

   We are currently investigating this issue.

2. identified Feb 18, 2026, 03:14 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified Feb 18, 2026, 04:01 PM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Feb 18, 2026, 04:50 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Feb 18, 2026, 05:08 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 07, 2026, 12:03 AM UTC· resolved Feb 07, 2026, 12:26 AM UTC

1. investigating Feb 07, 2026, 12:03 AM UTC

   We are currently investigating an issue that is causing delayed message import. Impacting all channels all regions

2. resolved Feb 07, 2026, 12:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 23, 2026, 09:51 PM UTC· resolved Jan 24, 2026, 01:40 AM UTC

1. identified Jan 23, 2026, 09:51 PM UTC

   Front is currently inaccessible. We have identified the cause and are working on a resolution.

2. identified Jan 23, 2026, 09:53 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Jan 23, 2026, 10:28 PM UTC

   Application and API access have been restored and we are continuing to monitor the system.

4. resolved Jan 24, 2026, 01:40 AM UTC

   This incident has been resolved. A fix has been implemented.

Read the full incident report →

Started Jan 22, 2026, 08:49 PM UTC· resolved Jan 23, 2026, 05:36 AM UTC

1. identified Jan 22, 2026, 08:49 PM UTC

   Microsoft Office365 is experiencing an outage affecting some Front channels: "Users may be seeing degraded service functionality or be unable to access multiple Microsoft 365 services." Front is unable to send or receive messages for affected customers. Their status page is available at https://status.cloud.microsoft/.

2. monitoring Jan 23, 2026, 03:28 AM UTC

   Microsoft appears to have recovered, and we're no longer seeing any impact on Office 365 channels. All pending messages have been delivered. We're continuing to monitor the situation closely.

3. resolved Jan 23, 2026, 05:36 AM UTC

   Microsoft is still reporting service degradation, but it's not impacting Front. We'll continue monitoring the situation in case it changes.

Read the full incident report →

Started Dec 19, 2025, 03:13 PM UTC· resolved Dec 19, 2025, 09:23 PM UTC

1. investigating Dec 19, 2025, 03:13 PM UTC

   We are currently investigating the issue. [us-west-1], [us-west-2]

2. investigating Dec 19, 2025, 04:06 PM UTC

   We are continuing to investigate this issue.

3. identified Dec 19, 2025, 04:47 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Dec 19, 2025, 05:29 PM UTC

   A fix has been implemented and we are monitoring the results. We are seeing recovery but continuing to close out remaining recovery items.

5. monitoring Dec 19, 2025, 05:57 PM UTC

   We are continuing to monitor and close our our remaining recovery items for [us-west-2] customers. Other regions are recovered.

6. monitoring Dec 19, 2025, 06:23 PM UTC

   Front is operational for all customers. We are continuing to backfill any missed messages and application webhooks.

7. resolved Dec 19, 2025, 09:23 PM UTC

   All backfills complete

8. postmortem Dec 19, 2025, 11:21 PM UTC

   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.

Read the full incident report →

Started Dec 10, 2025, 01:06 AM UTC· resolved Dec 10, 2025, 04:00 PM UTC

1. investigating Dec 10, 2025, 01:06 AM UTC

   We are currently investigating an issue that is causing errors loading conversations. We believe it is limited in scope to a subset of customers who use our slack integration

2. identified Dec 10, 2025, 01:11 AM UTC

   We believe we have identified the issue, currently working on implementing a fix

3. identified Dec 10, 2025, 01:23 AM UTC

   We are rolling out the fix now

4. monitoring Dec 10, 2025, 01:53 AM UTC

   We've rolled out a fix to the issue, all conversations should now load. Please reach out to support if you continue to experience any issues

5. resolved Dec 10, 2025, 04:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 01, 2025, 10:18 PM UTC· resolved Dec 01, 2025, 10:26 PM UTC

1. identified Dec 01, 2025, 10:18 PM UTC

   We have identified an issue where delegated inboxes are not appearing in the navigation panel. We are working on a fix for this issue and will provide another update once there is an ETA for the resolution.

2. identified Dec 01, 2025, 10:25 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Dec 01, 2025, 10:26 PM UTC

   We have restored delegated inboxes. If delegated inboxes are not currently visible, please restart the application.

Read the full incident report →

Started Nov 21, 2025, 07:21 PM UTC· resolved Nov 21, 2025, 10:18 PM UTC

1. investigating Nov 21, 2025, 07:21 PM UTC

   We are currently investigating an outage.

2. monitoring Nov 21, 2025, 07:48 PM UTC

   A rollback has started recovering the failures in us-west-1. We are monitoring and further investigating root cause

3. monitoring Nov 21, 2025, 07:57 PM UTC

   Recovering messages for all regions but restoring back to operational state. Continuing to monitor

4. monitoring Nov 21, 2025, 08:15 PM UTC

   Fully recovered for us-west-1 and eu-west-1 regions. Continued recovery for us-west-2 customers

5. monitoring Nov 21, 2025, 08:18 PM UTC

   Us-West-2 customers are now recovered. We are continuing to monitor

6. monitoring Nov 21, 2025, 08:40 PM UTC

   Investigating continued outages for [by_company_00017] customers only.

7. monitoring Nov 21, 2025, 09:15 PM UTC

   Continuing investigation for [by_company_00017] customers only.

8. monitoring Nov 21, 2025, 09:45 PM UTC

   Recovering app for [by_company_00017] customers, delay for rules and calendar remains.

9. resolved Nov 21, 2025, 10:18 PM UTC

   This incident has been resolved.

10. postmortem Nov 21, 2025, 11:59 PM UTC

    At 19:05 UTC \(11:05 am PST\), Front began a routine application deployment. Front typically deploys new versions of the application multiple times per day as part of normal operation. This app release included a change in the way we connect to an internal caching system. The change passed all our testing requirements, but due to an environment-specific configuration on the caching system it immediately caused a problem in our customer environment. ‌ Front was alerted within minutes of the increased error rate and immediately started investigating. At 19:20 UTC we initiated a rollback of the deployment across all regions. Because of the progressive nature of the rollback, some customers saw the application recover quickly after while for others it took up to 30 minutes. By 19:50 all rollbacks were complete and most customers were back to normal. ‌ However, for one slice of Front customers the rollback triggered a second issue that kept the application from recovering. For clarity, Front divides customers into one of 40 “cells” that isolate them from one another. This architecture is designed to limit the scope of certain failures, like this one. But for the 2% of customers on the affected cell we had to take additional steps to recover. ‌ This second issue was triggered by a spike in database load caused by the stampede of traffic from customers returning to the application. In this cell a particular workload caused high database contention that ultimately timed out and then started over, which prevented us from escaping the problem. Traffic continued to back up and we were unable to progress through all the messages. ‌ Once we identified that the problematic workload was in the evaluation of rules, we were able to block all rules from processing. This allowed the database and the application to immediately recover, coming back online for users at 21:39 UTC. Rule evaluations continued to back up, and we were able to slowly restart processing to make sure the database didn’t reenter a bad state. All rule evaluations were caught up by 22:20 UTC. ‌ We would like to apologize for the disruption this outage has caused and for the unusually long duration. In the immediate aftermath of the incident we have identified a number of actions we can take to prevent this kind of event from occurring again. ‌ The first step is to ensure we have a test environment that appropriately represents the configuration of the production customer environment for the caching system. This issue should have been detected before we ever deployed it. The second task is to investigate the rollback system to see if we can safely improve the speed, so that if we have a similar issue in the future we can recover even faster.

Read the full incident report →

Started Oct 09, 2025, 09:29 PM UTC· resolved Oct 11, 2025, 12:20 AM UTC

1. investigating Oct 09, 2025, 09:29 PM UTC

   Some Canadian IP addresses are experiencing app slowness and/or degraded email message performance.

2. investigating Oct 09, 2025, 09:36 PM UTC

   We are continuing to investigate this issue.

3. investigating Oct 09, 2025, 10:14 PM UTC

   We are continuing to investigate this issue.

4. investigating Oct 09, 2025, 11:19 PM UTC

   We are still investigating the issue and searching for the root cause.

5. investigating Oct 10, 2025, 02:15 AM UTC

   We are continuing to investigate this issue, and are yet to identify a root cause Some impacted users have been able to workaround the issue by using a VPN to re-route their traffic, or by tethering to a mobile device. We will update this page as soon as we have more information

6. monitoring Oct 10, 2025, 05:39 PM UTC

   We've received reports this morning that users are no longer encountering issues. We are continuing to monitor, please reach out to support if you are experiencing degraded performance

7. resolved Oct 11, 2025, 12:20 AM UTC

   We've had no further reports of issues. Please reach out to Front support if you experience degradation in the app

Read the full incident report →

Started Sep 26, 2025, 04:47 PM UTC· resolved Sep 26, 2025, 04:56 PM UTC

1. investigating Sep 26, 2025, 04:47 PM UTC

   App is not loading in specific regions and timeouts have been spiking for some API calls

2. resolved Sep 26, 2025, 04:56 PM UTC

   A cache node was lost and automatically recovered in 6 minutes. All systems should now be operational.

Read the full incident report →

Started Sep 19, 2025, 06:40 PM UTC· resolved Sep 23, 2025, 09:48 AM UTC

1. investigating Sep 19, 2025, 06:40 PM UTC

   We've have received reports of the google sign in flow failing to redirect back to the mobile app successfully, and have been able to reproduce the issue We are currently investigating the problem

2. investigating Sep 19, 2025, 08:08 PM UTC

   We have isolated the issue to iOS devices, Android customers should be unaffected Continuing to investigate

3. identified Sep 19, 2025, 10:51 PM UTC

   We've identified the issue, and are still working on a fix. In the meantime we have identified a workaround that appears to be working on some clients - by navigating directly to https://app.frontapp.com/oauth/google-signin?client_type=universalLink in Safari on iOS and signing you should get redirected to the app in a signed in state

4. identified Sep 23, 2025, 02:13 AM UTC

   We've released a new version of the app (5.69.1) that fixes the behavior in some cases, but does not fully address the issue. We are in progress on a full fix. For clients still unable to login we have identified a workaround that appears to be working on some clients - by navigating directly to https://app.frontapp.com/oauth/google-signin?client_type=universalLink in Safari on iOS and signing you should get redirected to the app in a signed in state

5. monitoring Sep 23, 2025, 06:11 AM UTC

   We've implemented a fix - you can download the latest version from the app store (5.69.2) to test. Please let us know if you experience any issues on this version

6. resolved Sep 23, 2025, 09:48 AM UTC

   We have confirmed reports that the latest version of the iOS app (5.69.2) addresses the issue. If you run into login issues, ensure you've updated to the latest version, and reach out if the problem persists.

Read the full incident report →

Started Sep 16, 2025, 10:02 PM UTC· resolved Sep 16, 2025, 11:23 PM UTC

1. investigating Sep 16, 2025, 10:02 PM UTC

   Front is currently investigating an issue in which trying to load some conversations results in an error message.

2. identified Sep 16, 2025, 10:26 PM UTC

   Conversations that leveraged Suggest Reply between 21:30 and 21:50 UTC (2:30pm – 2:50pm PDT) may cause an error when loading. Front has identified the root cause and is deploying a fix that will allow these messages to display.

3. monitoring Sep 16, 2025, 10:52 PM UTC

   A fix for the affected conversations has now been deployed, and initial tests show all conversations should now be visible. Please make sure to refresh your browser or app if you don't see this right away.

4. resolved Sep 16, 2025, 11:23 PM UTC

   Front has now completed the fix and cleanup associated with this incident. If you continue to see errors loading conversations, please make sure you've done a browser or app refresh, and if the issue persists please contact support. Summary: Conversations for which Front attempted to provide a Suggested Reply between 21:30 – 21:50 UTC may have been unreadable until the fix was completed at 22:49 UTC. During that initial time, suggested replies were generated with an additional field that caused an unrecoverable error in the frontend. No data or messages were lost or corrupted during the incident. Suggested replies for conversations that arrived during that time may need to be regenerated.

Read the full incident report →

Started Sep 12, 2025, 10:32 PM UTC· resolved Sep 13, 2025, 12:00 AM UTC

1. identified Sep 12, 2025, 10:32 PM UTC

   We have an ongoing issue causing delays importing new messages from all gmail channels. We have identified the issue and are currently working on a fix

2. monitoring Sep 12, 2025, 10:44 PM UTC

   Fixes are currently rolling out, we are monitoring backlog of unimported messages

3. monitoring Sep 12, 2025, 11:31 PM UTC

   Continuing to monitor our backlog of messages, the majority of channels have recovered - but still have a small segment still catching up

4. resolved Sep 13, 2025, 12:00 AM UTC

   All channels should now be recovered

Read the full incident report →