26 major incidents detected for Robin AI. View live status dashboard →
On 2026-06-06 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-03 at 03:45 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 16m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-06-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-05-30 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-05-27 at 04:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 0m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-24 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-21 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 31m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-18 at 03:30 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 30m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-15 at 06:45 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 68h 15m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-12 at 06:15 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 68h 45m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-10 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-05-07 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-05-04 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 53m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-05-01 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-28 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-25 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-22 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-19 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-16 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-13 at 03:00 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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 Robin AI. 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:12 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-04 at 03:06 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. 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-01 at 03:03 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 57m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.
On 2026-03-29 at 03:10 UTC, DownForAI monitoring detected a significant service issue affecting Robin AI. The incident has been resolved after approximately 71h 50m. 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 Robin AI. 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.