- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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-05-26 12:30 UTC and 2025-05-26 12: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 experienced a brief performance degradation in some regions with LT Tunnel servers between 09:30 AM UTC and 12:30 PM UTC. Our engineering team promptly identified the root cause and resolved the issue within this timeframe. We sincerely apologize for any inconvenience this may have caused. Our Support Team remains available to assist you further if needed, and we appreciate your continued trust and understanding. 2025-05-26T12: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-b973f4490a
Is LambdaTest still down?
No, this incident was resolved 2025-05-26 12:30 UTC. For LambdaTest's live state, see https://down.guide/lambdatest.
How long did it last?
0m, from 2025-05-26 12:30 UTC to 2025-05-26 12: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.