- Level
- confirmed
- Worst impact
- Maintenance
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.Check that everything you run on LambdaTest came back after the window closed 2026-02-17 00:00 UTC.
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 will be performing a database maintenance. During this time, you may experience issues accessing our services and in running test executions. This update is essential to improve performance, security, and stability. Please plan accordingly to avoid disruptions. We sincerely apologize for any inconvenience this may cause and appreciate your understanding and patience during this time. Should you require any further assistance, please do not hesitate to contact our Support Team. Thank you for your continued trust in our services.
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-806314e5a8
Is this LambdaTest maintenance still going on?
No, it ended 2026-02-17 00:00 UTC.
How long did it last?
0m, from 2026-02-17 00:00 UTC to 2026-02-17 00:00 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.