- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 28of 100
What to do
Check whether you use LambdaTest in us. 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-05-13 23:30 UTC and 2025-05-13 23: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
Our US data center experienced a network outage from 11:30 PM UTC on May 13, 2025, to 2:00 AM UTC on May 14, 2025. During this window, you may have encountered connectivity issues or test failures. Our engineering team identified and resolved the problem promptly. We apologize for any inconvenience and appreciate your patience. If you need further assistance, please don't hesitate to contact our Support team. 2025-05-14T02:00:00.000Z Resolved The issue has been fixed, 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-c2aca47cf8
Is LambdaTest still down?
No, this incident was resolved 2025-05-13 23:30 UTC. For LambdaTest's live state, see https://down.guide/lambdatest.
How long did it last?
0m, from 2025-05-13 23:30 UTC to 2025-05-13 23:30 UTC, by the times LambdaTest posted.
What was affected?
LambdaTest named in us.
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.