502: Bad Gateway error

Nijimiss.moe (Misskey instance) under maintenance

From here: https://status.nijimiss.com/

#isitdown #misskey

503 Service Temporarily Unavailable

Edit: changed to "404 page not found"

Edit: it's back online

LemmyNSFW(.com) down; gives 502: Bad Gateway error

#isitdown

This is apparently a new instance that was short lived. Cannot reach http://lemmy.digdeeper.rodeo/c/xmpp and it apparently did not get widely federated.

So, I guess they did not get enough donations to pay the bills?

The communities are still reachable by e.g. visiting $yournode/c/AskLemmy@lemmings.world

Website is running but every page is just an error msg.

I get an "Internal Server Error" loading on my browser.

websitedown.org gives an "eggplant.place is reachable but failing with server errors", followed by "Returned 5xx server errors in 8 of 8 regions."

www.isitdownrightnow.com gives "[DOWN] Eggplant.place is DOWN for everyone."

isitdownchecker.com gives "PROBLEMS DETECTED" followed by "eggplant.place is not responding to our server checks. The site appears to be experiencing a significant outage." and "Down for 5 minutes".

A few free AIs with site-checking capabilities also can't reach it. One through DuckDuckGo also gave error 500, seemingly confirming my error and that from websitedown.org.

“This site can’t be reached”

And because infosec.pub is down, I wonder who else can see this post. Surely sdf people will see it, but since infosec.pub is offline then I suppose all other nodes will not see this post in !isitdown@infosec.pub.

Anubis, the instance's anti-bot system, seems to be working, so issue's a bit after that I'd imagine.

Also tested across multiple browsers, devices, VPN servers, a real IP, with and without login... Appears down in general.

I also noticed a few other sites I keep as homepage tabs on my browser were struggling to load, including Cloudflare being far jumpier than the usual, so I wonder if it's related.

Just times out for me.

Been unreachable for a day or so now.

Just times out.

Frogfind.com was probably a little known search service that was good at filtering out the garbage and gives a lightweight web UX. Now there is some kind of anti-bot check. I pass the check and enter a query, but then that just gives a blank page. Been happening for a few days now. I hope this service isn’t dead.

Same problem as a couple months ago. It has been down for a day or so now.

BTW, why these gateway errors? What gateway?

May have come back some 2~3 days ago since I saw around then an older link in a chat display a preview, and just remembered to check.

I think it started yesterday.

MTL of the attached post:

It will not continue to connect to Pawoo. The deadline for notifications on mastdn.jp has been extended to August 17th. When accessing in Google Chrome, DNS_PROBE_FINISHED_NXDOMAIN is displayed, so I think that the name resolution of the domain is not working well. “From August 5th, at 4:49am, pawoo has been having a server failure, and we are currently unable to use the service.”

Additionally, before finding the post, I tested on 3 instances I have accounts on, checked 5 "is it down"-style sites, and poked some online AI, and in no cases the instance was reachable either, so can confirm on my side.

Just last week I posted to !retrocomputing@lemmy.sdf.org. I can visit that particular thread but if I go to the timeline there is nothing newer than like 9 month or so.

Not sure of the full scope of the attack but I routinely fetch the lemmyverse dataset and see that over the past two days someone has created over a hundred bogus communities at discuss.tchncs.de.

(update) now looking at the timestamps, there is a non-uniform time between community creations often ranging from 2—10min. So it does not look automated. Maybe some pissed off kid manually did this? Or maybe someone who is just testing their attack script. Here is a sample:

…
exhibit56355@discuss.tchncs.de     2026-08-05T23:56:07.111126Z
exhibit74575@discuss.tchncs.de     2026-08-05T23:56:53.499897Z
montage49848@discuss.tchncs.de     2026-08-05T23:57:25.442903Z
gallery78147@discuss.tchncs.de     2026-08-05T23:59:49.329487Z
archive68564@discuss.tchncs.de     2026-08-06T00:09:18.605958Z
portfolio24010@discuss.tchncs.de   2026-08-06T00:12:13.200293Z
archive57120@discuss.tchncs.de     2026-08-06T00:12:26.712641Z
stills64667@discuss.tchncs.de      2026-08-06T00:18:44.101341Z
curated97085@discuss.tchncs.de     2026-08-06T00:20:27.982432Z
montage57326@discuss.tchncs.de     2026-08-06T00:25:18.222482Z
visuals79552@discuss.tchncs.de     2026-08-06T00:26:32.490046Z
portfolio82493@discuss.tchncs.de   2026-08-06T00:31:00.950359Z
curated50274@discuss.tchncs.de     2026-08-06T00:32:35.967834Z
archive62242@discuss.tchncs.de     2026-08-06T00:33:19.683080Z
archive95840@discuss.tchncs.de     2026-08-06T00:37:49.730539Z
visuals27150@discuss.tchncs.de     2026-08-06T00:40:28.852659Z
visuals37605@discuss.tchncs.de     2026-08-06T00:43:18.418426Z
curated85385@discuss.tchncs.de     2026-08-06T00:47:10.542885Z
visuals85531@discuss.tchncs.de     2026-08-06T00:49:14.857853Z
collection63981@discuss.tchncs.de  2026-08-06T00:51:42.154544Z
collection44977@discuss.tchncs.de  2026-08-06T00:53:34.997045Z
portfolio58030@discuss.tchncs.de   2026-08-06T01:02:16.596242Z
archive79163@discuss.tchncs.de     2026-08-06T01:04:15.370817Z
frames63631@discuss.tchncs.de      2026-08-06T01:11:01.770464Z
portfolio93081@discuss.tchncs.de   2026-08-06T01:23:46.632166Z
…

Maybe it’s not an attack per-se but rather a coded way to signal to a botnet.

It’s a pattern. And there is no FOSS tool for users to backup their Lemmy content, AFAIK.

SDF was down for a very long time.. like 4-6 months. After finally coming back online, we lost federation capabilities. We also lost the ability to create communities despite having the “Create Community” option.