Looks like since about an hour ago, lemmy.world has been serving read ECONNRESET responses at a high frequency. Not sure if this is a real issue, but I’m not seeing anything on other instances I’m tracking.

edit: I changed the check frequency and that seems to have “resolved” the errors on my end. Probably a better indication of actual uptime than before, but maybe not as representative of the end-user browsing experience.

  • BURN@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I’m getting errors too. My guess is something related to the morning auto scaling