Laravel Forge Incident History

Deployments have fully returned to normal. If a deployment failed during this window, retrying should now succeed.

A fix has been deployed and deployments are succeeding again. We're monitoring to confirm stability before considering this resolved.

The issue has been identified and a fix is being implemented.

Some users may hit a 500 error when triggering a deployment on Forge. Your live sites, servers, and the rest of your infrastructure are not affected and continue to run normally. This is limited to starting new deployments.

Deployments have fully returned to normal. If a deployment failed during this window, retrying should now succeed.

Deployments are succeeding again. We are monitoring to confirm stability before considering this resolved.

Deployments on Forge are failing for some users due to a degradation on the GitHub API. If your deployments are failing, please wait a while and try again. More information is available at https://www.githubstatus.com/incidents/gxycch3076xk

This incident has been resolved.

A fix has been implemented and DigitalOcean are monitoring the results. If you have a server in the TOR1 (Canada) region that is still not responding, please initiate a reboot within the Forge Control Panel. If the server continues to be unresponsive after this, our Support Team is available to assist.

Our third-party provider has identified the cause of the issue affecting IP routing in the TOR1 region, which was causing inbound and outbound traffic to and from IPs in TOR1 to fail. Their engineering team is now working on implementing a fix. We will provide additional updates as more information becomes available to us.

Our third-party provider has reported an issue with IP routing in our Canadian, Toronto region affecting Laravel VPS customers. They've investigating the cause of the disruption and are working to restore service.