Front change history

Front reported a major outage affecting outbound sending on a subset of custom SMTP channels, listed as SMTP (non-Gmail / O365). It started at 2026-10-05 07:42 UTC and was resolved at 2026-10-05 09:45 UTC, lasting 2 h 2 min. Front deployed a fix but did not specify the cause.

Front reported a major O365 outage affecting a subset of customers, with offline channels preventing email sending or receiving. It started at 2026-05-28 18:24 UTC and was resolved at 2026-06-01 23:35 UTC, lasting 4 days 5 h. Front added automatic channel recovery while continuing to investigate remaining sync failures with Microsoft.

Front reported a critical outage affecting the App and API and integrations, starting 2026-01-23 21:51 UTC and lasting 3 h 49 min until resolution at 2026-01-24 01:40 UTC. Application and API access were restored at 01-23 22:28 UTC; Front confirmed a fix was implemented but did not disclose the cause.

A major Microsoft Office365 outage prevented affected Front customers from sending or receiving messages starting 2026-01-22 20:49 UTC. The incident lasted 8 h 46 min and was resolved at 2026-01-23 05:36 UTC; all pending messages were delivered, and Microsoft's remaining service degradation was no longer impacting Front.

Front recorded a critical App outage starting 2025-12-19 17:29 UTC, lasting 3 h 53 min and resolving at 2025-12-19 21:23 UTC. Its postmortem reports US-West-2 API latency from 14:50 UTC to 18:10 UTC prevented website loading and queued messages; no messages were lost. Missed-message and application-webhook backfills were completed.

Front reported a major outage affecting App, Calendar, and Rules and Workflows from 2025-11-21 19:21 UTC to 2025-11-21 22:18 UTC (2 h 56 min). A rollback began recovering failures in us-west-1, though rules and calendar delays persisted during recovery. Front linked the problem to a deployment changing internal caching connections and an environment-specific caching configuration.

Front reported a major outage affecting app loading in specific regions and causing timeouts for some API calls. It lasted 9 min, from 2025-09-26 16:47 UTC to 2025-09-26 16:56 UTC. Front stated that a cache node was lost and automatically recovered in 6 minutes; all systems should now be operational.

Front reported a major outage of Google sign-in on iOS: redirects back to the mobile app failed; Android was unaffected. It ran from 2025-09-19 18:40 UTC to 2025-09-23 09:48 UTC, lasting 3 days 15 h. Front confirmed iOS app version 5.69.2 fixed the issue; affected customers should update.

Front reported a critical App outage in us-west-2, with some customers unable to load the app, starting 2025-07-15 16:28 UTC. It was resolved at 2025-07-15 18:00 UTC after 1 h 31 min; Front said it identified the root cause and recovered but did not disclose the cause or fix.

Front reported a critical App outage in us-west-2: some customers experienced issues loading the app. It started at 2025-07-15 15:11 UTC and was resolved at 2025-07-15 15:52 UTC, lasting 41 min; a fix was implemented and monitored before resolution.

Front reported a critical web app loading outage, recorded as starting and resolving at 2025-06-09 21:00 UTC (computed duration: 0 min). A Content Distribution Network configuration change blocked access to files needed for startup; impact was limited to users trying to start the app during the affected window.

Front reported a critical App outage affecting roughly 3% of users, a subset of US-based customers in us-west-1, from 2025-04-29 23:54 UTC to 2025-04-30 05:43 UTC (5 h 49 min). Human error during planned maintenance made one database shard unrecoverable; Front restored it from an up-to-date backup and caught up missed messages.

Front reported major app-loading slowness in us-west-2 affecting by_company_00008, starting at 2025-03-19 17:24 UTC and lasting 35 min until resolution at 2025-03-19 17:59 UTC. A fix was implemented by 2025-03-19 17:42 UTC; no cause was stated.

Front reported a critical outage causing errors sending and receiving email for Office365 channels, starting 2025-03-14 21:49 UTC and resolved 2025-03-15 00:28 UTC, lasting 2 h 39 min. Front deployed a fix and monitored service before confirming resolution; no specific cause was disclosed.

Front reported a major Office 365 channel outage from 2025-03-01 21:14 UTC to 2025-03-01 22:32 UTC, lasting 1 h 17 min. An Office365 outage prevented user login and Front from sending and importing messages; Front later reported that Office appeared to have resolved the issue and was processing an import backlog before marking the incident resolved.

Front reported a major incident delaying automated emails, including notifications, teammate invites and calendar events, from 2024-12-18 19:33 UTC to 2024-12-18 20:41 UTC (1 h 8 min). Front worked with its provider to remediate the issue and marked it resolved.

Front reported a major public API incident in us-west-2, with increased 5xx errors potentially affecting sending and receiving messages on some channels. It ran from 2024-11-18 20:03 UTC to 2024-11-18 22:18 UTC, lasting 2 h 15 min. Errors subsided before resolution; no root cause or fix was stated.

Front reported a major incident affecting Gmail, O365, and SMTP (non-Gmail / O365) message sending and receiving from 2024-09-27 20:25 UTC to 2024-09-28 02:51 UTC (6 h 26 min). A manually deployed fix circumvented a Docker outage; delivery recovered with residual backlog delays. us-west-2 and eu-west-1 recovered before us-west-1.

Front reported a major incident delaying Gmail message sending and receiving, initially in us-west-2 and later across multiple regions. It started at 2024-09-13 15:38 UTC and resolved at 2024-09-13 19:25 UTC, lasting 3 h 47 min. Front suspected Gmail rate limiting, drained the message backlog, and reported all channels back to normal.