On September 29 from 07:29 to 07:54 EDT (11:29-11:54 UTC), our secondary config-delivery standby (secondary.quonfig.com / stream.secondary.quonfig.com) returned 503 errors.

The standby's hosting provider stopped the instance it was running on, and it was restarted on a new host. The restart was normal except for a slow container image pull, which accounted for most of the 25-minute recovery. Once the new instance was up, it was fully warmed with every workspace's configuration and serving normally.

The primary delivery service (primary.quonfig.com) was fully healthy throughout, and SDK clients kept getting configs from it without interruption. There was no customer impact. For those 25 minutes, the only effect was that the standby was not available as a failover target.

No action is needed from customers.