A DNS resolution failure at GoDaddy caused a partial outage affecting Tight users. The issue was resolved by migrating DNS hosting from GoDaddy to Amazon Route 53, completed at approximately 4:35 PM ET.
GoDaddy's DNS resolution service failed to properly resolve Tight's domain for a subset of users depending on their network and DNS resolver. The failure originated entirely within GoDaddy's infrastructure and was outside of Tight's direct control. This issue was not detected by Tight’s monitoring systems because the geographic regions Tight presently monitors from were never impacted.
Tight was first notified at 2:25 PM ET, identified GoDaddy as the root cause at 3:01 PM ET, and began migrating DNS hosting from GoDaddy to Amazon Route 53 at 3:05 PM ET. The switchover was completed at 4:35 PM ET. Tight continued to monitor global propagation following the switchover to confirm successful resolution.
GoDaddy did not publish any incident to their status page until 4:17 PM ET. Because of GoDaddy’s delayed response and the lack of any known resolution time from their end, the Tight team elected to migrate their DNS resolution to Route53 to mitigate this issue as quickly as possible.
DNS Provider Migration: Tight has permanently moved DNS hosting to Amazon Route 53, eliminating dependency on GoDaddy's infrastructure going forward.
DNS Monitoring: Tight will implement additional DNS resolution monitoring across a variety of geographic regions around the world to detect future DNS-layer failures faster and reduce time-to-detection and time-to-mitigation.
