- 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-29 16:30 UTC and 2025-10-29 16:30 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
We’re currently experiencing an outage with our cloud provider which might result in test failures or degraded performance. We sincerely apologize for the inconvenience. Our team is working actively with the cloud provider to restore the services. Please reach out to the Support team if you have any questions. https://azure.status.microsoft/en-gb/status 2025-10-29T20:30:00.000Z Resolved This issue has been resolved and we'll continue to monitor it. Thank you for your patience!
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-c7f3dcb8a8
Is LambdaTest still down?
No, this incident was resolved 2025-10-29 16:30 UTC. For LambdaTest's live state, see https://down.guide/lambdatest.
How long did it last?
0m, from 2025-10-29 16:30 UTC to 2025-10-29 16:30 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.