I think it is good to point it out though. kbin.social is missing from the fediverse observer, but if you have a look at this: https://mbin.fediverse.observer/list you'll see that almost all mbin servers have a >98% recent uptime and a >95% uptime over the whole lifetime of the server. Sadly, fedidb does not have an uptime metric

(yes mine is not up there, because it was offline for a week in september last year)

[–] BentiGorlich@gehirneimer.de 10 points 5 months ago* (last edited 5 months ago) (1 children)

https://kbin.fediverse.observer/kbin.social there you can go to graphs and see the uptime. The overall uptime is actually still quite good with 95.94%, but in recent months it has been a bit rough

[–] BarbecueCowboy@lemmy.world 6 points 5 months ago (1 children)

A lot of the time it was technically 'up', but just non-functional/unusable.

Most common for me was just not being able to do anything but look at the front page, couldn't click on anything without errors.

[–] OpenStars@discuss.online 3 points 5 months ago (1 children)

That is an excellent point - I so rarely went there but I thought I recalled that being my experience as well, and yet I wasn't certain enough to say so. It really does mess with the stats if we are trying to use "server uptime" to compare between instances or Kbin vs. Mbin.

[–] BentiGorlich@gehirneimer.de 3 points 5 months ago

well server uptime is usually, and in the case of fediverse observer, coupled to a successful response. If the server spits out a 500 internal server error, that does not count as being up