Incident History

Between 08:30 UTC and 14:30 UTC, some customers in a specific environment in us-east-2 experienced sporadic 502 errors on HTTP requests. The issue was traced to an internal DNS disruption that intermittently prevented resolution for certain application endpoints, affecting only a portion of traffic to those applications. The issue is now resolved, and we are implementing measures to prevent similar occurrences in the future.

GitHub has reported that this issue is resolved.

This incident has been resolved.

This incident has been resolved.

We observed a temporary interruption in deployments lasting approximately 45 minutes due to an upstream issue with GitHub webhooks. The issue has been identified and resolved by GitHub.

More details are available in GitHub’s incident report: https://www.githubstatus.com/incidents/6swp0zf7lk8h

This incident was resolved Aug 04, 2025 - 19:35 UTC.

https://www.cloudflarestatus.com/incidents/ffwzxb94kxk9

What happened
Starting at 09:21 UTC on July 24, 2025, the Laravel Cloud dashboard became unavailable, including the ability to deploy applications. All hosted applications continued running without interruption — we only impacted the part of the platform you use to manage and deploy your applications. Full service was restored at 09:37 UTC, for a total downtime of 16 minutes.

What caused it
A scheduled database migration that added a new column to our deployments table was blocked by an existing long-running query against that same table. Because the migration couldn’t acquire the necessary lock, the deployment pipeline stalled. Once we identified and terminated the blocking query, the migration completed successfully.

How we fixed it

1. We identified the long running query that was holding the lock and causing the deployment to fail.
2. We deployed a hotfix for that query, and fixed our migration to handle any partial state changes.
3. We retriggered the deployment pipeline, which completed successfully and restored all services.

What we’re doing next

• We have added alerts in place to notify us of long-running queries that could block deployments in the future.
• We're reviewing and optimizing our schema to prevent similar issues happening in the future.
• We will ensure our status page is updated with the most detailed information about incidents like this in the future.

This incident has been resolved.

Upstream issue appears to be resolved

This incident has been resolved.