Live  /  Front  /  Incident

Front: [by_company_00015] Delays on channel imports for a subset of us-west-1 customers

Front · frontapp.comMinor incidentResolved2026-11-12 13:15 UTC
Public — what happened

Summary

Front said that some customers in its us-west-1 region faced delays when bulk importing messages from newly connected channels, because the queues handling those imports had built up a backlog. The company reported the problem began at 08:05 UTC on 2026-11-12 and said fewer than 10 customers were affected. By 09:26 UTC it said the backlog was starting to shrink, and the incident was marked resolved at 13:15 UTC. Front classed it as minor and did not describe a cause in its updates.

Affected

Other channels

As listed on Front’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Front against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Front: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Front report →

More from Front

Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.

The full archive is on the Front status & history page.

Related: Front status & history. SquidGrid is not affiliated with Front.