UPDATE: @[email protected] has responded

It is temporary as lemmy.world was cascading duplicates at us and the only way to keep the site up reliably was to temporarily drop them. We’re in the process of adding more hardware to increase RAM, CPU cores and disk space. Once that new hardware is in place we can try turning on the firehose. Until then, please patient.


ORIGINAL POST:

Starting sometime yesterday afternoon it looks like our instance started blocking lemmy.world: https://lemmy.sdf.org/instances

A screenshot of the page at https://lemmy.sdf.org/instances showing the lemmy.world instance on the blocklist

This is kind of a big deal, because 1/3rd of all active users originate there! A pie chart depicting the top instances by usershare. The lemmy.world instance is in the top spot with 1/3 of the total usershare

Was this decision intentional? If so, could we get some clarification about it? @[email protected]

  • chaorace@lemmy.sdf.orgOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    As someone working on integrations I’d also have to leave if we’re permanently blocking the largest instance, but I’d like to give SDF the benefit of the doubt here. Maybe this was just a temporary measure to deal with the insane load from yesterday?

      • chaorace@lemmy.sdf.orgOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        I don’t know if geoblocking is a thing, but just FYI: there are additional Lemmy SDF instances for EU & JP regions which may work better depending on where you’re based.

        • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Ah, seems like blacklisted IP. Since I am behind CG-NAT the public IP is simultaneously shared between many users. I tried disconnecting and reconnecting to the network which changed my public IP, and it works now.

          We really need the IPv6.