- Level
- confirmed
- Worst impact
- Degraded
- Components
- Website
What to do
Check whether you use Todoist Website. 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-06-09 11:52 UTC and 2026-06-09 11:52 UTC may need a replay.Subscribe to Todoist's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=todoist works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Todoist 1
- resolved
Type: Incident Duration: 1 hour and 36 minutes Affected Components: Website Jun 9, 13:28:28 GMT+0 - Resolved - Users should now be able to log in with their Google credentials. We apologize for the inconvenience! Jun 9, 11:52:31 GMT+0 - Investigating - Some users have reported that they can't log in with Google credentials. We are currently investigating the issue and will provide an update here as soon as we have more information. We sincerely apologize for the inconvenience! 🙏
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-97db61ce51
Is Todoist still down?
No, this incident was resolved 2026-06-09 11:52 UTC. For Todoist's live state, see https://down.guide/todoist.
How long did it last?
0m, from 2026-06-09 11:52 UTC to 2026-06-09 11:52 UTC, by the times Todoist posted.
What was affected?
Todoist named Website.
What caused it?
Todoist hasn't published a root cause. If it does, it shows here.
Where does this come from?
Todoist's official status page, https://status.todoist.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.