Front reported "[smtp] Problems with outbound sending on custom SMTP channels" on its status page at 2026-10-05 07:42 UTC.

Front lists these components: SMTP (non-Gmail / O365).

When did the incident start and end?

It started at 2026-10-05 07:42 UTC and ended at 2026-10-05 09:45 UTC. It lasted 2 h 3 min.

How do I get alerts for Front?

Subscribe to the Front live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Front. outages.live reads it every few minutes and keeps every update.

FrontIncident · 2026-10-05 07:42 UTC

[smtp] Problems with outbound sending on custom SMTP channels

ResolvedOfficial update

This incident has been resolved.

The latest update from Front.

State

Resolved

Started

28 d ago

2026-10-05 07:42 UTC

Lasted

2 h 3 min

until 2026-10-05 09:45 UTC

Worst impact

Partial outage

Timeline

4 updates

07:4208:1308:4309:1409:45

Partial outageUpdate postedTimes in UTC

Investigating

52 min 42%

Identified

39 min 32%

Monitoring

32 min 26%

Updates

Times in UTC

As posted by Front

Resolved2026-10-05 09:45 UTC

This incident has been resolved.

Monitoring2026-10-05 09:13 UTC

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

Identified2026-10-05 08:34 UTC

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

Investigating2026-10-05 07:42 UTC

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

Affected components

SMTP (non-Gmail / O365)

Front in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 8 min

This incident

1.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 23 min

median 1 h 8 min

90 days agoToday

Other Front incidents

All incidents

Front·Delays on generation of certain AI outputs

This incident has been resolved.

Resolvedresolved 26 d ago

Front·[us-west-2] Elevated API error rates may cause delays

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

Resolvedresolved 36 d ago

Front·[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.

Resolvedresolved 39 d ago

Front·[office365] Delays in sending and receiving messages for some customers in [us-west-1] and [us-west-2]

This incident has been resolved.

Resolvedresolved 49 d ago

Front·Application performance degraded

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

Resolvedresolved 62 d ago

Follow Front

Your coding agent knows when Front is down, and tells you when a failure is theirs, not yours. You can also get Front incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "front" and tell me if Front has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.live/feed.xml?providers=front

Slack

/feed subscribe https://outages.live/feed.xml?providers=front

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane