Front

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 15:19 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 2026-10-06 15:20 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-10-06 15:31 UTC

   Backlog has reduced. We're continuing to monitor.

4. resolved 2026-10-06 15:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: SMTP (non-Gmail / O365)

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-05 07:42 UTC

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

2. identified 2026-10-05 08:34 UTC

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

3. monitoring 2026-10-05 09:13 UTC

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

4. resolved 2026-10-05 09:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail, O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-27 01:49 UTC

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

2. resolved 2026-09-27 02:04 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail, O365

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 10:38 UTC

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

2. investigating 2026-09-23 11:34 UTC

   We are continuing to investigate the issue.

3. monitoring 2026-09-23 12:47 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 2026-09-23 15:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-14 08:20 UTC

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

2. investigating 2026-09-14 09:00 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-14 09:39 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 2026-09-14 10:13 UTC

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

5. resolved 2026-09-14 11:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-08-31 15:43 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...

2. resolved 2026-08-31 16:51 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-15 20:11 UTC

   We are currently investigating this issue.

2. investigating 2026-08-15 20:12 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 2026-08-15 20:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-28 18:24 UTC

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

2. identified 2026-05-28 18:57 UTC

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

3. identified 2026-05-28 19:35 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 2026-05-28 23:36 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 support@front.com for...

5. identified 2026-05-29 02:05 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 support@front.com for...

6. identified 2026-05-29 10:42 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 support@front.com for...

7. identified 2026-05-29 18:38 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 support@front.com for...

8. identified 2026-05-29 23:40 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 support@front.com for...

9. identified 2026-05-30 03:37 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...

10. identified 2026-05-30 16:04 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...

11. identified 2026-05-31 03:17 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 support@front.com for...

12. identified 2026-05-31 15:22 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 support@front.com for...

13. identified 2026-06-01 02:57 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...

14. identified 2026-06-01 15:30 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...

15. resolved 2026-06-01 23:35 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.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-25 18:37 UTC

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

2. resolved 2026-04-25 19:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Other channels

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-14 17:03 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 2026-04-14 20:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail, O365

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-23 15:17 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 2026-02-23 15:51 UTC

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

3. investigating 2026-02-23 16:36 UTC

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

4. monitoring 2026-02-23 16:48 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 2026-02-23 18:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-18 14:59 UTC

   We are currently investigating this issue.

2. identified 2026-02-18 15:14 UTC

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

3. identified 2026-02-18 16:01 UTC

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

4. monitoring 2026-02-18 16:50 UTC

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

5. resolved 2026-02-18 17:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: SMTP (non-Gmail / O365), Gmail, O365, Facebook, Twitter, Twilio, Other channels

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-07 00:03 UTC

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

2. resolved 2026-02-07 00:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, API and integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-01-23 21:51 UTC

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

2. identified 2026-01-23 21:53 UTC

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

3. monitoring 2026-01-23 22:28 UTC

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

4. resolved 2026-01-24 01:40 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-01-22 20:49 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...

2. monitoring 2026-01-23 03:28 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 2026-01-23 05:36 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-19 15:13 UTC

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

2. investigating 2025-12-19 16:06 UTC

   We are continuing to investigate this issue.

3. identified 2025-12-19 16:47 UTC

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

4. monitoring 2025-12-19 17:29 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 2025-12-19 17:57 UTC

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

6. monitoring 2025-12-19 18:23 UTC

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

7. resolved 2025-12-19 21:23 UTC

   All backfills complete

8. postmortem 2025-12-19 23:21 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...

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-10 01:06 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 2025-12-10 01:11 UTC

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

3. identified 2025-12-10 01:23 UTC

   We are rolling out the fix now

4. monitoring 2025-12-10 01:53 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 2025-12-10 16:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-01 22:18 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 2025-12-01 22:25 UTC

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

3. resolved 2025-12-01 22:26 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, Rules and Workflows, Calendar

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-21 19:21 UTC

   We are currently investigating an outage.

2. monitoring 2025-11-21 19:48 UTC

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

3. monitoring 2025-11-21 19:57 UTC

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

4. monitoring 2025-11-21 20:15 UTC

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

5. monitoring 2025-11-21 20:18 UTC

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

6. monitoring 2025-11-21 20:40 UTC

   Investigating continued outages for [by_company_00017] customers only.

7. monitoring 2025-11-21 21:15 UTC

   Continuing investigation for [by_company_00017] customers only.

8. monitoring 2025-11-21 21:45 UTC

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

9. resolved 2025-11-21 22:18 UTC

   This incident has been resolved.

10. postmortem 2025-11-21 23:59 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...

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, SMTP (non-Gmail / O365), Gmail, O365

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-09 21:29 UTC

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

2. investigating 2025-10-09 21:36 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-09 22:14 UTC

   We are continuing to investigate this issue.

4. investigating 2025-10-09 23:19 UTC

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

5. investigating 2025-10-10 02:15 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 2025-10-10 17:39 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 2025-10-11 00:20 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, API and integrations

Failure mode: CDN or edge layer failed or served bad content. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-26 16:47 UTC

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

2. resolved 2025-09-26 16:56 UTC

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

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-19 18:40 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 2025-09-19 20:08 UTC

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

3. identified 2025-09-19 22:51 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...

4. identified 2025-09-23 02:13 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...

5. monitoring 2025-09-23 06:11 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 2025-09-23 09:48 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.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-16 22:02 UTC

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

2. identified 2025-09-16 22:26 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 2025-09-16 22:52 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 2025-09-16 23:23 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...

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-12 22:32 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 2025-09-12 22:44 UTC

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

3. monitoring 2025-09-12 23:31 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 2025-09-13 00:00 UTC

   All channels should now be recovered

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-05 13:41 UTC

   We are investigating reports of Google SSO and Office SSO login issues on our mobile apps (iOS and Android).

2. investigating 2025-09-05 14:41 UTC

   We are continuing to investigate this issue.

3. identified 2025-09-05 16:41 UTC

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

4. resolved 2025-09-05 17:09 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, API and integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-01 14:05 UTC

   We are currently investigating reports of increased latency affecting a subset of customers in the EU region. Impact: Some customers in EU may experience slower response times or intermittent delays when using our app. Not all customers in this region are affected.

2. investigating 2025-09-01 14:05 UTC

   We are continuing to investigate this issue.

3. identified 2025-09-01 14:53 UTC

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

4. monitoring 2025-09-01 15:02 UTC

   Response times are stabilizing, though we continue to actively monitor the situation to ensure the issue is fully resolved.

5. resolved 2025-09-01 17:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-29 23:41 UTC

   We are experiencing some delays in O365 channels and are actively investigating this issue.

2. monitoring 2025-07-29 23:52 UTC

   An offending change was identified and reverted. We are monitoring the impact now

3. resolved 2025-07-30 00:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-15 16:28 UTC

   Some customers might experience issues loading the app. We are currently investigating the root cause.

2. monitoring 2025-07-15 17:07 UTC

   We've identified the root cause and recovered. We're monitoring to ensure a full resolution.

3. resolved 2025-07-15 18:00 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-07-15 15:11 UTC

   Some customers might experience issues loading the app

2. identified 2025-07-15 15:31 UTC

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

3. monitoring 2025-07-15 15:42 UTC

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

4. resolved 2025-07-15 15:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-24 15:36 UTC

   We are currently investigating reports of increased loading times affecting a subset of our customers. Some users may experience slower than normal response times when accessing the app or navigating between pages.

2. monitoring 2025-06-24 16:40 UTC

   We have implemented initial mitigation measures and are seeing improvements in app loading times. Performance is gradually returning to normal levels. We are continuing to monitor the situation closely.

3. resolved 2025-06-24 18:38 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Failure mode: CDN or edge layer failed or served bad content. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2025-06-09 21:00 UTC

   A configuration change was made to the Content Distribution Network that caused the web clients to lose access to files that were needed for startup. The web app couldn't be loaded between 1:48 PM and 2:16 PM PDT. Impact was limited to users who tried to start the app between...

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Analytics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-06-05 06:45 UTC

   We are currently processing a backlog of analytics data. This may cause delays in data availability and temporarily skewed metrics. Our team is actively working to resolve the issue.

2. resolved 2025-06-05 07:39 UTC

   The backlog of analytics data has been fully processed, and metrics are now up to date.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App, API and integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-03 15:55 UTC

   We are currently investigating an issue where some users may be experiencing difficulties with the app not loading and some API calls timing out or returning errors. We are working to identify the cause and will provide an update shortly.

2. monitoring 2025-06-03 16:20 UTC

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

3. resolved 2025-06-03 16:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-04-29 23:34 UTC

   Front is investigating a major database outage affecting one shard of customers. [us-west-1] [by_company_00005]

2. identified 2025-04-29 23:54 UTC

   At 4:16 pm PDT (23:16 UTC), during a routine maintenance operation on one of Front’s customer databases, the database was inadvertently disabled and made unrecoverable. Front immediately began the restoration procedure from our up-to-date backup, but as it has to copy the entire...

3. identified 2025-04-30 01:41 UTC

   The restoration process is still underway, but nearing completion. We are targeting less than 60 minutes to restore limited application functionality. [us-west-1] [by_company_00005]

4. identified 2025-04-30 03:13 UTC

   The database recovery has completed and application functionality is now restored. Messages from the last few hours since the incident started are now being re-synced. This will take some time to catch up, but we anticipate no data loss as a result of this issue. [us-west-1]...

5. monitoring 2025-04-30 04:09 UTC

   As of 8:11 pm PDT (03:11 Wednesday UTC), the application is functioning for all customers. Front began applying all changes since the incident started, like syncing messages from email channels, which are now caught up. Customers may experience delays for a few more minutes as...

6. resolved 2025-04-30 05:43 UTC

   This incident has been resolved.

7. postmortem 2025-04-30 23:00 UTC

   On Tuesday, April 29, Front experienced an application outage lasting roughly 4 hours for a subset of US-based customers—roughly 3% of users. This was the result of a human error during a planned database maintenance operation that resulted in one database shard becoming...

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-25 10:28 UTC

   We are currently investigating delays for inbound messages on some Office365 channels.

2. investigating 2025-04-25 11:42 UTC

   We are continuing to investigate this issue.

3. resolved 2025-04-25 15:19 UTC

   Issue is not resolved, opening a partner incident instead: https://front-partners.statuspage.io/incidents/sdln9wvbqdb7 Please contact Microsoft for assistance with an affected mailbox.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-04-17 13:15 UTC

   We received reports from a small number of customers that some drafts error when sending, with the message: "Unexpected problem sending attachment larger than 3MB to Office 365."

2. investigating 2025-04-17 18:47 UTC

   Office 365 servers may sometimes fail to accept attachments larger than 3 MB. As a temporary alternative, we suggest using another method of sharing files with recipients, such as OneDrive. We have communicated the issue to Microsoft and are investigating additional mitigations.

3. resolved 2025-04-22 21:56 UTC

   There has been a significant reduction in the number of failures for Office 365 requests with attachments larger than 3 MB. We will continue to monitor.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-19 17:24 UTC

   We are currently investigating the issue

2. monitoring 2025-03-19 17:42 UTC

   A fix has been implemented and we are monitoring performance for customers.

3. resolved 2025-03-19 17:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-14 21:49 UTC

   We are currently investigating errors sending and receiving email for Office365 channels

2. identified 2025-03-14 21:51 UTC

   We have identified the issue causing errors when sending and receiving mail for Office365 channels and are working towards a resolution.

3. identified 2025-03-14 21:59 UTC

   We are currently deploying a fix for this issue and expect to restore service within 30 minutes

4. monitoring 2025-03-14 22:17 UTC

   We have deployed a fix and are monitoring the situation.

5. resolved 2025-03-15 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-03-01 21:14 UTC

   Our monitoring is suggesting there are elevated error rates for Office 365 channels. We are currently investigating.

2. identified 2025-03-01 21:23 UTC

   Office365 is currently experiencing an outage preventing users to login. This is also preventing us from sending and importing messages.

3. monitoring 2025-03-01 21:45 UTC

   Office seem to have resolved the issue. We're working through a backlog of imports.

4. resolved 2025-03-01 22:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-02-12 21:00 UTC

   We're currently processing a backlog of Gmail messages. Messages received after 8:25pm UTC are not impacted.

2. resolved 2025-02-12 21:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Front chat

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-12-26 21:30 UTC

   We're investigating some errors only affecting our AI answers functionality with Chat

2. identified 2024-12-26 21:48 UTC

   AI Answers functionality in Chat is degraded due to an outage with an upstream provider. We are working on a mitigation. In the meantime, AI Answers chatbot nodes will follow the "AI doesn't resolve the inquiry" branch.

3. monitoring 2024-12-26 23:18 UTC

   We are seeing AI Answers in Chat back to being fully operational. We will continue monitoring.

4. monitoring 2024-12-26 23:19 UTC

   We are seeing AI Answers in Chat back to being fully operational. We will continue monitoring.

5. resolved 2024-12-27 00:01 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-12-18 19:33 UTC

   We are currently investigating this issue.

2. investigating 2024-12-18 19:38 UTC

   We have identified the issue and are working with our provider to remediate.

3. monitoring 2024-12-18 20:06 UTC

   We've worked with our provider and remediated the issue. We'll continue to monitor.

4. resolved 2024-12-18 20:41 UTC

   This incident has been relsolved.

Excerpts are shortened. Read the full incident on Front's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-12-11 23:30 UTC

   This caused numerous Front AI features to be unavailable, including AI Answers, AI Tagging (beta), Suggested Replies(beta), AI Compose, and AI Translate (beta). Additionally, the AI Tagging failures blocked subsequent rules from being run.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-11-25 08:41 UTC

   Our partner Microsoft is experiencing a service degradation affecting Exchange Online mailboxes. You can follow Microsoft Issue ID MO941162 for more details. This may cause outbound/inbound delays for customers using Office 365, as Front cannot connect to Microsoft servers.

2. identified 2024-11-25 10:49 UTC

   Microsoft is still investigating the issue; here is their latest update. > We’re continuing to investigate recent changes, service telemetry and the failure paths to determine the root cause of impact. Source:...

3. identified 2024-11-25 15:47 UTC

   Microsoft is deploying a fix > At 15:27 CET > We’re monitoring the progress of the fix, which has been deployed to approximately 60% of the affected environments. We’re continuing our manual restarts on the remaining impacted machines. We are closely monitoring our systems for...

4. monitoring 2024-11-25 20:26 UTC

   Microsoft deployed a fix. Our systems are recovering. Latest update from Microsoft: > At 20:52 CET > We're continuing to redirect traffic and apply targeted remediation to impacted servers. > We've observed initially positive results in some areas, and we're monitoring service...

5. monitoring 2024-11-26 00:07 UTC

   Our systems have fully recovered. We are now retrying failed tasks.

6. resolved 2024-11-26 02:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: API and integrations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-11-18 20:03 UTC

   We are seeing an increase in 5xx errors on our public API in us-west-2 region, which may also affect the ability to send/receive messages on some channels.

2. monitoring 2024-11-18 20:44 UTC

   The increased rate of errors has subsided as of approximately 10 minutes ago, but we are still determining the root cause.

3. resolved 2024-11-18 22:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-29 12:34 UTC

   We are receiving reports of elevated loading times for some customers in the us-west-1 region. We're currently investigating the root cause.

2. monitoring 2024-10-29 12:47 UTC

   We have put in place mitigations and are seeing a return to normal performance. We're continuing to monitor.

3. resolved 2024-10-29 13:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: SMTP (non-Gmail / O365), Gmail, O365

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-27 20:25 UTC

   We are currently investigating this issue.

2. investigating 2024-09-27 20:25 UTC

   We are continuing to investigate this issue.

3. identified 2024-09-27 20:38 UTC

   We have identified the cause of the issue and are working on a fix. The issue affects some but not all channels.

4. identified 2024-09-27 21:02 UTC

   We are validating the fix in our staging environment.

5. identified 2024-09-27 21:27 UTC

   We have validated the fix and are in the process of doing a manual deploy to circumvent the current Docker outage.

6. monitoring 2024-09-27 21:47 UTC

   The fix has been deployed and we are seeing email delivery services have recovered. We're monitoring and catching up on backlog so there might be residual delays.

7. monitoring 2024-09-28 02:21 UTC

   Customers in us-west-2 and eu-west-1 regions have fully recovered. We are still working through the incoming message backlog on us-west-1.

8. resolved 2024-09-28 02:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-23 11:00 UTC

   We're receiving some reports of customers having difficulties accessing Front, or delays in sending and receiving messages, in our eu-west-1 region. We're currently investigating.

2. identified 2024-09-23 11:07 UTC

   We believe we've identified the problem which caused a temporary spike in API errors. We're seeing a return to normal levels, and are working on a root-cause fix.

3. resolved 2024-09-23 11:30 UTC

   Application performance has appeared to return to normal for eu-west-1 users.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: Gmail

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-13 15:38 UTC

   We're observing problems sending and receiving some messages on Gmail channels in the us-west-2 region. We're working on identifying the root cause.

2. investigating 2024-09-13 15:52 UTC

   We are continuing to investigate this issue, which seems to be related to Gmail's rate limiting mechanisms. We're seeing some impact across multiple regions.

3. investigating 2024-09-13 16:35 UTC

   We are continuing to see message delays, and are rescaling our internal queues globally to help mitigate the issue.

4. investigating 2024-09-13 16:57 UTC

   We are beginning to see a gradual increase in successful deliveries. We are continuing to monitor the situation, as well as replaying deliveries that have been delayed by the original incident.

5. identified 2024-09-13 17:22 UTC

   We are on the recovery path now and are focused on draining the backlog of delayed messages.

6. monitoring 2024-09-13 17:44 UTC

   We are continuing to drain the backlog and will be doing so for the next couple hours.

7. monitoring 2024-09-13 18:38 UTC

   Continuing to drain the backlog

8. monitoring 2024-09-13 19:19 UTC

   Some channels are still experiencing delays as we import the backlog of messages received while Gmail was experiencing an outage

9. resolved 2024-09-13 19:25 UTC

   All channels should be back to normal now.

Excerpts are shortened. Read the full incident on Front's status page.

Affected: App

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-08-29 09:43 UTC

   We are experiencing issues launching new deployments in our us-west-2 region, which may degrade the app performance and lead to delays in receiving messages for some customers.

2. monitoring 2024-08-29 09:51 UTC

   We're beginning to see new deployments coming online. We're continuing to monitor the health of the cluster.

3. resolved 2024-08-29 10:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Front's status page.