Remote Config incident – intermittent latency

This issue has been resolved. Please reach out to our support team if you see this again. Thank you for your patience.

We have identified the cause of the issue and deployed a fix.

Since deploying the fix, the platform has remained 100% stable, and we are seeing dramatically improved performance.

We will continue monitoring the service closely for a week before closing this incident.

If you are experiencing any issue,s please contact Remote Config Support

The issue has resurfaced again, and engineers are actively working to get latency back under control.

Operational (monitoring) Earlier latency spikes have subsided and the service is currently operating normally. We’ve deployed mitigations and will continue monitoring. If fetch delays recur, please fall back to cached/local defaults and retry with backoff. We’ll post updates if conditions change.

We’ve deployed mitigations to reduce cache pressure and stabilize the service, and we’re working with our cloud provider on the underlying memory issue. Some latency spikes may still occur while we monitor. Please fall back to cached/local defaults and retry with backoff. We’ll share another update as status changes.

We’re seeing intermittent latency spikes (EU and some US), causing delayed or timed‑out fetches. Spikes typically resolve within 30–60 minutes. Please fall back to cached/local defaults and retry with backoff; avoid time‑sensitive rollouts for now. We’re scaling capacity and working with our provider—updates to follow.