<?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 (US) on Fixie Status</title><link>https://status.usefixie.com/affected/socks-proxy-servers-us/</link><description>Incident history</description><generator>github.com/cstate</generator><language>en</language><lastBuildDate>2026-01-26T00:50:00+00:00</lastBuildDate><updated>2026-01-26T00:50:00+00:00</updated><atom:link href="https://status.usefixie.com/affected/socks-proxy-servers-us/index.xml" rel="self" type="application/rss+xml"/><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] Major outage on Speedway group</title><link>https://status.usefixie.com/issues/2025-12-31-major-outage-on-speedway-group/</link><pubDate>Wed, 31 Dec 2025 09:54:46 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-12-31-major-outage-on-speedway-group/</guid><category>2025-12-31 10:28:44</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - This incident was resolved at 10:15 AM UTC after approximately 75 minutes of downtime.&lt;/p&gt;
&lt;p&gt;The root cause was a dependency update. We had rolled out incrementally for &amp;gt;6 hours without incident, but hit an edge case in error handling that resulted in an unhandled exception. We mitigated the issue with a forward fix and will review our policy for rolling out dependabot upgrades.
&lt;span class="faded"&gt;(10:28 UTC — Dec 31)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - We&amp;rsquo;ve fixed the issue and monitoring the system. The issue was related to an edge condition around latest dependency security update that didn&amp;rsquo;t surface during the daytime testing and monitoring.
&lt;span class="faded"&gt;(10:19 UTC — Dec 31)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - This incident was resolved at 10:15 AM UTC after approximately 75 minutes of downtime.&lt;/p&gt;
&lt;p&gt;The root cause was a dependency update. We had rolled out incrementally for &amp;gt;6 hours without incident, but hit an edge case in error handling that resulted in an unhandled exception. We mitigated the issue with a forward fix and will review our policy for rolling out dependabot upgrades.
&lt;span class="faded"&gt;(10:28 UTC — Dec 31)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - We&amp;rsquo;ve fixed the issue and monitoring the system. The issue was related to an edge condition around latest dependency security update that didn&amp;rsquo;t surface during the daytime testing and monitoring.
&lt;span class="faded"&gt;(10:19 UTC — Dec 31)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating an outage
&lt;span class="faded"&gt;(09:54 UTC — Dec 31)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Elevated latency in Speedway group</title><link>https://status.usefixie.com/issues/2025-12-30-elevated-latency-in-speedway-group/</link><pubDate>Tue, 30 Dec 2025 05:24:07 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-12-30-elevated-latency-in-speedway-group/</guid><category>2025-12-30 05:28:50</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The service is fully restored and we will continue monitoring the proxy group
&lt;span class="faded"&gt;(05:28 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Speedway group had intermittent (short) failures throughout the day. We&amp;rsquo;ve identified the issue and in the process of testing monitoring and fixes.
&lt;span class="faded"&gt;(05:26 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Speedway group had intermittent (short) failures throughout the day. We&amp;rsquo;ve identified the issue and in the process of testing monitoring and fixes.
&lt;span class="faded"&gt;(05:24 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The service is fully restored and we will continue monitoring the proxy group
&lt;span class="faded"&gt;(05:28 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Speedway group had intermittent (short) failures throughout the day. We&amp;rsquo;ve identified the issue and in the process of testing monitoring and fixes.
&lt;span class="faded"&gt;(05:26 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Monitoring&lt;/em&gt; - Speedway group had intermittent (short) failures throughout the day. We&amp;rsquo;ve identified the issue and in the process of testing monitoring and fixes.
&lt;span class="faded"&gt;(05:24 UTC — Dec 30)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Elevated latency in Speedway group</title><link>https://status.usefixie.com/issues/2025-12-12-elevated-latency-in-speedway-group/</link><pubDate>Fri, 12 Dec 2025 17:18:10 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-12-12-elevated-latency-in-speedway-group/</guid><category>2025-12-12 17:25:51</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Outage was resolved by scaling this group vertically
&lt;span class="faded"&gt;(17:25 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt;
&lt;span class="faded"&gt;(17:18 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating degraded performance in the Speedway socks proxy group
&lt;span class="faded"&gt;(17:18 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Outage was resolved by scaling this group vertically
&lt;span class="faded"&gt;(17:25 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt;
&lt;span class="faded"&gt;(17:18 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt; - We are investigating degraded performance in the Speedway socks proxy group
&lt;span class="faded"&gt;(17:18 UTC — Dec 12)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Elevated latency in the Speedway group</title><link>https://status.usefixie.com/issues/2025-04-01-elevated-latency-in-the-speedway-group-from-1057am/</link><pubDate>Tue, 01 Apr 2025 14:57:00 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-04-01-elevated-latency-in-the-speedway-group-from-1057am/</guid><category>2025-04-01 16:38:00</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The Speedway socks proxy experienced a protracted period of elevated latency on one of its two nodes, causing high latency on ~50% of requests for 90 minutes. This was resolved by scaling vertically.
&lt;span class="faded"&gt;(16:38 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - The Speedway socks proxy experienced a protracted period of elevated latency on one of its two nodes, causing high latency on ~50% of requests for 90 minutes. This was resolved by scaling vertically.
&lt;span class="faded"&gt;(16:38 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;</content></item><item><title>[Resolved] Elevated latency in Speedway proxy group</title><link>https://status.usefixie.com/issues/2025-04-01-elevated-latency-in-speedway-proxy-group/</link><pubDate>Tue, 01 Apr 2025 02:28:40 +0000</pubDate><guid>https://status.usefixie.com/issues/2025-04-01-elevated-latency-in-speedway-proxy-group/</guid><category>2025-04-01 02:42:21</category><description>&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Fleet update completed and response times have recovered. We will continue to monitor.
&lt;span class="faded"&gt;(02:42 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - Latency was caused by a significant load spike. We are mitigating the issue by scaling this cluster vertically. Half of the fleet has updated and we are seeing response times recover.
&lt;span class="faded"&gt;(02:39 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt;
&lt;span class="faded"&gt;(02:28 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;</description><content type="html">&lt;p&gt;&lt;em&gt;Resolved&lt;/em&gt; - Fleet update completed and response times have recovered. We will continue to monitor.
&lt;span class="faded"&gt;(02:42 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Identified&lt;/em&gt; - Latency was caused by a significant load spike. We are mitigating the issue by scaling this cluster vertically. Half of the fleet has updated and we are seeing response times recover.
&lt;span class="faded"&gt;(02:39 UTC — Apr 1)&lt;/span&gt;
&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Investigating&lt;/em&gt;
&lt;span class="faded"&gt;(02:28 UTC — Apr 1)&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>