TCP Backup2Cloud US Node 1:4401, TCP Backup2Cloud US Node 2:4401, and 4 other services are down
Resolved
May 30, 2025 at 09:06pm UTC
TCP Backup2Cloud US CT Node 3:4401 recovered.
Affected services
Updated
May 30, 2025 at 09:06pm UTC
TCP Backup2Cloud US Node 1:4401, TCP Backup2Cloud US Node 2:4401, TCP Backup2Cloud US Node 3:4401, and 2 other resources recovered.
Affected services
Updated
May 30, 2025 at 08:47pm UTC
TCP Backup2Cloud US Node 3:4401 went down.
Affected services
Updated
May 30, 2025 at 08:47pm UTC
TCP Backup2Cloud US Node 1:4401 went down.
Affected services
Updated
May 30, 2025 at 08:47pm UTC
TCP Backup2Cloud US CT Node 3:4401 went down.
Affected services
Updated
May 30, 2025 at 08:46pm UTC
TCP Backup2Cloud US Node 2:4401 and TCP Backup2Cloud US CT Node 2:4401 went down.
Affected services
Updated
May 30, 2025 at 08:46pm UTC
TCP Backup2Cloud US CT Node 1:4401 went down.
Affected services
Updated
May 30, 2025 at 01:32pm UTC
TCP Backup2Cloud US CT Node 3:4401 recovered.
Affected services
Updated
May 30, 2025 at 01:31pm UTC
TCP Backup2Cloud US CT Node 2:4401 recovered.
Affected services
Updated
May 30, 2025 at 01:31pm UTC
TCP Backup2Cloud US CT Node 1:4401 recovered.
Affected services
Updated
May 30, 2025 at 01:30pm UTC
TCP Backup2Cloud US CT Node 2:4401 went down.
Affected services
Updated
May 30, 2025 at 01:24pm UTC
TCP Backup2Cloud US CT Node 1:4401 went down.
Affected services
Created
May 30, 2025 at 01:24pm UTC
TCP Backup2Cloud US CT Node 3:4401 went down.
Affected services