There were two problems:
First, The monitoring system did not send out an alert so we didn't know something was wrong with the host server until around 3PM.

Second, we would run into hardware problems even back in AWS cloud computing days. In this case, the host server's DNS resolution was broken and failed to resolve the domain name of the internal monitoring system, resulting in the failure to execute processing of plurks on a timeline.

Once we discovered that it's a hardware problem, we replaced it with new hardware before removing the old ones.

Notes: Errors mine. I'm not very savvy on server/website backend things

Anyway things are fixed now \o/

yaaayy!!! thank you for translating

aw thank you

yay, back on line . . . .I had to interact with real people for a while

We appreciate your work 🙌 thanks

hi

Wholesale Nitrile Gloves in UK