Changes / Trello / Trello is down
Trello: Critical incident: Trello is down
Summary
Trello reported a critical outage affecting API and Trello.com, preventing multiple users from connecting to its servers. It started at 2023-11-10 14:43 UTC and was resolved at 2023-11-10 16:19 UTC, lasting 1 h 35 min. Trello said its changes fixed the connection issues and all services were functional.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Trello is down
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2023-11-10 14:43 UTC
Before: not present
After: 2023-11-10 16:19 UTC
Before: not present
After: API, Trello.com
Before: not present
After: We've identified an issue on Trello that's affecting multiple users to connect to our servers. We'll provide a new update soon.
Before: not present
After: We are continuing to work on a fix for this issue.
Before: not present
After: We've identified the root cause of the issue, and we made some adjustments, which should bring Trello's functionalities back soon.
Before: not present
After: The changes we released have fixed the connection issues our users were experiencing when connecting to Trello. We're now monitoring it.
Before: not present
After: We want to let you know that the changes we made on our side fixed all the connection issues our users were experiencing with Trello, and all services are functional right now. We appreciate your patience and understanding.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Trello is down (this change) Trello reported a critical outage affecting API and Trello.com, preventing multiple users from connecting to its servers. It started at 2023-11-10 14:43 UTC and was resolved at 2023-11-10 16:19 UTC, lasting 1 h 35 min. Trello said its changes fixed the connection issues and all services were functional. | Major incident |