Live  /  Laravel Forge  /  Incident

Laravel Forge: Degraded performance in the Forge control panel

Laravel Forge · on-forge.comMajor incidentResolved2026-10-21 23:27 UTC
Public — what happened

Summary

Laravel Forge said its control panel was running slowly starting at 13:51 UTC on 2026-10-21, with pages loading slowly and some actions taking longer, while customers' servers and sites kept running normally. The company said it added capacity, and by 18:04 UTC it reported that a backlog of queued jobs had cleared. Slowness returned at 20:24 UTC, with some errors and delays to deployments, PHP updates and new server setups, which Forge attributed to a very large number of users updating PHP at once. By 22:12 UTC deployments were back to normal, though PHP update jobs were still catching up and live dashboard updates were switched off for the time being, and the incident was marked resolved at 23:27 UTC.

Affected

Forge Control Panel

As listed on Laravel Forge’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 Laravel Forge 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 Laravel Forge: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Laravel Forge report →

More from Laravel Forge

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

The full archive is on the Laravel Forge status & history page.

Related: Laravel Forge status & history. SquidGrid is not affiliated with Laravel Forge.