Front Outage History

20 incidents recorded over the last 365 days, 20 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Front status100.00% uptime history

Every Recorded Front Incident

Front incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 4, 2026[us-west-1] High API latency currently causing delaysThe incident has been resolved1h 25mResolved
Oct 6, 2026Delays on generation of certain AI outputsThis incident has been resolved.34 minResolved
Oct 5, 2026[smtp] Problems with outbound sending on custom SMTP channelsThis incident has been resolved.2h 2mResolved
Sep 27, 2026[us-west-2] Elevated API error rates may cause delaysThe upstream issues causing delays in our system have been resolved.14 minResolved
Sep 23, 2026[office365] [gmail] delays in sending and receiving messages for customers in [us-west-1], [us-west-2], and [eu-west-1]This incident has been resolved.4h 22mResolved
Sep 14, 2026[office365] Delays in sending and receiving messages for some customers in [us-west-1] and [us-west-2]This incident has been resolved.2h 40mResolved
Aug 31, 2026Application performance degradedThis incident has been resolved, and all activities have caught up to realtime. Front will continue to monitor application performance.1h 7mResolved
Aug 15, 2026Resource audit log delayed events [eu-west-1][by_company_00006]This incident has been resolved.32 minResolved
May 28, 2026[office365] Office channels offline preventing emails being sent or receivedFront 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.101h 11mResolved
Apr 25, 2026Folder counters update delayThis incident has been resolved.32 minResolved
Apr 14, 2026Delay in messages sent or received over SlackThis incident has been resolved.2h 56mResolved
Feb 23, 2026Delays receiving emails from Gmail and Office channels in [us-west-2]This incident has been resolved.2h 53mResolved
Feb 18, 2026Shared inboxes not visible in the mobile appThis incident has been resolved.2h 9mResolved
Feb 7, 2026Message import delayedThis incident has been resolved.23 minResolved
Jan 23, 2026Front is inaccessibleThis incident has been resolved. A fix has been implemented.3h 49mResolved
Jan 22, 2026Microsoft Office365 IncidentMicrosoft is still reporting service degradation, but it's not impacting Front. We'll continue monitoring the situation in case it changes.8h 46mResolved
Dec 19, 2025App not respondingOn 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…3h 53mResolved
Dec 10, 2025Errors loading conversationsThis incident has been resolved.14h 53mResolved
Dec 1, 2025Delegated inboxes not visibleWe have restored delegated inboxes. If delegated inboxes are not currently visible, please restart the application.8 minResolved
Nov 21, 2025[by_company_00017] Front App OutageAt 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…2h 56mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Front incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Front Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Front acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Front outage in this window ran 4d 5h, against a mean recovery of 7h 52m. If you depend on Front in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.