Live / Laravel Forge / Incident
Laravel Forge: Nginx may fail to start on some servers
Laravel Forge · on-forge.comResolved2026-09-03 20:15 UTC
Public — what happened
Summary
Laravel Forge reported that Nginx, the web server software, might not start on some servers it manages, beginning on 3 September 2026 at 19:47 UTC. The company said the problem comes from a Brotli compression module it adds when setting up servers, which only works with one specific Nginx version and stops loading once Nginx is upgraded, something automatic updates can do on their own. Forge said new servers are no longer affected, but those set up since 10 August could still be at risk, and it was working on an automated fix while advising customers with sites down to contact support. The incident is listed with a resolution time of 10 September at 13:13, though its status still reads as identified.
Timeline
- Started — 2026-09-03 19:47 UTC
- Resolved — 2026-09-10 13:13 UTC · 7 days after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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 37, 2026, our weekly internet health report.