Live  /  Laravel Forge  /  Incident

Laravel Forge: Some Let's Encrypt certificates failing to issue or renew

Laravel Forge · on-forge.comMinor incidentResolved2026-09-02 19:06 UTC
Public — what happened

Summary

Laravel Forge reported that some servers were unable to issue or renew Let's Encrypt security certificates, beginning on 2026-09-02 at 19:06 UTC. The company said the process was failing at the step where it downloads its certificate tool from GitHub, before any domain checks happen, and that customers' own DNS, firewall or site settings were not the reason. Forge advised users to retry failed certificates from the site's Domains tab, especially any nearing expiry. The incident was listed as minor and still under investigation, though a resolution time of 2026-09-11 at 02:29 was also recorded.

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 37, 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.