Front Outage History
Front is up right nowPingoru has recorded 50 incidents for Front: 19 in the last 12 months and 7 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 4 of 720 (0%) |
| May 2026 | 1 | 78 of 744 (10%) |
| June 2026 | 0 | 24 of 720 (3%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 2 | 2 of 744 (0%) |
| September 2026 | 3 | 7 of 720 (1%) |
| October 2026 | 2 | 3 of 576 (0%) |
Incidents, newest first
Minor September 1, 2025 API Latency [eu-west-1][by_company_00006] 3h 47m App, API and integrations
Started Sep 01, 2025, 02:05 PM UTC· resolved Sep 01, 2025, 05:52 PM UTC
- investigating Sep 01, 2025, 02:05 PM 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.
- investigating Sep 01, 2025, 02:05 PM UTC
We are continuing to investigate this issue.
- identified Sep 01, 2025, 02:53 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Sep 01, 2025, 03:02 PM UTC
Response times are stabilizing, though we continue to actively monitor the situation to ensure the issue is fully resolved.
- resolved Sep 01, 2025, 05:52 PM UTC
This incident has been resolved.
Minor July 29, 2025 Delays on O365 channels 1h 15m O365
Started Jul 29, 2025, 11:41 PM UTC· resolved Jul 30, 2025, 12:57 AM UTC
- investigating Jul 29, 2025, 11:41 PM UTC
We are experiencing some delays in O365 channels and are actively investigating this issue.
- monitoring Jul 29, 2025, 11:52 PM UTC
An offending change was identified and reverted. We are monitoring the impact now
- resolved Jul 30, 2025, 12:57 AM UTC
This incident has been resolved.
Critical July 15, 2025 Front not loading [us-west-2][by_company_00007] 1h 31m App
Started Jul 15, 2025, 04:28 PM UTC· resolved Jul 15, 2025, 06:00 PM UTC
- investigating Jul 15, 2025, 04:28 PM UTC
Some customers might experience issues loading the app. We are currently investigating the root cause.
- monitoring Jul 15, 2025, 05:07 PM UTC
We've identified the root cause and recovered. We're monitoring to ensure a full resolution.
- resolved Jul 15, 2025, 06:00 PM UTC
This incident has been resolved.
Critical July 15, 2025 Front not loading [us-west-2][by_company_00007][by_company_00001] 41m App
Started Jul 15, 2025, 03:11 PM UTC· resolved Jul 15, 2025, 03:52 PM UTC
- investigating Jul 15, 2025, 03:11 PM UTC
Some customers might experience issues loading the app
- identified Jul 15, 2025, 03:31 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 15, 2025, 03:42 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 15, 2025, 03:52 PM UTC
This incident has been resolved.
Minor June 24, 2025 [us-west-2] [by_company_00007] Customers may experience slowness in app loading 3h 1m App
Started Jun 24, 2025, 03:36 PM UTC· resolved Jun 24, 2025, 06:38 PM UTC
- investigating Jun 24, 2025, 03:36 PM 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.
- monitoring Jun 24, 2025, 04:40 PM 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.
- resolved Jun 24, 2025, 06:38 PM UTC
This incident has been resolved.
Critical June 9, 2025 Web app not loading 28m
Started Jun 09, 2025, 08:48 PM UTC· resolved Jun 09, 2025, 09:16 PM UTC
- resolved Jun 09, 2025, 10:16 PM 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 those times.
Minor June 5, 2025 [us-west-2] [by_company_00008] Delays in analytics data ingestion 54m Analytics
Started Jun 05, 2025, 06:45 AM UTC· resolved Jun 05, 2025, 07:39 AM UTC
- identified Jun 05, 2025, 06:45 AM 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.
- resolved Jun 05, 2025, 07:39 AM UTC
The backlog of analytics data has been fully processed, and metrics are now up to date.
Minor June 3, 2025 App not loading [us-west-2][by_company_00008] 34m App, API and integrations
Started Jun 03, 2025, 03:55 PM UTC· resolved Jun 03, 2025, 04:29 PM UTC
- investigating Jun 03, 2025, 03:55 PM 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.
- monitoring Jun 03, 2025, 04:20 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 03, 2025, 04:29 PM UTC
This incident has been resolved.
Critical April 29, 2025 2025-04-29 Application unavailable for some customers 6h 9m App
Started Apr 29, 2025, 11:34 PM UTC· resolved Apr 30, 2025, 05:43 AM UTC
- investigating Apr 29, 2025, 11:34 PM UTC
Front is investigating a major database outage affecting one shard of customers. [us-west-1] [by_company_00005]
- identified Apr 29, 2025, 11:54 PM 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 database this procedure takes time to complete. We expect this to take roughly two hours, during which time the application will be unavailable for customers on this database. This issue affects a fraction of Front's customers, but for those customers the application will be unavailable until the restoration is complete. [us-west-1] [by_company_00005]
- identified Apr 30, 2025, 01:41 AM 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]
- identified Apr 30, 2025, 03:13 AM 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] [by_company_00005]
- monitoring Apr 30, 2025, 04:09 AM 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 caches clear. Front is now monitoring the application for further issues. All functionality should be restored; please contact support if you continue to see application issues. [us-west-1] [by_company_00005]
- resolved Apr 30, 2025, 05:43 AM UTC
This incident has been resolved.
- postmortem Apr 30, 2025, 11:00 PM 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 unrecoverable. Front was able to restore this database shard from an up-to-date backup and then catch up any missed messages during that period, which resulted in no data lost as a result of this issue. Front customers are divided into database shards so that an issue with one shard does not affect all others. Earlier this week Front performed an upgrade of all database shards as a routine procedure, and while the upgrade was successful with no customer impact, there was an error in the cleanup step that caused one shard to be irrevocably invalidated. This occurred at 4:16 pm PDT \(23:16 UTC\). Front maintains up-to-date database replicas for this purpose, from which we were able to initiate a restoration. This involves copying data, and therefore took nearly four hours to complete. Once the database was restored at 8:07 pm PDT \(03:07 UTC Wednesday\), the application became available again, and Front was able to initiate the next task of applying all changes since the incident began, like syncing in emails from Gmail and O365. Front apologizes to the affected customers for the inconvenience caused by this extended outage. We strive to be always available to customers and have made great investments over the last several years to minimize the possibility and the impact of this kind of error. We can always do more, and are taking the following steps based on lessons from this incident. We have modified our database upgrade procedures and the permissions granted to the operators to significantly reduce the likelihood of this same error. At the same time, we are accelerating our upgrade frequency, which means we’ll have more practice and more automation with this procedure, further reducing risk. More upgrades also means faster adoption of performance and security improvements. Front is also investigating opportunities to improve the recovery time from the backup. Most of the time during this outage was waiting for data to be replicated from one storage region to another, and there may be ways to cut that down. Once again, Front would like to apologize for any disruption caused by this incident and emphasize our commitment to high availability and transparency.
Minor April 25, 2025 [office365] Some customers experiencing delays receiving messages on Office365 channels 4h 50m O365
Started Apr 25, 2025, 10:28 AM UTC· resolved Apr 25, 2025, 03:19 PM UTC
- investigating Apr 25, 2025, 10:28 AM UTC
We are currently investigating delays for inbound messages on some Office365 channels.
- investigating Apr 25, 2025, 11:42 AM UTC
We are continuing to investigate this issue.
- resolved Apr 25, 2025, 03:19 PM 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.
Minor April 17, 2025 [office365] Message Attachment Size Limit Error 5d 8h O365
Started Apr 17, 2025, 01:15 PM UTC· resolved Apr 22, 2025, 09:56 PM UTC
- investigating Apr 17, 2025, 01:15 PM 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."
- investigating Apr 17, 2025, 06:47 PM 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.
- resolved Apr 22, 2025, 09:56 PM 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.
Major March 19, 2025 [us-west-2] [by_company_00008] Customers may experience slowness in app loading 35m App
Started Mar 19, 2025, 05:24 PM UTC· resolved Mar 19, 2025, 05:59 PM UTC
- investigating Mar 19, 2025, 05:24 PM UTC
We are currently investigating the issue
- monitoring Mar 19, 2025, 05:42 PM UTC
A fix has been implemented and we are monitoring performance for customers.
- resolved Mar 19, 2025, 05:59 PM UTC
This incident has been resolved.
Critical March 14, 2025 Errors sending and receiving mail for [Office365] channels 2h 39m O365
Started Mar 14, 2025, 09:49 PM UTC· resolved Mar 15, 2025, 12:28 AM UTC
- investigating Mar 14, 2025, 09:49 PM UTC
We are currently investigating errors sending and receiving email for Office365 channels
- identified Mar 14, 2025, 09:51 PM UTC
We have identified the issue causing errors when sending and receiving mail for Office365 channels and are working towards a resolution.
- identified Mar 14, 2025, 09:59 PM UTC
We are currently deploying a fix for this issue and expect to restore service within 30 minutes
- monitoring Mar 14, 2025, 10:17 PM UTC
We have deployed a fix and are monitoring the situation.
- resolved Mar 15, 2025, 12:28 AM UTC
This incident has been resolved.
Major March 1, 2025 Elevated error rates for [office365] channels 1h 17m O365
Started Mar 01, 2025, 09:14 PM UTC· resolved Mar 01, 2025, 10:32 PM UTC
- investigating Mar 01, 2025, 09:14 PM UTC
Our monitoring is suggesting there are elevated error rates for Office 365 channels. We are currently investigating.
- identified Mar 01, 2025, 09:23 PM UTC
Office365 is currently experiencing an outage preventing users to login. This is also preventing us from sending and importing messages.
- monitoring Mar 01, 2025, 09:45 PM UTC
Office seem to have resolved the issue. We're working through a backlog of imports.
- resolved Mar 01, 2025, 10:32 PM UTC
This incident has been resolved.
Minor February 12, 2025 Delays ingesting emails [gmail] 38m Gmail
Started Feb 12, 2025, 09:00 PM UTC· resolved Feb 12, 2025, 09:39 PM UTC
- identified Feb 12, 2025, 09:00 PM UTC
We're currently processing a backlog of Gmail messages. Messages received after 8:25pm UTC are not impacted.
- resolved Feb 12, 2025, 09:39 PM UTC
This incident has been resolved.
Minor December 26, 2024 AI answers for Chat errors 2h 31m Front chat
Started Dec 26, 2024, 09:30 PM UTC· resolved Dec 27, 2024, 12:01 AM UTC
- investigating Dec 26, 2024, 09:30 PM UTC
We're investigating some errors only affecting our AI answers functionality with Chat
- identified Dec 26, 2024, 09:48 PM 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.
- monitoring Dec 26, 2024, 11:18 PM UTC
We are seeing AI Answers in Chat back to being fully operational. We will continue monitoring.
- monitoring Dec 26, 2024, 11:19 PM UTC
We are seeing AI Answers in Chat back to being fully operational. We will continue monitoring.
- resolved Dec 27, 2024, 12:01 AM UTC
This incident has been resolved.
Major December 18, 2024 Automated emails from Front are delayed - notifications, invites to your teammates, calendar events, etc. 1h 8m App
Started Dec 18, 2024, 07:33 PM UTC· resolved Dec 18, 2024, 08:41 PM UTC
- investigating Dec 18, 2024, 07:33 PM UTC
We are currently investigating this issue.
- investigating Dec 18, 2024, 07:38 PM UTC
We have identified the issue and are working with our provider to remediate.
- monitoring Dec 18, 2024, 08:06 PM UTC
We've worked with our provider and remediated the issue. We'll continue to monitor.
- resolved Dec 18, 2024, 08:41 PM UTC
This incident has been relsolved.
Notice December 11, 2024 Front AI features outage –
Started Dec 11, 2024, 11:30 PM UTC· resolved Dec 11, 2024, 11:30 PM UTC
- resolved Dec 13, 2024, 01:10 AM 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.
Minor November 25, 2024 Exchange Online mailboxes sync delay [office365] 18h 11m O365
Started Nov 25, 2024, 08:41 AM UTC· resolved Nov 26, 2024, 02:52 AM UTC
- identified Nov 25, 2024, 08:41 AM 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.
- identified Nov 25, 2024, 10:49 AM 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: https://portal.office.com/Adminportal/Home#/servicehealth/:/alerts/MO941162 (You need to be an O365 admin to be able to access it)
- identified Nov 25, 2024, 03:47 PM 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 signs of recovery; however, we have not observed any significant progress at this time.
- monitoring Nov 25, 2024, 08:26 PM 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 health closely as our mitigation workstreams continue in parallel.
- monitoring Nov 26, 2024, 12:07 AM UTC
Our systems have fully recovered. We are now retrying failed tasks.
- resolved Nov 26, 2024, 02:52 AM UTC
This incident has been resolved.
Major November 18, 2024 [us-west-2] Increased failure rate on public API 2h 15m API and integrations
Started Nov 18, 2024, 08:03 PM UTC· resolved Nov 18, 2024, 10:18 PM UTC
- investigating Nov 18, 2024, 08:03 PM 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.
- monitoring Nov 18, 2024, 08:44 PM UTC
The increased rate of errors has subsided as of approximately 10 minutes ago, but we are still determining the root cause.
- resolved Nov 18, 2024, 10:18 PM UTC
This incident has been resolved.
Minor October 29, 2024 [by_company_00017] Elevated loading times for some customers in us-west-1 41m App
Started Oct 29, 2024, 12:34 PM UTC· resolved Oct 29, 2024, 01:15 PM UTC
- investigating Oct 29, 2024, 12:34 PM 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.
- monitoring Oct 29, 2024, 12:47 PM UTC
We have put in place mitigations and are seeing a return to normal performance. We're continuing to monitor.
- resolved Oct 29, 2024, 01:15 PM UTC
This incident has been resolved.