<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Yibnum</title>
    <description>The latest articles on DEV Community by Yibnum (@yibnum_e28bd788205e815a92).</description>
    <link>https://dev.to/yibnum_e28bd788205e815a92</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3619693%2F2d01560b-e7e8-4fce-ada0-bcf5eca955e0.jpg</url>
      <title>DEV Community: Yibnum</title>
      <link>https://dev.to/yibnum_e28bd788205e815a92</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yibnum_e28bd788205e815a92"/>
    <language>en</language>
    <item>
      <title>Cloudflare went down yesterday. My monitoring lied. So I built this.</title>
      <dc:creator>Yibnum</dc:creator>
      <pubDate>Wed, 19 Nov 2025 21:44:34 +0000</pubDate>
      <link>https://dev.to/yibnum_e28bd788205e815a92/cloudflare-went-down-yesterday-my-monitoring-lied-so-i-built-this-520o</link>
      <guid>https://dev.to/yibnum_e28bd788205e815a92/cloudflare-went-down-yesterday-my-monitoring-lied-so-i-built-this-520o</guid>
      <description>&lt;p&gt;Yesterday’s Cloudflare outage wasted a few hours of my time — not because the outage was confusing, but because my monitoring stack gave me zero context about what was actually failing.&lt;/p&gt;

&lt;p&gt;Everything lit up red. Every alert fired.&lt;br&gt;
But nothing told me whether the problem was:&lt;/p&gt;

&lt;p&gt;my origin&lt;/p&gt;

&lt;p&gt;Cloudflare’s edge&lt;/p&gt;

&lt;p&gt;DNS&lt;/p&gt;

&lt;p&gt;SSL&lt;/p&gt;

&lt;p&gt;routing&lt;/p&gt;

&lt;p&gt;My servers were completely fine the whole time.&lt;/p&gt;

&lt;p&gt;The real issue ended up being Cloudflare’s Bot Management system (a feature file doubled in size and tripped them up).&lt;/p&gt;

&lt;p&gt;The bigger discovery:&lt;br&gt;
most monitoring tools cannot tell the difference between an origin outage and a CDN/edge outage.&lt;/p&gt;

&lt;p&gt;So I built a simple tool today to diagnose exactly that:&lt;/p&gt;

&lt;p&gt;👉 &lt;a href="https://stayup.dev" rel="noopener noreferrer"&gt;https://stayup.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Paste a URL and it checks:&lt;/p&gt;

&lt;p&gt;origin health&lt;/p&gt;

&lt;p&gt;Cloudflare/Vercel/AWS edge&lt;/p&gt;

&lt;p&gt;DNS&lt;/p&gt;

&lt;p&gt;SSL expiry&lt;/p&gt;

&lt;p&gt;CDN failure patterns&lt;/p&gt;

&lt;p&gt;I built this out of frustration, but if you’re interested I’d love to hear how your monitoring handled the outage yesterday.&lt;/p&gt;

</description>
      <category>networking</category>
      <category>monitoring</category>
      <category>showdev</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
