TCP Backup2Cloud US Node 1:4401, TCP Backup2Cloud US Node 2:4401, and 5 other services are down
Resolved
May 20, 2025 at 08:56pm UTC
Service has been restored
Affected services
Updated
May 20, 2025 at 06:11pm UTC
At present our US provider is escalating this to their ISP (Cogent) who appear to be having quite a few issues that match the start time of this incident.
Affected services
Updated
May 20, 2025 at 05:46pm UTC
TCP Backup2Cloud US Node 3:4401 went down.
Affected services
Updated
May 20, 2025 at 05:43pm UTC
TCP Backup2Cloud US Node 2:4401, TCP Backup2Cloud US DE Node 1:4401, and TCP Backup2Cloud US CT Node 3:4401 went down.
Affected services
Updated
May 20, 2025 at 05:43pm UTC
TCP Backup2Cloud US Node 1:4401, TCP Backup2Cloud US CT Node 1:4401, and TCP Backup2Cloud US CT Node 2:4401 went down.
Affected services
Updated
May 20, 2025 at 08:19am UTC
TCP Backup2Cloud US CT Node 1:4401 recovered.
Affected services
Updated
May 20, 2025 at 08:19am UTC
TCP Backup2Cloud US DE Node 1:4401 and TCP Backup2Cloud US CT Node 3:4401 recovered.
Affected services
Updated
May 20, 2025 at 08:18am UTC
TCP Backup2Cloud US CT Node 1:4401 went down and TCP Backup2Cloud US Node 3:4401 recovered.
Affected services
Updated
May 20, 2025 at 08:18am UTC
TCP Backup2Cloud US Node 2:4401 and TCP Backup2Cloud US CT Node 2:4401 recovered.
Affected services
Updated
May 20, 2025 at 08:18am UTC
TCP Backup2Cloud US DE Node 1:4401 and TCP Backup2Cloud US CT Node 3:4401 went down.
Affected services
Created
May 20, 2025 at 08:18am UTC
TCP Backup2Cloud US Node 2:4401, TCP Backup2Cloud US Node 3:4401, and TCP Backup2Cloud US CT Node 2:4401 went down.
Affected services