Cloud Base

We monitor our systems around the clock. This page shows live status, active incidents, and maintenance windows so you always know what's happening.

← Back to Status
critical RESOLVED

CloudBase API - #368956

Affected Service
CloudBase API
Started
Apr 09, 2026 08:01 UTC
Resolved
Apr 09, 2026 10:36 UTC
Duration
2.6 hours

Incident Timeline

Apr 09, 2026 10:36 UTC

Monitor is back up. Incident resolved automatically.

Apr 09, 2026 08:01 UTC

Monitor detected as down. Location: us-nyc-1 Cause: Request failed: Get "https://apptlysoft1.com": dial tcp: lookup apptlysoft1.com on 127.0.0.53:53: no such host

CloudBase API DNS lookup failure

Published Apr 09, 2026 13:05 UTC
critical Duration: 2 hours 35 minutes Detection: StatusDrift synthetic HTTP monitoring

Summary

StatusDrift detected that the CloudBase API became unavailable when the monitor could no longer resolve apptlysoft1.com. The incident started at 08:01 UTC on April 9, 2026 and cleared at 10:36 UTC after DNS resolution recovered.

Impact

Requests that depended on the CloudBase API hostname failed during the incident window. Customers using the affected endpoint could see request errors until DNS resolution was restored.

Timeline

Time Event
08:01 UTC StatusDrift detected the CloudBase API as down after DNS lookup for apptlysoft1.com returned no such host.
10:36 UTC DNS resolution recovered and the monitor marked the incident resolved automatically.

Trigger

The incident began when DNS lookups for apptlysoft1.com started returning no such host for the monitored endpoint.

Root cause

An upstream DNS resolution failure prevented the monitor from resolving the API hostname, so the service could not be reached by name.

Resolution

Service recovered once DNS resolution for the hostname was restored. StatusDrift automatically marked the incident resolved after the endpoint started responding again.