Secondary delivery standby briefly unreachable during a hosting provider issue
Resolved
Nov 13, 2026 at 7:27pm UTC
On November 13 from 14:11 to 14:27 EST (19:11–19:27 UTC), most requests to our secondary config-delivery standby (secondary.quonfig.com / stream.secondary.quonfig.com) timed out or returned 503 errors.
The standby's hosting provider had a platform incident with an elevated rate of 5XX errors at its network edge. Our standby instance itself stayed healthy and kept answering the requests that reached it; the provider's edge was failing in front of it. Nothing changed on our side, and the standby recovered when the provider's edge did.
The primary delivery service (primary.quonfig.com) was healthy throughout, and SDKs only use the standby when the primary is unreachable, so we don't expect any customer impact. During this window the standby was not reliably available as a failover target.
No action is needed from customers.
Affected services