19 major incidents detected for Trae. View live status dashboard →
On 2026-05-18 at 06:45 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 48h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-15 at 05:30 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 69h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-12 at 05:00 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 70h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-09 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-06 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-03 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-30 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-27 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-24 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-21 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-18 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-16 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 48h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-13 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-10 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-07 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 54m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-04 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 72h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-04-01 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-03-29 at 03:04 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 71h 56m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-03-26 at 08:36 UTC, DownForAI monitoring detected a significant service issue affecting Trae. The incident has been resolved after approximately 66h 24m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.