Backend Resources cannot be accessed at the moment. This incident was created by an automated monitoring service.
Figured I’d post this in case anyone else came by trying to figure out what the heck was going on…
Submitted 5 days ago by ccunning@lemmy.world to support@lemmy.world
https://fhf-lemmyworld.instatus.com/
Backend Resources cannot be accessed at the moment. This incident was created by an automated monitoring service.
Figured I’d post this in case anyone else came by trying to figure out what the heck was going on…
i see this slowing down my voting and slowing the sorting of comments inside a post
Hey I found this when I was having issues & couldn’t upvote or reply bc of the errors, lol, but ty for posting so I knew it wasn’t just me!
Ah. That explains why Lemmy is being all wonky today.
Looks like someone kicked the pods or something and the JSON api monitors are green again on the datadog dashboard: …datadoghq.com/…/e801a480-2ef0-11ee-8d4a-da7ad090…
I saw a report 24 hours ago that was a canary in the coal mine. Will link it once things are working again
This post lemmy.world/post/50440448
Not sure if related to root cause. I see several posts about 500 errors in the last week.
Thanks for the update. Was getting frustrated that I can hardly do or see anything lol. Hope it gets resolved soon!
MrKaplan@lemmy.world 5 days ago
Hi,
sorry for the late response to this. The immediate issue is resolved, and we’re looking to extend our monitoring in the coming days to have better insights on the underlying issue, as well as alerts before it would get to the point of throwing errors.
For some reason Lemmy has been having significantly more open file handles (including e.g. connections) than usual, leading to a denial of service. At this point it’s unknown whether this is caused by a bug in Lemmy, an attack, or something else.
TastySoup@lemmy.world 5 days ago
Ty for the update! :)