HTTP Proxy Servers (EU) on Fixie Status

[Resolved] Elevated latency on Olympic proxy group

Thu, 12 Feb 2026 11:10:00 +0000

Resolved - Latency on the olympic proxy group has returned to normal levels. (15:00 UTC — Feb 12)

Investigating - We are investigating elevated latency on the olympic proxy group in EU HTTP. (11:10 UTC — Feb 12)

[Resolved] All proxy groups unavailable

Mon, 26 Jan 2026 00:47:00 +0000

Resolved - All proxy groups have been restored. The root cause was a bad infrastructure as code change that made our databases unreachable from our proxy groups. (00:50 UTC — Jan 26)

Investigating - We are investigating reports that all proxy groups are unavailable. (00:47 UTC — Jan 26)

[Resolved] Degradation in Olympic proxy group

Wed, 07 Jan 2026 16:43:23 +0000

Resolved - Issue been resolved (16:52 UTC — Jan 7)

Investigating - Only olympic proxy group is affected. All other proxy groups in EU function as expected (16:51 UTC — Jan 7)

Investigating - We are investigating issues with both proxy types in EU/US regions (16:43 UTC — Jan 7)

[Resolved] HTTP Proxies were degraded in the EU region

Mon, 12 Apr 2021 18:42:07 +0000

Resolved (18:44 UTC — Apr 12)

Resolved - HTTP proxies were degraded in the EU region this morning. The issue was resolved at 8:25am CST this morning.

We are improving alerting for EU-specific outages to improve our response in the future. (18:44 UTC — Apr 12)

Monitoring (18:42 UTC — Apr 12)

[Resolved] Network issues in EU Region

Sun, 15 Mar 2020 15:33:55 +0000

Resolved (15:34 UTC — Mar 15)

Resolved - Monitoring indicates that proxies in our EU region were unreachable from application hosts in US West. The proxies are healthy and are resolving without issue from US East.

We believe this is a temporary network partition on the AWS side, and is now resolved. (15:33 UTC — Mar 15)

[Resolved] All Fixie proxies degraded

Sun, 29 Sep 2019 11:30:00 +0000

Resolved - From approximately 11:30 UTC to 14:30 UTC, Fixie was degraded across all proxy groups. Response times spiked and a high number of requests timed out. The root cause was a load spike which, downstream, caused a spike in load to our database hosts, eventually causing them to run out of CPU credits. This is now resolved. (14:30 UTC — Sep 29)