
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>AzureFixes</title>
      <link>https://Azurefixes.com/blog</link>
      <description>This blog is for Azure Troubleshooting</description>
      <language>en-us</language>
      <managingEditor>address@yoursite.com (NVN)</managingEditor>
      <webMaster>address@yoursite.com (NVN)</webMaster>
      <lastBuildDate>Mon, 29 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://Azurefixes.com/tags/bgp/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://Azurefixes.com/blog/azure-vng-cpu-spikes</guid>
    <title>Fixing Azure VPN Gateway CPU Spikes: A Route Explosion RCA</title>
    <link>https://Azurefixes.com/blog/azure-vng-cpu-spikes</link>
    <description>A production incident walkthrough: VPN Gateway CPU pegged at 95% across both active-active instances, causing BGP flaps and tunnel instability. Root cause was 2,400 BGP prefixes with no summarization. Fix: route summarization + SKU upgrade brought CPU to 38%.</description>
    <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (NVN)</author>
    <category>Azure</category><category>VPN Gateway</category><category>BGP</category><category>Networking</category><category>Troubleshooting</category><category>ExpressRoute</category>
  </item>

    </channel>
  </rss>
