<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Details of the 1.1.1.1 July 14th incident, with Dynatrace in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/Details-of-the-1-1-1-1-July-14th-incident-with-Dynatrace/m-p/282333#M6611</link>
    <description>&lt;P&gt;I use &lt;A href="https://en.wikipedia.org/wiki/1.1.1.1" target="_self"&gt;1.1.1.1&lt;/A&gt; as a DNS server a lot, both personally and professionally. Besides working well, it has some additional advantages, including privacy. Cloudflare, who operates 1.1.1.1, did a great blog post of what happened recently, in the &lt;A href="https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/" target="_self"&gt;July 14th incident&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Given that I depend a lot on it, I also monitor it. Since I use the Ping Every Second extension for it, I have a great view of what happened that day.&lt;/P&gt;
&lt;P&gt;First, availability: connectivity disappeared for me at 22:54:29 (all times are Portuguese time: UTC+1) and was back partially at 23:20:41. It wasn't until 23:42 that it totally recovered:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AntonioSousa_2-1753467491054.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29198i4C664D98E36EA710/image-size/large?v=v2&amp;amp;px=999" role="button" title="AntonioSousa_2-1753467491054.png" alt="AntonioSousa_2-1753467491054.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;But I also measure RTT every second.&amp;nbsp;RTT also fluctuated immediately before and after the total connectivity loss was observed, but I was expecting it to be higher than it was, especially with the max values after connectivity returned:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AntonioSousa_3-1753468070022.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29199iA6B60F416C07C15F/image-size/large?v=v2&amp;amp;px=999" role="button" title="AntonioSousa_3-1753468070022.png" alt="AntonioSousa_3-1753468070022.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;It is very satisfying that what I observed and what Cloudflare detailed in their Incident Timeline is almost a perfect match. But even more impressive is that I was able to get the details at a one second resolution with Dynatrace, and so have a perfect idea of what happened!&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jul 2025 06:40:40 GMT</pubDate>
    <dc:creator>AntonioSousa</dc:creator>
    <dc:date>2025-07-29T06:40:40Z</dc:date>
    <item>
      <title>Details of the 1.1.1.1 July 14th incident, with Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Extensions/Details-of-the-1-1-1-1-July-14th-incident-with-Dynatrace/m-p/282333#M6611</link>
      <description>&lt;P&gt;I use &lt;A href="https://en.wikipedia.org/wiki/1.1.1.1" target="_self"&gt;1.1.1.1&lt;/A&gt; as a DNS server a lot, both personally and professionally. Besides working well, it has some additional advantages, including privacy. Cloudflare, who operates 1.1.1.1, did a great blog post of what happened recently, in the &lt;A href="https://blog.cloudflare.com/cloudflare-1-1-1-1-incident-on-july-14-2025/" target="_self"&gt;July 14th incident&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Given that I depend a lot on it, I also monitor it. Since I use the Ping Every Second extension for it, I have a great view of what happened that day.&lt;/P&gt;
&lt;P&gt;First, availability: connectivity disappeared for me at 22:54:29 (all times are Portuguese time: UTC+1) and was back partially at 23:20:41. It wasn't until 23:42 that it totally recovered:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AntonioSousa_2-1753467491054.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29198i4C664D98E36EA710/image-size/large?v=v2&amp;amp;px=999" role="button" title="AntonioSousa_2-1753467491054.png" alt="AntonioSousa_2-1753467491054.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;But I also measure RTT every second.&amp;nbsp;RTT also fluctuated immediately before and after the total connectivity loss was observed, but I was expecting it to be higher than it was, especially with the max values after connectivity returned:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AntonioSousa_3-1753468070022.png" style="width: 999px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/29199iA6B60F416C07C15F/image-size/large?v=v2&amp;amp;px=999" role="button" title="AntonioSousa_3-1753468070022.png" alt="AntonioSousa_3-1753468070022.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;It is very satisfying that what I observed and what Cloudflare detailed in their Incident Timeline is almost a perfect match. But even more impressive is that I was able to get the details at a one second resolution with Dynatrace, and so have a perfect idea of what happened!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 06:40:40 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/Details-of-the-1-1-1-1-July-14th-incident-with-Dynatrace/m-p/282333#M6611</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2025-07-29T06:40:40Z</dc:date>
    </item>
  </channel>
</rss>

