- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 28of 100
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 2025-10-01 07:36 UTC and 2025-10-01 07:36 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.
Updates from LambdaTest 1
- resolved
Due to a minor issue in one of our services, we have experience the test queuing problem. Our internal alerting system promptly detected the issue. Our engineering team responded within a time and resolved this concern. We apologize for any disruption this may caused and we appreciate your patience. If you continue to encounter problems or need immediate assistance, don't hesitate to contact our Support team at support@lambdatest.com. 2025-10-01T08:07:00.000Z Resolved The issue has been fixed now and we are actively monitoring it.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-27a57bf631
Is LambdaTest still down?
No, this incident was resolved 2025-10-01 07:36 UTC. For LambdaTest's live state, see https://down.guide/lambdatest.
How long did it last?
0m, from 2025-10-01 07:36 UTC to 2025-10-01 07:36 UTC, by the times LambdaTest posted.
What caused it?
LambdaTest hasn't published a root cause. If it does, it shows here.
Where does this come from?
LambdaTest's official status page, https://status.lambdatest.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.