https://grafana.lem.rocks/d/edf3gjrxxnocgd/federation-health-activities-behind?orgId=1&var-instance=All&var-remote_instance=lemmy.ca&var-remote_software=All&from=now-24h&to=now

Decided to check out the site above and I'm not sure if I'm reading things correctly, but it looks like we're running behind Lemmy.World by a significant amount compared to the other major instances. I'm also noticing the scores of my posts in a Lemmy.World community is not updating despite receiving upvotes.

Anyone else experiencing similar issues or any odd issues in general?

all 11 comments

sorted by: hot top controversial new old
[–] 3 points 10 months ago* (last edited 10 months ago) (1 child)

Lemmy.world doesn't appear to have synced with Lemmy.ca since around 3pm today. (30 nov 2025) It sucks to have server issues on a Sunday and also when world admins are likely on Thanksgiving holiday so it could be tough to troubleshoot.

It appears lemmy.ca threads show correctly on .world, which would suggest something wrong on the .ca side.

My random guess is a spam rule on the lemmy.ca got triggered or something else went on the fritz, in any case blocking inbound connections?

Update: it appears other servers are having issues with lemmy.world outbound federation.

  • source
  • hideshow 1 child comment
  • [–] 2 points 10 months ago

    I'm not sure the issue is on the .ca side, something's going on between .world and Sopuli too now. Started almost exactly 3 hours ago. At the same time, .ca to .world sync started getting worse again too

  • source
  • parent
  • [–] 2 points 10 months ago* (last edited 10 months ago) (6 children)

    Thanks for flagging this, I don't think it's an issue on our side. I've whitelisted LW in our cloudflare just in case, and reached out to one of the LW admins.

    2025-11-30T20:23:37.635652Z  INFO lemmy_federate::send: lemmy.world: retrying ActivityId(29239709) attempt 2 with delay 1.25s. (Activity https://lemmy.ca/activities/announce/dislike/93aa88c6-1c46-4c2e-9354-2b4ff53a4e78 to https://lemmy.world/inbox failure with status 503 Service Unavailable: <html><body><h1>503 Service Unavailable</h1>
    No server is available to handle this request.
    </body></html>
    
  • source
  • hideshow 6 child comments
  • [–] 1 point 10 months ago (5 children)

    They've restarted their federation container and seems to be dropping now.

  • source
  • parent
  • hideshow 5 child comments
  • [–] [S] 1 point 10 months ago (2 children)

    Looks like it's happening again. It happened once yesterday (at a smaller scale), and again today. Any chance you may know if the LW team is aware of this being a recurring issue?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 10 months ago* (1 child)