Incident History

Laravel Cloud Dashboard Downtime

This incident has been resolved.

1758835900 - 1758837027 Resolved

Partial degradation of platform services

The issues affecting metrics has been fully resolved. All platform components are operating normally.

We’ll continue to monitor for stability.

1758760318 - 1758763462 Resolved

New Laravel MySQL instances may not come online in Sydney

This incident has been resolved.

1758644509 - 1758650530 Resolved

KV Store service degradation

This incident has been resolved.

1756752561 - 1756806458 Resolved

Laravel Cloud Dashboard Downtime

This incident has been resolved.

1755076111 - 1755077409 Resolved

Intermittent errors on select applications in us-east-2 (Ohio)

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.

1755031203 - 1755031203 Resolved

GitHub issues may impact deployments

GitHub has reported that this issue is resolved.

1755009672 - 1755022008 Resolved

Log Service Degradation

This incident has been resolved.

1754505135 - 1754508545 Resolved

Laravel Serverless Postgres service degradation

This incident has been resolved.

1754494375 - 1754550542 Resolved

GitHub Webhook Disruption Impacting Deployments

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

1754416151 - 1754416151 Resolved
⮜ Previous Next ⮞