Skip to content

Outage tracker

Front: the full evidence record

The last 24 hours in detail, 15 days of measured availability, a 12-month summary, our own incident log, Front's declared record, and how the two compare.

← Back to Front's live status

We started measuring Front on August 22, 2026, which is 15 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Front's own status page declared. Below it, any public chatter we saw about Front and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Front's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Unverified user reportsNo reports about Front in the last 24 hours, which is not evidence that nothing is wrong.
Front's status pageNo incident declared in the last 24 hours.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is Front's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention Front next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East100.00%617
US-West100.00%616
Europe100.00%613
Asia-Pacific100.00%597
US-Central100.00%59
Canada100.00%59
UK100.00%59
Southeast Asia100.00%56
Australia100.00%56
South America100.00%58

Monthly summary

Tracking Front since Aug 22, 2026. In that time our probes detected no outage. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Oct 2025not tracked
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 2026100%00 min
Sep 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for Front: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and Front's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for Front in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: Front's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

No outages detected for Front since we started measuring it on August 22, 2026. We show nothing from before that date.

Their declared record

Front's own incident history, taken from their public status feed. This is their account of what happened, not our measurement, and it never changes the incident log above or the other way around.

Application performance degradedMinor incident
Aug 31, 2026, 3:43 PM UTC to Aug 31, 2026, 4:51 PM UTC (1h 8m)resolved
their latest update (Aug 31, 2026, 4:51 PM UTC): This incident has been resolved, and all activities have caught up to realtime. Front will continue to monitor application performance.
Resource audit log delayed events [eu-west-1][by_company_00006]All systems operational
Aug 15, 2026, 8:11 PM UTC to Aug 15, 2026, 8:44 PM UTC (33 min)resolved
their latest update (Aug 15, 2026, 8:44 PM UTC): This incident has been resolved.
[office365] Office channels offline preventing emails being sent or receivedPartial outage
May 28, 2026, 6:24 PM UTC to Jun 1, 2026, 11:35 PM UTC (4d 5h)resolved
their latest update (Jun 1, 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.
Folder counters update delayMinor incident
Apr 25, 2026, 6:37 PM UTC to Apr 25, 2026, 7:09 PM UTC (32 min)resolved
their latest update (Apr 25, 2026, 7:09 PM UTC): This incident has been resolved.
Delay in messages sent or received over SlackMinor incident
Apr 14, 2026, 5:03 PM UTC to Apr 14, 2026, 8:00 PM UTC (2h 57m)resolved
their latest update (Apr 14, 2026, 8:00 PM UTC): This incident has been resolved.
Delays receiving emails from Gmail and Office channels in [us-west-2]Minor incident
Feb 23, 2026, 3:17 PM UTC to Feb 23, 2026, 6:10 PM UTC (2h 54m)resolved
their latest update (Feb 23, 2026, 6:10 PM UTC): This incident has been resolved.
Shared inboxes not visible in the mobile appMinor incident
Feb 18, 2026, 2:59 PM UTC to Feb 18, 2026, 5:08 PM UTC (2h 10m)resolved
their latest update (Feb 18, 2026, 5:08 PM UTC): This incident has been resolved.
Message import delayedMinor incident
Feb 7, 2026, 12:03 AM UTC to Feb 7, 2026, 12:26 AM UTC (23 min)resolved
their latest update (Feb 7, 2026, 12:26 AM UTC): This incident has been resolved.
Front is inaccessibleMajor outage
Jan 23, 2026, 9:51 PM UTC to Jan 24, 2026, 1:40 AM UTC (3h 50m)resolved
their latest update (Jan 24, 2026, 1:40 AM UTC): This incident has been resolved. A fix has been implemented.
Microsoft Office365 IncidentPartial outage
Jan 22, 2026, 8:49 PM UTC to Jan 23, 2026, 5:36 AM UTC (8h 47m)resolved
their latest update (Jan 23, 2026, 5: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.

Showing the 10 most recent of 51 incidents Front has declared in the history we hold.

These entries are Front's own declarations, taken from their public status feed, shown separately from the outages we detected ourselves. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

The scorecard

How Front's status page compared with what we measured, for every outage above that falls inside the window we have been capturing their claims.

We started recording Front's own status page on August 22, 2026, 13 days ago. This comparison covers that period only, we do not reconstruct what they said before it, and we compare only inside outages we measured ourselves.

We have not measured an outage for Front since we started recording their status page, so there is nothing to compare. That is a short measurement window, not a track record.

Front decides what their status page covers, and it may report per component while our check reaches one surface from ten regions. We state what each side measured and leave the conclusion to you. If Front believes a figure here is wrong, we publish corrections as prominently as the original.

Full detail on what a probe does and does not prove is in the methodology page.