<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Geo-Maps on Netdata</title><link>https://www.netdata.cloud/tags/geo-maps/</link><description>Recent content in Geo-Maps on Netdata</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.netdata.cloud/tags/geo-maps/index.xml" rel="self" type="application/rss+xml"/><item><title>Geo Maps: See Where Your Infrastructure Lives</title><link>https://www.netdata.cloud/blog/geo-maps/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://www.netdata.cloud/blog/geo-maps/</guid><description>&lt;p>When your infrastructure is spread across regions, data centers, branch offices, or edge locations, knowing where a node is physically located matters more than people usually admit. During an incident, &amp;ldquo;the node in the Singapore POP&amp;rdquo; communicates faster than a hostname. When you&amp;rsquo;re planning capacity, seeing geographic clustering tells you something that a flat list of nodes doesn&amp;rsquo;t. When a subset of your fleet starts misbehaving, the first question is often &amp;ldquo;is this regional?&amp;rdquo;&lt;/p></description></item></channel></rss>