- 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-06-02 12: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 have a scheduled database maintenance window by our cloud provider on Sun, 07 Jun 2026 04:00:00 GMT and Sun, 07 Jun 2026 05:00:00 GMT. This maintenance is necessary to ensure the continued stability and performance of our services. We understand the importance of our services to your operations and apologize for any inconvenience this downtime may cause. However, these upgrades are necessary to enhance the overall user experience and ensure the stability of our platform. Thank you for your understanding and cooperation. Please reach out to our support team at support@lambdatest.com in case of any concerns.
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-c74f4051ba
Is this LambdaTest maintenance still going on?
No, it ended 2026-06-02 12:00 UTC.
How long did it last?
0m, from 2026-06-02 12:00 UTC to 2026-06-02 12: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.