Test Creation Timeouts

What to do

• Check whether your product depends on LambdaTest. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-09-28 09:00 UTC and 2026-09-28 09:00 UTC may need a replay.

• Subscribe to LambdaTest's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=lambdatest works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We experienced degraded performance due to a service disruption.

Updates from LambdaTest 1

1. resolvedSep 28, 2026, 9:00 AM UTC

   We experienced degraded performance due to a service disruption. We sincerely apologize for the inconvenience caused. Our team worked to restore normal operation as quickly as possible. For any questions or assistance, please reach out to our Support team. 2026-09-28T09:55:00.000Z Monitoring Real Device sessions have returned to normal operation. Some Automation and HyperExecute sessions may still take longer than usual to start. We are actively monitoring. 2026-09-28T13:30:00.000Z Resolved The issue has been resolved, and normal service operation has been restored. As a preventive measure, our team is reviewing the incident and implementing additional monitoring and safeguards to help prevent similar issues in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.