<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Bluesky is down today.]]></title><description><![CDATA[<p>Bluesky is down today. "Hah", I think, "since I use a self-hosted PDS for posting and Blacksky for viewing posts, I can go on using the service just fine".</p><p>Blacksky can't show me my own posts. I can make them and they show up on my PDS, but my profile shows none more recent than last night.</p><p>I wonder if Blacksky is coincidentally having server problems, or if Blacksky has a still-undisclosed dependency on Bluesky services. (It *does* have disclosed use of Bluesky moderation; maybe that's it.)</p>]]></description><link>https://board.circlewithadot.net/topic/ec2f0b10-2f53-444a-879b-854064ba3acf/bluesky-is-down-today.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 01 May 2026 05:25:37 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/ec2f0b10-2f53-444a-879b-854064ba3acf.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 16 Apr 2026 18:34:30 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:24:04 GMT]]></title><description><![CDATA[<p><span><a href="https://mastodon.social/@mcc" rel="nofollow noopener noreferrer">@<span>mcc</span></a></span> the worst are distributed p2p attacks like i watch in ipfs.</p>]]></description><link>https://board.circlewithadot.net/post/https://social.manalejandro.com/@ale@social.manalejandro.com/posts/567701750042044264/</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://social.manalejandro.com/@ale@social.manalejandro.com/posts/567701750042044264/</guid><dc:creator><![CDATA[ale@social.manalejandro.com]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:24:04 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:23:48 GMT]]></title><description><![CDATA[<p><span><a href="/user/aeris%40firefish.imirhil.fr">@<span>aeris</span></a></span> <span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> and yet, despite the 43 min latency you’re reporting, we’ve been having a perfectly synchronous conversation for the last 15 minutes.</p>]]></description><link>https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416251715910565</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416251715910565</guid><dc:creator><![CDATA[jeromechoo@masto.ai]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:23:48 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:23:32 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> And my new instance (migrating from Mastodon to Misskey exactly for this reason) is <b>ALREADY</b> filled with 600 dangling requests. At this point it doesn't generate any noticable delay, but only because the overall death rate is low. If a huge instance goes down, it would not be the same at all.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hqyi4ngsq0094</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hqyi4ngsq0094</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:23:32 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:22:06 GMT]]></title><description><![CDATA[<p><a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> <a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> No, it not running fine. I <b>ALREADY</b> reported 43 minutes latency to deliver <b>ANY MESSAGE</b><span> on Mastodon. This "bug" (in fact bad design) is known since ages.<br /></span><a href="https://github.com/mastodon/mastodon/issues/12445">https://github.com/mastodon/mastodon/issues/12445</a></p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hp4dkngsq0093</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hp4dkngsq0093</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:22:06 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:21:12 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> At the end any workers just have 7% of "luck" (3 out of 42) to hit a down request, consuming resource for nothing for 2-3s, having no more time to schedule alive server, with 13.000 pending request because starvation, with many many alive request in those 13.000. Perhaps the 13.000th will be a alive one, but it will be delivered in only 43 minutes in average.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hnykbngsq0092</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hnykbngsq0092</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:21:12 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:21:05 GMT]]></title><description><![CDATA[<p><span><a href="/user/aeris%40firefish.imirhil.fr">@<span>aeris</span></a></span> <span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> like I have already said — every post you’ve made just now has failed to deliver to several instances. Your instance is running just fine is it not?</p><p>If mastodon.social goes down. It would add ONE more failed delivery to the queue of thousands your instance is already managing.</p>]]></description><link>https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416241059902094</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416241059902094</guid><dc:creator><![CDATA[jeromechoo@masto.ai]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:21:05 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:20:29 GMT]]></title><description><![CDATA[<p><span><a href="/user/nasser%40merveilles.town">@<span>nasser</span></a></span> <span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> Thanks indeed! This is a great explanation.</p><p>My own takeaway is that Bluesky is a lost cause in terms of decentralization, because its architecture is designed to resist that outcome.</p>]]></description><link>https://board.circlewithadot.net/post/https://chaos.social/users/slothrop/statuses/116416238663415267</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://chaos.social/users/slothrop/statuses/116416238663415267</guid><dc:creator><![CDATA[slothrop@chaos.social]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:20:29 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:18:28 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/aeris%40firefish.imirhil.fr">@aeris@firefish.imirhil.fr</a> if that's really the case, if anything, that's an implementation problem. Mail servers have dealt with this problem for ages. That's why they have queues and per server exponentially increasing retry intervals. Push is not inherently bad.</p>]]></description><link>https://board.circlewithadot.net/post/https://federation.network/notes/al5hkfupj44600oj</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://federation.network/notes/al5hkfupj44600oj</guid><dc:creator><![CDATA[scatty_hannah@federation.network]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:18:28 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:18:07 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> After a while, you have 43 minutes latency for <b>EVERY DELIVERY</b>, even alive server. I experience that on my own Mastodon instance…</p>

<div class="row mt-3"><div class="col-12 mt-3"><img class="img-thumbnail" src="https://s3.imirhil.fr/firefish//f3393ea5-4b62-41a6-8bca-88bc54c76752.webp" alt="Link Preview Image" /></div></div>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hk0c9ngsq0091</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hk0c9ngsq0091</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:18:07 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:17:38 GMT]]></title><description><![CDATA[<p><span><a href="/user/breizh%40pleroma.breizh.pm">@<span>breizh</span></a></span> As of this second, Blacksky has resolved the issue. I don't know how.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416227484312180</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416227484312180</guid><dc:creator><![CDATA[mcc@mastodon.social]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:17:38 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:16:48 GMT]]></title><description><![CDATA[<p>Updates</p><p>- Over the last two hours the problem has gone from "I don't see my posts" to "I see my posts 1 hour after I make them" to "17 minutes" to "3 minutes" to "it's fixed". I interpret this as the relay firehose pointer, whatever relay is in use right now, gradually catching up.</p><p>- I need to stress the above thread is a mix of fact (ATProto federation is duplicative and often brittle) and conjecture (I can't know what relay is being used internally by Blacksky except if Rudy tells us).</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416224224800921</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416224224800921</guid><dc:creator><![CDATA[mcc@mastodon.social]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:16:48 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:16:11 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> Each post is a dangling request which will consume 3s of CPU time and so 10× consumption of 300ms for alive server, and planned for reschedule. After a while, all workers are just stuck with full of 3s waiting process, with starvation for alive requests.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hhispngsq008z</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hhispngsq008z</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:16:11 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:14:11 GMT]]></title><description><![CDATA[<p><a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> <a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> It affect deliver to masto.ai because EACH of my post generate a dangling request, hiting timeout. After a while, my worker consume more time to dangling request taking 2-3s (hiting timeout) than trying to send content to masto.ai.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hexvgngsq008y</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5hexvgngsq008y</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:14:11 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:13:19 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/mcc%40mastodon.social" aria-label="Profile: mcc@mastodon.social">@<bdi>mcc@mastodon.social</bdi></a> From what I understand of the protocol, they could just stop using a relay at all, but then it would increase the traffic on all the PDS that were scrapped by the relay until then, since the AppView would have to connect to each of those instead of the relay.</p>
<p dir="auto">And did switching to another relay solved the issue?</p>
]]></description><link>https://board.circlewithadot.net/post/https://pleroma.breizh.pm/objects/d26f21d7-6db9-4779-b58a-5e77c361590b</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://pleroma.breizh.pm/objects/d26f21d7-6db9-4779-b58a-5e77c361590b</guid><dc:creator><![CDATA[breizh@pleroma.breizh.pm]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:13:19 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:12:19 GMT]]></title><description><![CDATA[<p><span><a href="/user/aeris%40firefish.imirhil.fr">@<span>aeris</span></a></span> <span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> this post you made probably just failed to deliver to a few instances. One of them could be mastodon.social if it was down. </p><p>How does that affect delivery to masto.ai? </p><p>mastodon.social being down is no different to your server than any other server being down. One request each.</p>]]></description><link>https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416206591605231</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416206591605231</guid><dc:creator><![CDATA[jeromechoo@masto.ai]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:12:19 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:10:44 GMT]]></title><description><![CDATA[<p><span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> When I initially raised my eyebrows at Bluesky's notion of "federation", I was told that anyone can run a relay on a small cheap computer, it's dead easy, etc.…</p>]]></description><link>https://board.circlewithadot.net/post/https://cosocial.ca/users/timbray/statuses/116416200311414600</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://cosocial.ca/users/timbray/statuses/116416200311414600</guid><dc:creator><![CDATA[timbray@cosocial.ca]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:10:44 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:07:31 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> The trouble scale not to the down instance size, but to the alive instance size. The more it is active with many content generated, the fastest the background job queue fill with dangling content.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h6dkkngsq008x</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h6dkkngsq008x</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:07:31 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:06:07 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a> <a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> So a huge instance sent dozen of post per second (many content generated, but delivered only one) to another huge instance, with one background job per content to deliver.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h4kb9ngsq008w</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h4kb9ngsq008w</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:06:07 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:04:20 GMT]]></title><description><![CDATA[<p><a href="/user/jeromechoo%40masto.ai">@jeromechoo@masto.ai</a> <a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a><span> Yes, I know that. Trouble is not one content send to many, but many content sent to one.<br />Each post of one instance is sent only once to mastodon.social, but </span><b>EACH</b> post.</p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h2a0fngsq008v</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5h2a0fngsq008v</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:04:20 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:03:30 GMT]]></title><description><![CDATA[<p><span><a href="/user/aeris%40firefish.imirhil.fr">@<span>aeris</span></a></span> <span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> failed deliveries happen all the time. mastodon.social is just another instance. Since Mastodon and misskey operate on shared inboxes, the failed deliveries won’t scale sender failures by recipient instance size.</p><p><a href="https://seb.jambor.dev/posts/understanding-activitypub/#:~:text=To%20combat%20this,our%20followers%20internally" rel="nofollow noopener"><span>https://</span><span>seb.jambor.dev/posts/understan</span><span>ding-activitypub/#:~:text=To%20combat%20this,our%20followers%20internally</span></a>.</p>]]></description><link>https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416171869190345</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://masto.ai/users/jeromechoo/statuses/116416171869190345</guid><dc:creator><![CDATA[jeromechoo@masto.ai]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:03:30 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 20:01:29 GMT]]></title><description><![CDATA[<p><a href="https://mastodon.social/@mcc">@mcc@mastodon.social</a><span> And it's a vector attack in theory. You can bootstrap thousands of instance, just subscribing to as many account as possible, and then just shutdown your instance.<br />Any content from subscribed account will generate a background job to your down instance, then hiting timeout each time.<br />You can just flood instance like that to continue to overflow queue with dangling content.</span></p>]]></description><link>https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5gylw4ngsq008s</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://firefish.imirhil.fr/notes/al5gylw4ngsq008s</guid><dc:creator><![CDATA[aeris@firefish.imirhil.fr]]></dc:creator><pubDate>Thu, 16 Apr 2026 20:01:29 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 19:58:45 GMT]]></title><description><![CDATA[<p><span><a href="https://mastodon.social/@mcc">@<span>mcc</span></a></span> <span><a href="/user/esm%40wetdry.world">@<span>esm</span></a></span> I think we'll need to wait for the analysis and blog posts that follow.</p>]]></description><link>https://board.circlewithadot.net/post/https://hachyderm.io/users/thisismissem/statuses/116416153225904246</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://hachyderm.io/users/thisismissem/statuses/116416153225904246</guid><dc:creator><![CDATA[thisismissem@hachyderm.io]]></dc:creator><pubDate>Thu, 16 Apr 2026 19:58:45 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 19:58:44 GMT]]></title><description><![CDATA[<p><span><a href="/user/esm%40wetdry.world">@<span>esm</span></a></span> <span><a href="/user/thisismissem%40hachyderm.io">@<span>thisismissem</span></a></span> I mean it's certainly possible that I am simply misinterpreting Rudy's comments about relays!… but all we ever get from Rudy are these vague gnomic comments, so this is about the best I can do. I'd rather him be spending his time sysadminining and writing Rust than writing up incident reports for public consumption but it does mean trying to figure out wtf is happening to my feed as a blacksky user is constant detective work</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416153154122615</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416153154122615</guid><dc:creator><![CDATA[mcc@mastodon.social]]></dc:creator><pubDate>Thu, 16 Apr 2026 19:58:44 GMT</pubDate></item><item><title><![CDATA[Reply to Bluesky is down today. on Thu, 16 Apr 2026 19:57:03 GMT]]></title><description><![CDATA[<p><span><a href="/user/esm%40wetdry.world">@<span>esm</span></a></span> <span><a href="/user/thisismissem%40hachyderm.io">@<span>thisismissem</span></a></span> That's interesting, but</p><p>1. If it's true, why would the DDOS differentially impact third-party PDSes on Blacksky while Blacksky PDS runs at normal speed?</p><p>2. Did atproto go down because of a DOS or because of some side-effect of an attempt to move over to it as the primary relay?</p><p>One possibility is the failures I saw were *because* we switched from bluesky to atproto.africa, causing a short netlag period while atproto.africa caught up to the present? I don't know?</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416146549961134</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/mcc/statuses/116416146549961134</guid><dc:creator><![CDATA[mcc@mastodon.social]]></dc:creator><pubDate>Thu, 16 Apr 2026 19:57:03 GMT</pubDate></item></channel></rss>