Network Performance Issues in parts of Asia and Europe.
- Started
- 2026-04-20 17:00 UTC
- Resolved
- 2026-04-20 17:00 UTC
- Duration
- 0 minutes
- Date
- 2026-04-20
Incident Timeline
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.
Between approximately 18:00 UTC on April 20 and 07:35 UTC on April 22, a subset of users in parts of Asia and Europe experienced degraded performance when reaching Cloudflare's network. This was caused by a configuration issue in Singapore that resulted in suboptimal traffic routing. The issue has been identified and resolved.