Tight incident

Tight API DNS Issues

Minor Resolved View vendor source →

Tight experienced a minor incident on March 16, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 16, 2026, 08:45 PM UTC
Resolved
Mar 16, 2026, 08:45 PM UTC
Duration
—
Detected by Pingoru
Mar 16, 2026, 08:45 PM UTC

Update timeline

  1. investigating Mar 16, 2026, 06:25 PM UTC

    Status: Investigating A DNS resolution failure at GoDaddy is causing a geographic-based partial outage affecting Tight users.

  2. resolved Mar 16, 2026, 08:45 PM UTC

    Status: Resolved Tight is seeing restored behavior resolving the API's DNS.