<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Thalamus</title><link>https://blog.thalamus.am/tag/networking/</link><description>Recent content in Networking on Thalamus</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Thalamus TM</copyright><lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.thalamus.am/tag/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>The 200 that nobody received</title><link>https://blog.thalamus.am/posts/the-200-that-nobody-received/</link><pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate><guid>https://blog.thalamus.am/posts/the-200-that-nobody-received/</guid><description>&lt;img src="https://blog.thalamus.am/posts/the-200-that-nobody-received/editorial-cover.png" alt="Featured image of post The 200 that nobody received" /&gt;&lt;p&gt;Clients of &lt;code&gt;api.thalamus.am&lt;/code&gt; were occasionally timing out. The gateway access log showed successful requests.&lt;/p&gt;
&lt;p&gt;The request had arrived. The upstream had answered. The log recorded a 200. There was no obvious pattern by endpoint or time of day, and the failures were rare enough to disappear into otherwise healthy dashboards.&lt;/p&gt;
&lt;p&gt;I spent too long looking for an application error. The useful question turned out to be: which machines did the connection depend on after the application had done its work?&lt;/p&gt;</description></item></channel></rss>