<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-04-18T05:36:02Z</updated>
  <generator>https://yabu.me</generator>

  <title>Nostr notes by Matt Nordhoff</title>
  <author>
    <name>Matt Nordhoff</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://yabu.me/npub185ceaey2s0sv2luquzxnsw4c0cthnfk2h7ju5qlu9h93j5gltulstmjnwf.rss" />
  <link href="https://yabu.me/npub185ceaey2s0sv2luquzxnsw4c0cthnfk2h7ju5qlu9h93j5gltulstmjnwf" />
  <id>https://yabu.me/npub185ceaey2s0sv2luquzxnsw4c0cthnfk2h7ju5qlu9h93j5gltulstmjnwf</id>
  <icon></icon>
  <logo></logo>




  <entry>
    <id>https://yabu.me/nevent1qqsw9ft388tudcxaqzdggvp3xl30upuveay96wc5xq8d39x7dfd0wnszyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n787t6up</id>
    
      <title type="html">Luckily for some, AWS&amp;#39;s public SLAs have an &amp;#34;SLA ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsw9ft388tudcxaqzdggvp3xl30upuveay96wc5xq8d39x7dfd0wnszyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n787t6up" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqswram8fq8z7aqrawtelv2hmtxdztjcypx53u8kx7n35n39tfkm2msxwm7dh&#39;&gt;nevent1q…m7dh&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Luckily for some, AWS&amp;#39;s public SLAs have an &amp;#34;SLA Exclusions&amp;#34; section that says you can get lost in case of force majeure! I guess they can skip the refunds and everyone can proceed straight to the lawsuits.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://aws.amazon.com/s3/sla/&#34;&gt;https://aws.amazon.com/s3/sla/&lt;/a&gt;&lt;br/&gt;&lt;a href=&#34;https://aws.amazon.com/compute/sla/&#34;&gt;https://aws.amazon.com/compute/sla/&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;I wonder what local laws say or what kinda contracts their large/government clients get.
    </content>
    <updated>2026-03-03T01:47:34Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqs254020y7eqxepnhyj8gtk836wm3kp7sjc7pn9uxfffhfvjs4gj0szyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n73ut6tz</id>
    
      <title type="html">Lengthy update on https://health.aws.amazon.com/health/status ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqs254020y7eqxepnhyj8gtk836wm3kp7sjc7pn9uxfffhfvjs4gj0szyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n73ut6tz" />
    <content type="html">
      Lengthy update on &lt;a href=&#34;https://health.aws.amazon.com/health/status&#34;&gt;https://health.aws.amazon.com/health/status&lt;/a&gt; earlier:&lt;br/&gt;&lt;br/&gt;&amp;gt; **Mar 02 4:19 PM PST**&amp;gt;  We are providing an update on the ongoing service disruptions affecting the AWS Middle East (UAE) Region (ME-CENTRAL-1) and the AWS Middle East (Bahrain) Region (ME-SOUTH-1). Due to the ongoing conflict in the Middle East, both affected regions have experienced physical impacts to infrastructure as a result of drone strikes. In the UAE, two of our facilities were directly struck, while in Bahrain, a drone strike in close proximity to one of our facilities caused physical impacts to our infrastructure. These strikes have caused structural damage, disrupted power delivery to our infrastructure, and in some cases required fire suppression activities that resulted in additional water damage. We are working closely with local authorities and prioritizing the safety of our personnel throughout our recovery efforts.&lt;br/&gt;&lt;br/&gt;&amp;gt; In the ME-CENTRAL-1 (UAE) Region, two of our three Availability Zones (mec1-az2 and mec1-az3) remain significantly impaired. The third Availability Zone (mec1-az1) continues to operate normally, though some services have experienced indirect impact due to dependencies on the affected zones. In the ME-SOUTH-1 (Bahrain) Region, one facility has been impacted. Across both regions, customers are experiencing elevated error rates and degraded availability for services including Amazon EC2, Amazon S3, Amazon DynamoDB, AWS Lambda, Amazon Kinesis, Amazon CloudWatch, Amazon RDS, and the AWS Management Console and CLI. We are working to restore full service availability as quickly as possible, though we expect recovery to be prolonged given the nature of the physical damage involved.&lt;br/&gt;&lt;br/&gt;&amp;gt; …
    </content>
    <updated>2026-03-03T01:15:05Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsy5wu6u808lgxjevnldupqgx9qv4xq28qhhulelec5aa5f2r9j2rszyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n77ecst4</id>
    
      <title type="html">RE: https://infosec.exchange/@mnordhoff/116160410647779449 Based ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsy5wu6u808lgxjevnldupqgx9qv4xq28qhhulelec5aa5f2r9j2rszyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n77ecst4" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsfhzx6pw07h9t6qfux28yndetr5ds5vqgahezrunuh9a2u22znl6gxj5rz7&#39;&gt;nevent1q…5rz7&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;RE: &lt;a href=&#34;https://infosec.exchange/@mnordhoff/116160410647779449&#34;&gt;https://infosec.exchange/@mnordhoff/116160410647779449&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Based on its unique architecture, Amazon S3 is designed to exceed 99.999999999% data durability.&lt;br/&gt;&lt;br/&gt;The S3 Standard storage class offers a 99.9% availability SLA and is designed for 99.99% availability.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://aws.amazon.com/s3/storage-classes/&#34;&gt;https://aws.amazon.com/s3/storage-classes/&lt;/a&gt;&lt;blockquote class=&#34;border-l-05rem border-l-strongpink border-solid&#34;&gt;&lt;div class=&#34;-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2&#34;&gt;quoting &lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Article&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/note1nwyd5zulaw2h5qncv5wfxmjk8gmpgcq3m0jy8e8ewt64c5598l5s8z82q2&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;note1nwy…82q2&lt;/a&gt;&lt;/span&gt;&lt;br/&gt; &lt;/div&gt; I missed this yesterday, but AWS Middle East (UAE) (me-central-1) has been having issues due to the war.&lt;br/&gt;&lt;br/&gt;&#34;At around 4:30 AM PST [2026-03-01], one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire department shut off power to the facility and generators as they worked to put out the fire.&#34;&lt;br/&gt;&lt;br/&gt;&#34;**Mar 01 10:46 PM PST** We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3).&#34;&lt;br/&gt;&lt;br/&gt;This might be the first time AWS has ever had separate, serious outages affecting multiple AZs simultaneously, if you exclude the many many outages where a region-level service like S3 goes down due to a software issue.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://health.aws.amazon.com/health/status&#34;&gt;https://health.aws.amazon.com/health/status&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Edit: I didn&#39;t scroll down! Middle East (Bahrain) also has an affected AZ.&lt;br/&gt;&lt;br/&gt;&#34;**Mar 01 11:09 PM PST** We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue.&#34; &lt;/blockquote&gt;
    </content>
    <updated>2026-03-02T23:23:38Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsfhzx6pw07h9t6qfux28yndetr5ds5vqgahezrunuh9a2u22znl6gzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7wantdr</id>
    
      <title type="html">I missed this yesterday, but AWS Middle East (UAE) (me-central-1) ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsfhzx6pw07h9t6qfux28yndetr5ds5vqgahezrunuh9a2u22znl6gzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7wantdr" />
    <content type="html">
      I missed this yesterday, but AWS Middle East (UAE) (me-central-1) has been having issues due to the war.&lt;br/&gt;&lt;br/&gt;&amp;#34;At around 4:30 AM PST [2026-03-01], one of our Availability Zones (mec1-az2) was impacted by objects that struck the data center, creating sparks and fire. The fire department shut off power to the facility and generators as they worked to put out the fire.&amp;#34;&lt;br/&gt;&lt;br/&gt;&amp;#34;**Mar 01 10:46 PM PST** We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3).&amp;#34;&lt;br/&gt;&lt;br/&gt;This might be the first time AWS has ever had separate, serious outages affecting multiple AZs simultaneously, if you exclude the many many outages where a region-level service like S3 goes down due to a software issue.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://health.aws.amazon.com/health/status&#34;&gt;https://health.aws.amazon.com/health/status&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;Edit: I didn&amp;#39;t scroll down! Middle East (Bahrain) also has an affected AZ.&lt;br/&gt;&lt;br/&gt;&amp;#34;**Mar 01 11:09 PM PST** We are investigating connectivity and power issues affecting APIs and instances in a single Availability Zone (mes1-az2) in the ME-SOUTH-1 Region due to a localized power issue.&amp;#34;
    </content>
    <updated>2026-03-02T16:00:03Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsd2kz9eh6rql5qkwqt4zu2zz8sky3pfe8vrdyfjd05gdg42ftnzegzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n75lv4v7</id>
    
      <title type="html">RE: https://infosec.exchange/@mnordhoff/115675202677067879 ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsd2kz9eh6rql5qkwqt4zu2zz8sky3pfe8vrdyfjd05gdg42ftnzegzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n75lv4v7" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs9tt2auqsud22sjpe8zkxmhvf2q53s6ahn82p2r9kne9vyp47cmjqq5842n&#39;&gt;nevent1q…842n&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;RE: &lt;a href=&#34;https://infosec.exchange/@mnordhoff/115675202677067879&#34;&gt;https://infosec.exchange/@mnordhoff/115675202677067879&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://groups.google.com/a/list.nist.gov/g/internet-time-service/c/Zd7VaR-vqV4&#34;&gt;https://groups.google.com/a/list.nist.gov/g/internet-time-service/c/Zd7VaR-vqV4&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;&amp;gt; On Saturday, 6 December 2025 at approximately 21:13 UTC, the atomic time source (a single cesium beam atomic clock) for all the internet time servers at the NIST Gaithersburg campus failed and exhibited a time step of approximately -10 ms.&lt;br/&gt;&lt;br/&gt;Oh.&lt;blockquote class=&#34;border-l-05rem border-l-strongpink border-solid&#34;&gt;&lt;div class=&#34;-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2&#34;&gt;quoting &lt;br/&gt;&lt;span itemprop=&#34;mentions&#34; itemscope itemtype=&#34;https://schema.org/Article&#34;&gt;&lt;a itemprop=&#34;url&#34; href=&#34;/note12kk4mcppc654pyrjw9vdhwcj5pfrp4m0xw5z5xtd8j2cgrta3hyqnuljut&#34; class=&#34;bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1&#34;&gt;note12kk…ljut&lt;/a&gt;&lt;/span&gt;&lt;br/&gt; &lt;/div&gt; time.cloudflare.com suddenly 5-10 ms off the real time in the eastern US.&lt;br/&gt;&lt;br/&gt;I&#39;d guess probably something boring, like network asymmetry near the top of the tree (bottom of the tree?).&lt;br/&gt;&lt;br/&gt;(When the service was new, the accuracy was routinely worse than this.) &lt;/blockquote&gt;
    </content>
    <updated>2025-12-09T11:11:11Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqs9tt2auqsud22sjpe8zkxmhvf2q53s6ahn82p2r9kne9vyp47cmjqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n792t46r</id>
    
      <title type="html">time.cloudflare.com suddenly 5-10 ms off the real time in the ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqs9tt2auqsud22sjpe8zkxmhvf2q53s6ahn82p2r9kne9vyp47cmjqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n792t46r" />
    <content type="html">
      time.cloudflare.com suddenly 5-10 ms off the real time in the eastern US.&lt;br/&gt;&lt;br/&gt;I&amp;#39;d guess probably something boring, like network asymmetry near the top of the tree (bottom of the tree?).&lt;br/&gt;&lt;br/&gt;(When the service was new, the accuracy was routinely worse than this.)
    </content>
    <updated>2025-12-06T23:25:17Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsy4ehajmf8sdeu4yp7hqkrztc389u6kt84y70sf76wdjth8wpd45qzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7kztysv</id>
    
      <title type="html">Cloudflare will also turn off Cloudflare&amp;#39;s security features ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsy4ehajmf8sdeu4yp7hqkrztc389u6kt84y70sf76wdjth8wpd45qzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7kztysv" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs2plqr5ucw7rvy6eq052263xl32u24u3r5yznzysc93wxxjfkzx0qs45dd7&#39;&gt;nevent1q…5dd7&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Cloudflare will also turn off Cloudflare&amp;#39;s security features if Cloudflare is down!&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://blog.cloudflare.com/details-of-the-cloudflare-outage-on-july-2-2019/&#34;&gt;https://blog.cloudflare.com/details-of-the-cloudflare-outage-on-july-2-2019/&lt;/a&gt;
    </content>
    <updated>2025-11-18T17:22:06Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsqakjszq579f3ntkx73vq93n2wf5wayxa80nthaqu56yfu62cg0nqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n78savdj</id>
    
      <title type="html">Almost all of the gTLD registry backend operators, and some ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsqakjszq579f3ntkx73vq93n2wf5wayxa80nthaqu56yfu62cg0nqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n78savdj" />
    <content type="html">
      Almost all of the gTLD registry backend operators, and some ccTLDs, love moving infrastructure to AWS.&lt;br/&gt;&lt;br/&gt;I wonder if there will ever be any negative consequences to this, beyond the financial ones.&lt;br/&gt;&lt;br/&gt;:pika:
    </content>
    <updated>2025-08-17T20:16:16Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqs0nc3xj2ajn9ut6dglrlx68tm2q2ljjv4amumd5zgqcp28kxvsevczyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7r34fv7</id>
    
      <title type="html">I&amp;#39;m not sure. I think Ubuntu generated/generates their own, ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqs0nc3xj2ajn9ut6dglrlx68tm2q2ljjv4amumd5zgqcp28kxvsevczyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7r34fv7" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsy0c2fvu82a7xcnzw0tpj537sxc3w6f93c8g0h0f95sgaqv0fmdfg6c0jxh&#39;&gt;nevent1q…0jxh&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;I&amp;#39;m not sure. I think Ubuntu generated/generates their own, but my memory could be playing tricks on me.
    </content>
    <updated>2025-03-03T02:00:58Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsxhd6j20mxtrxtenm2k383v8eqx689ucr3w4huzjwr50s9nt3vj8czyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7nx7c2y</id>
    
      <title type="html">I liked how old versions of Ubuntu shipped tons of small ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsxhd6j20mxtrxtenm2k383v8eqx689ucr3w4huzjwr50s9nt3vj8czyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7nx7c2y" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs0hel0576jnydf04g3tukjwyd756rxm33xlj0dedmu5vu7g7uyhrqktx5nz&#39;&gt;nevent1q…x5nz&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;I liked how old versions of Ubuntu shipped tons of small parameters, about a dozen 6144-bit ones (dated 2004), and three 8192-bit ones (dated 2006). Obviously someone at OpenSSH/Debian/Ubuntu got tired of waiting and hit ^C.&lt;br/&gt;&lt;br/&gt;(Now they have dozens of each, dated more recently.)
    </content>
    <updated>2025-03-02T22:41:26Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsya0pu8td5x54t896dzf6r7ln2lyhergt6pm2ml5xn37knnxvtngqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7mfzqn7</id>
    
      <title type="html">So, yesterday&amp;#39;s thing was, DigiCert is dumping IPv6 support ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsya0pu8td5x54t896dzf6r7ln2lyhergt6pm2ml5xn37knnxvtngqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7mfzqn7" />
    <content type="html">
      So, yesterday&amp;#39;s thing was, DigiCert is dumping IPv6 support after their current CDN, Edgio, went bankrupt.&lt;br/&gt;&lt;br/&gt;(2 longstanding companies merged and rebranded onto a colonial .io domain and filed for bankruptcy 2 years later, eh?)&lt;br/&gt;&lt;br/&gt;But DigiCert also recently acquired the oft-DDoSed DNS service UltraDNS (to go with the other DNS service they acquired before), which uses Edgio for DDoS protection!&lt;br/&gt;&lt;br/&gt;(traceroute an UltraDNS nameserver like pdns196.ultradns.com or b.cctld.us, you may see AS22822/llnw.net near the destination.)&lt;br/&gt;&lt;br/&gt;Wonder how that&amp;#39;s gonna go.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://social.elizabeth.cat/notes/a2m7w4bjk1e3newm&#34;&gt;https://social.elizabeth.cat/notes/a2m7w4bjk1e3newm&lt;/a&gt;
    </content>
    <updated>2025-01-05T13:56:46Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsxralmluzu6vl4xqw8qzjrka28f0hynxdq5m3k7yuddyuv4zw485czyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7atfj9c</id>
    
      <title type="html">The .fun TLD has been a bit broken for a month now. 👍 ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsxralmluzu6vl4xqw8qzjrka28f0hynxdq5m3k7yuddyuv4zw485czyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7atfj9c" />
    <content type="html">
      The .fun TLD has been a bit broken for a month now. 👍&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://dnsviz.net/d/fun/ZzsFkg/dnssec/&#34;&gt;https://dnsviz.net/d/fun/ZzsFkg/dnssec/&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;They use a secondary DNS service -- but don&amp;#39;t list it in the root zone, so it doesn&amp;#39;t really make the TLD more reliable -- and it stopped updating the zone around 2024-10-18 for some reason.&lt;br/&gt;&lt;br/&gt;And the three companies involved have yet to fix it for some reason.&lt;br/&gt;&lt;br/&gt;So under certain circumstances a small percentage of DNS queries for .fun domains just randomly fail. 🤷
    </content>
    <updated>2024-11-18T09:28:57Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsq8nxqsdhjxgxassc096uy68xv8xs6m77rf272dcx7u2xu6n0r4yqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n79rhz82</id>
    
      <title>Nostr event nevent1qqsq8nxqsdhjxgxassc096uy68xv8xs6m77rf272dcx7u2xu6n0r4yqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n79rhz82</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsq8nxqsdhjxgxassc096uy68xv8xs6m77rf272dcx7u2xu6n0r4yqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n79rhz82" />
    <content type="html">
      &lt;a href=&#34;https://vercara.com/news/digicert-completes-acquisition-of-vercara&#34;&gt;https://vercara.com/news/digicert-completes-acquisition-of-vercara&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;!?!?!? First DigiCert acquired DNS Made Easy/Constellix, now they acquired Vercara (UltraDNS).&lt;br/&gt;&lt;br/&gt;Real loss for competition in the US enterprise DNS market. Now it&amp;#39;s just like NS1 (acquired by IBM instead), Akamai, *sigh* Cloudflare, and non-traditional services like Amazon.&lt;br/&gt;&lt;br/&gt;(Defining a &amp;#34;traditional&amp;#34; DNS service as roughly one that supports zone transfers, arbitrary record types and static DNSSEC.)&lt;br/&gt;&lt;br/&gt;(Meanwhile I continue to lament the non-enterprise-budget personal or small business DNS market.)
    </content>
    <updated>2024-09-25T09:47:57Z</updated>
  </entry>

  <entry>
    <id>https://yabu.me/nevent1qqsrruljszgm3x6ht59cm0m6wktcvtnyl5hlh7uk0xwksxpz92mgvtqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7ws8wee</id>
    
      <title type="html">Popular controversial hosting company Cloudflare has been ...</title>
    
    <link rel="alternate" href="https://yabu.me/nevent1qqsrruljszgm3x6ht59cm0m6wktcvtnyl5hlh7uk0xwksxpz92mgvtqzyq7nr8hy32p7p3tlsrsg6wp6hplpw7dxe2l6tjsrlskukx23ra0n7ws8wee" />
    <content type="html">
      Popular controversial hosting company Cloudflare has been reenabling Encrypted Client Hello (ECH) recently. They had announced it with [fanfare](&lt;a href=&#34;https://blog.cloudflare.com/announcing-encrypted-client-hello/&#34;&gt;https://blog.cloudflare.com/announcing-encrypted-client-hello/&lt;/a&gt; ) and then disabled it again with [less fanfare](&lt;a href=&#34;https://community.cloudflare.com/t/early-hints-and-encrypted-client-hello-ech-are-currently-disabled-globally/567730&#34;&gt;https://community.cloudflare.com/t/early-hints-and-encrypted-client-hello-ech-are-currently-disabled-globally/567730&lt;/a&gt; ).&lt;br/&gt;&lt;br/&gt;Almost all of the popular domains with it enabled look NSFW. :blobshrug:&amp;lt;code&amp;gt;$ dig &#43;short openstreetmap.org https&amp;lt;br&amp;gt;1 . alpn=&amp;#34;h3,h2&amp;#34; ipv4hint=104.21.88.66,172.67.173.161 ech=AEX&#43;DQBBswAgACCY/JoV&#43;3cuHZdOgYzHZ0SP9Ms&#43;TN3PN8D8vk10GJU/AgAEAAEAAQASY2xvdWRmbGFyZS1lY2guY29tAAA= ipv6hint=2606:4700:3030::ac43:ada1,2606:4700:3034::6815:5842&amp;lt;br&amp;gt;&amp;lt;/code&amp;gt;&lt;br/&gt;&lt;br/&gt;(That domain is not NSFW. Probably.)&lt;br/&gt;&lt;br/&gt;Apparently [someone noticed and Cloudflare confirmed it](&lt;a href=&#34;https://community.cloudflare.com/t/encrypted-client-hello-ech-are-being-enabled-again/700863&#34;&gt;https://community.cloudflare.com/t/encrypted-client-hello-ech-are-being-enabled-again/700863&lt;/a&gt; ) 3 weeks ago.
    </content>
    <updated>2024-09-11T15:11:33Z</updated>
  </entry>

</feed>