- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 18of 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 2026-01-26 04:10 UTC and 2026-01-26 04:10 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 experienced a network issue in one of our US West data centers between 04:10 AM UTC and 04:30 AM UTC, which may have caused test cancellations for a subset of users. The impacted hosts have been isolated, and the issue has been fully resolved. There are no further test cancellations at this time. 2026-01-26T04:30: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-de1906fafb
Is LambdaTest still down?
No, this incident was resolved 2026-01-26 04:10 UTC. For LambdaTest's live state, see https://down.guide/lambdatest.
How long did it last?
0m, from 2026-01-26 04:10 UTC to 2026-01-26 04:10 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.