SDF outgoing federation seems to be stuck
SDF outgoing federation seems to be stuck
Neither of my posts from yesterday and today have made it out to their communities' home instance (lemmy.world), and neither has received any comments or votes. It seems like something to do with outgoing federation is stuck.
Edit to clarify:
The problem I'm seeing affects posts. I don't know if it affects comments.
It's possible that it only affects lemmy.world communities, but it definitely affects them even on other instances. Neither of these posts are showing up on any remote instance that I've seen:
https://lemmy.sdf.org/post/21620419
https://lemmy.sdf.org/post/21673588
6 days later, it's happening again:
You're viewing a single thread.
Slrpnk seems to be receiving your posts
Looks like it received this one, but not the ones I mentioned that are in lemmy.world communities.
From my experience, lemmy.word can take hours to federate to no matter the instance. I think they might be using some weird shit for "last mile".
Can't wait to see what happens when/if they move to sublinks. How much worse can they get
How much worse can they get
I think kbin.social showed us that overload can get much worse.
Would a federation problem on lemmy.world block propagation to slrpnk.net? That would be a weirdly inefficient network design.
That's (an example of) what I'm seeing right now. It's abnormal.
Hours wouldn't raise my attention. I'm talking days.
I think they might be using some weird shit for “last mile”.
Given that lemmy.world uses Cloudflare, I wonder if their server is overloaded enough to sometimes exceed Cloudflare's 100 second timeout, triggering http-524 errors during federation.
From experience sh.itjust.works sometimes has this problem as well.
They also have one thing in common: Cloudflare
Perhaps it's getting "protected" from federation considered a DoS.