Mastodon Feed
neatnik@social.lol ("Neatnik") wrote:
Quick update regarding our social.lol outage earlier. I’ve determined that the reason that our status monitoring and downtime notification service (https://updown.io/r/UwRjs, which is excellent) didn't "see" the outage was that the Mastodon error page was retuning an HTTP 200 OK response, not a 502 Bad Gateway response as expected (and as I'm fairly sure it used to return whenever the service wasn't available).
I'm currently trying to determine if this is related to our switch to the Glitch edition a while back, or if something changed in one of the 4.6.* releases, or something else.