<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><link rel="alternate" type="text/html" href="https://status.usefixie.com/"/><title>SOCKS Proxy Servers (EU) on Fixie Status</title><link>https://status.usefixie.com/affected/socks-proxy-servers-eu/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-02-16T23:48:00+00:00</lastBuildDate><updated>2026-02-16T23:48:00+00:00</updated><atom:link href="https://status.usefixie.com/affected/socks-proxy-servers-eu/index.xml" rel="self" type="application/rss+xml"/><item><title>[Resolved] Bici group degraded (EU SOCKS)</title><link>https://status.usefixie.com/issues/2026-02-16-bici-group-degraded-eu-socks/</link><pubDate>Mon, 16 Feb 2026 23:48:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2026-02-16-bici-group-degraded-eu-socks/</guid><category>2026-02-17 01:11:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. Root cause was an interaction between our load balancer and patch management system that caused hosts to restart and then be replaced.
&lt;span class="faded"&gt;(01:11 UTC — Feb 17)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The &lt;code&gt;bici&lt;/code&gt; proxy group in EU SOCKS is experiencing periodic spikes in latency and errors. We are investigating.
&lt;span class="faded"&gt;(23:48 UTC — Feb 16)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. Root cause was an interaction between our load balancer and patch management system that caused hosts to restart and then be replaced.
&lt;span class="faded"&gt;(01:11 UTC — Feb 17)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - The &lt;code&gt;bici&lt;/code&gt; proxy group in EU SOCKS is experiencing periodic spikes in latency and errors. We are investigating.
&lt;span class="faded"&gt;(23:48 UTC — Feb 16)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Errors reported in bici group (EU SOCKS)</title><link>https://status.usefixie.com/issues/2026-01-30-bici-group-errors-in-eu-socks/</link><pubDate>Fri, 30 Jan 2026 01:22:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2026-01-30-bici-group-errors-in-eu-socks/</guid><category>2026-01-30 01:28:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. Root cause was a routine update where new instances took longer than expected to become available. As a mitigation, we will be updating our deploy strategy to prevent this in the future.
&lt;span class="faded"&gt;(01:28 UTC — Jan 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Monitoring is reporting errors in the &lt;code&gt;bici&lt;/code&gt; proxy group in EU SOCKS. We are investigating the issue.
&lt;span class="faded"&gt;(01:22 UTC — Jan 30)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The issue has been resolved. Root cause was a routine update where new instances took longer than expected to become available. As a mitigation, we will be updating our deploy strategy to prevent this in the future.
&lt;span class="faded"&gt;(01:28 UTC — Jan 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - Monitoring is reporting errors in the &lt;code&gt;bici&lt;/code&gt; proxy group in EU SOCKS. We are investigating the issue.
&lt;span class="faded"&gt;(01:22 UTC — Jan 30)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] SOCKS proxy groups experiencing high latency</title><link>https://status.usefixie.com/issues/2026-01-25-socks-proxy-degradation/</link><pubDate>Mon, 26 Jan 2026 00:50:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2026-01-25-socks-proxy-degradation/</guid><category>2026-01-26 00:57:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - All SOCKS proxy groups have recovered.
&lt;span class="faded"&gt;(00:57 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - SOCKS proxy groups bici, century, and speedway are experiencing high latency due to a cascading failure from the previous database connectivity incident.
&lt;span class="faded"&gt;(00:50 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - All SOCKS proxy groups have recovered.
&lt;span class="faded"&gt;(00:57 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - SOCKS proxy groups bici, century, and speedway are experiencing high latency due to a cascading failure from the previous database connectivity incident.
&lt;span class="faded"&gt;(00:50 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] All proxy groups unavailable</title><link>https://status.usefixie.com/issues/2026-01-25-all-proxy-groups-unavailable/</link><pubDate>Mon, 26 Jan 2026 00:47:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2026-01-25-all-proxy-groups-unavailable/</guid><category>2026-01-26 00:50:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.
&lt;span class="faded"&gt;(00:50 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating reports that all proxy groups are unavailable.
&lt;span class="faded"&gt;(00:47 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.
&lt;span class="faded"&gt;(00:50 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating reports that all proxy groups are unavailable.
&lt;span class="faded"&gt;(00:47 UTC — Jan 26)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Some SOCKS proxies were unavailable in the EU region</title><link>https://status.usefixie.com/issues/2025-01-11-some-socks-proxies-were-unavailable-in-the-eu-regi/</link><pubDate>Fri, 10 Jan 2025 22:08:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-01-11-some-socks-proxies-were-unavailable-in-the-eu-regi/</guid><category>2025-01-11 01:21:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - From 10:08 PM Friday January 10th (UTC) to 1:21 AM Saturday January 11th (UTC), the bici proxy group was unavailable. This proxy group is a SOCKS proxy group in the EU Region.&lt;/p&gt;
&lt;p&gt;Fixie uses AWS DocumentDB for some state. AWS made an unannounced change to the cname through which instances in the EU region connect to their managed DocumentDB cluster. This meant that proxy servers that had sufficient available, existing connections in their connection pool were able to serve requests without issue, but proxy servers could not start cleanly.
&lt;span class="faded"&gt;(01:21 UTC — Jan 11)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - From 10:08 PM Friday January 10th (UTC) to 1:21 AM Saturday January 11th (UTC), the bici proxy group was unavailable. This proxy group is a SOCKS proxy group in the EU Region.&lt;/p&gt;
&lt;p&gt;Fixie uses AWS DocumentDB for some state. AWS made an unannounced change to the cname through which instances in the EU region connect to their managed DocumentDB cluster. This meant that proxy servers that had sufficient available, existing connections in their connection pool were able to serve requests without issue, but proxy servers could not start cleanly.
&lt;span class="faded"&gt;(01:21 UTC — Jan 11)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Network issues in EU Region</title><link>https://status.usefixie.com/issues/2020-03-15-network-issues-in-eu-region/</link><pubDate>Sun, 15 Mar 2020 15:33:55 +0000</pubDate><guid>https://status.usefixie.com/issues/2020-03-15-network-issues-in-eu-region/</guid><category>2020-03-15 15:34:31</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt;
&lt;span class="faded"&gt;(15:34 UTC — Mar 15)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.&lt;/p&gt;
&lt;p&gt;We believe this is a temporary network partition on the AWS side, and is now resolved.
&lt;span class="faded"&gt;(15:33 UTC — Mar 15)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt;
&lt;span class="faded"&gt;(15:34 UTC — Mar 15)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.&lt;/p&gt;
&lt;p&gt;We believe this is a temporary network partition on the AWS side, and is now resolved.
&lt;span class="faded"&gt;(15:33 UTC — Mar 15)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] All Fixie proxies degraded</title><link>https://status.usefixie.com/issues/2019-09-29-all-fixie-proxies-degraded/</link><pubDate>Sun, 29 Sep 2019 11:30:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2019-09-29-all-fixie-proxies-degraded/</guid><category>2019-09-29 14:30:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.
&lt;span class="faded"&gt;(14:30 UTC — Sep 29)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - 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.
&lt;span class="faded"&gt;(14:30 UTC — Sep 29)&lt;/span&gt;
&lt;/p&gt;</content></item></channel></rss>