Harness (Split)
Developer Tools
90-Day Uptime History
Event Log
5h ago
7h ago
8h ago
14h ago
20h ago
Apr 5, 9:32 AM
Apr 5, 3:32 AM
Apr 4, 9:31 PM
Apr 4, 3:30 PM
Apr 4, 2:00 PM
Apr 4, 9:30 AM
Apr 4, 3:30 AM
Apr 3, 9:30 PM
Apr 3, 4:54 PM
We are continuing to monitor for any further issues.
Apr 3, 4:53 PM
Apr 3, 11:54 AM
Apr 3, 5:54 AM
Apr 2, 11:54 PM
Apr 2, 5:54 PM
Apr 2, 5:54 PM
Apr 2, 3:14 PM
We are investigating a degradation in CI steps when using AWS connectors and inherited authentication.
Apr 2, 3:13 PM
Apr 2, 2:24 PM
Apr 2, 8:41 AM
Apr 2, 8:24 AM
Apr 2, 2:24 AM
Apr 1, 8:24 PM
Apr 1, 2:24 PM
Apr 1, 8:23 AM
Apr 1, 8:22 AM
Apr 1, 8:21 AM
Apr 1, 6:17 AM
Update: AutoStopping functionality for AWS has been restored for all regions except me-south-1. The issue was caused by elevated latency from AWS in the affected region, impacting operations such as warm-up, cool-down, schedule execution, and traffic detection. We have now isolated this region to prevent impact on other customers. Resources in me-south-1 will continue to experience the issue until the region fully recovers. We are actively monitoring the situation and will provide further updates as available.
Apr 1, 6:16 AM
Apr 1, 1:06 AM
Mar 31, 7:06 PM
Mar 31, 1:05 PM
Mar 31, 7:05 AM
Mar 31, 1:05 AM
Mar 30, 7:04 PM
Mar 30, 1:03 PM
Mar 30, 7:03 AM
Mar 30, 1:02 AM
Mar 29, 7:01 PM
Mar 29, 1:01 PM
Mar 29, 7:01 AM
Mar 29, 4:31 AM
Mar 29, 1:08 AM
Mar 28, 7:08 PM
Mar 28, 1:08 PM
Mar 28, 7:08 AM
Sites Using Harness (Split)
2 analyzed sites depend on Harness (Split). If this service goes down, these sites may be affected.
Detection patterns, related technologies, and usage stats
Live dashboard for all monitored developer services
See how Harness (Split) status affects a real site
Status data polled every 60 seconds. History retained for 90 days. Snapshots stored on status changes.