Linq incident
Partial degradation on some lines due to network hardware maintenance
Resolved after 1 hour 47 minutes, affecting Linq V3 API, on August 13, 2026.
At approximately 4:38 AM CT, the affected lines came back online and service has been restored. We are marking this incident as resolved. Thank you for your patience.
Affected components
Update timeline
- identified Aug 13, 2026, 08:31 AM UTC
Some Linq partner phone lines are currently experiencing degradation while networking hardware at one of our data centers runs an update. An on-site engineer is working to get everything restored as soon as possible. We will update this status page once service is fully restored.
- identified Aug 13, 2026, 09:41 AM UTC
To restore service as quickly as possible, we are moving the affected lines over to backup networking equipment. We expect to be live on the backup equipment shortly and will post another update once service is fully restored.
- resolved Aug 13, 2026, 09:42 AM UTC
At approximately 4:38 AM CT, the affected lines came back online and service has been restored. We are marking this incident as resolved. Thank you for your patience.
Your product runs on more than Linq
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services