<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>FUCKUP.fail</title>
    <link>https://fuckup.fail/</link>
    <description>Recent content on FUCKUP.fail</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 25 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://fuckup.fail/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>FUCKUP #001: The VM That Could Reach Everything Except Its Gateway</title>
      <link>https://fuckup.fail/cases/001-vm-can-reach-subnet-but-not-gateway/</link>
      <pubDate>Fri, 25 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://fuckup.fail/cases/001-vm-can-reach-subnet-but-not-gateway/</guid>
      <description>A Linux VM could reach other hosts on its subnet, but not the default gateway. Even packet captures seemed to contradict the symptoms.</description>
    </item>
    <item>
      <title>About FUCKUP.fail</title>
      <link>https://fuckup.fail/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://fuckup.fail/about/</guid>
      <description>&lt;h2 id=&#34;why-fuckup&#34;&gt;Why FUCKUP?&lt;/h2&gt;
&lt;p&gt;For most people, the name is self-explanatory.&lt;/p&gt;
&lt;p&gt;For those who know:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;First Universal Cybernetic-Kinetic Ultramicro Program.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;FUCKUP.fail collects real-world infrastructure failures, strange symptoms, diagnostic paths and the reasoning that leads to the root cause.&lt;/p&gt;
&lt;p&gt;The focus is not on memorizing commands.&lt;/p&gt;
&lt;p&gt;It is on answering the more useful question:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What should I test next — and what does the result actually tell me?&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
