Secondary delivery standby unavailable during a hosting provider issue
Resolved
Oct 28, 2026 at 2:32pm UTC
On October 28 from 09:53 to 10:32 EDT (13:53–14:32 UTC), our secondary config-delivery standby (secondary.quonfig.com / stream.secondary.quonfig.com) returned 503 errors.
The host running the standby lost network connectivity, and our hosting provider's first two attempts to restart it failed. The third replacement instance started normally, warmed every workspace's configuration within seconds, and has been serving normally since.
The primary delivery service (primary.quonfig.com) was healthy throughout, and SDKs fall back to it automatically, so we don't expect any customer impact. During this window the standby was not available as a failover target.
No action is needed from customers.
Affected services