Stale Account Info Due to Caching Error

in steemit •  7 months ago

Starting at 5:50 AM Eastern time, a data caching error caused steemit.com and other applications leveraging Steemit’s HTTP API to display stale account history data. The fact that multiple applications displayed this information lead some users to believe that the issue was with the Steem blockchain, however, that was not the case. At no time was the blockchain affected and therefore at no time were follower counts, posts, or funds at risk.

We are still investigating the exact cause of the original caching error and should have fixes deployed within 24 hours. We have also instituted fixes which ensure that if the bug does appear again it will not result in stale account history being displayed. We apologize for any inconvenience this may have caused.

Team Steemit

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Steemit needs a status page that shows if things are up. When it goes wrong people panic. We need something on Twitter or elsewhere we can check for updates.

·

I'm in full agreement with you. A status page or something offsite where people can go for updates. Both. Discord maybe? A GINAbot alert? Something. I'd rather keep it in the confines of what users are commonly using that doesn't include the social media we're attempting to transition away from, but hey, even that is better than panicking from lack of information.

·
·

you could have just signed into
https://steemitstage.com
with your posing key as the steem blockchain was running just fine on there

·
·
·

That's certainly nice to know. I didn't actually have any issue today, though (it's buggy off and on this week, but so far not today). I was just agreeing with @steevc that some kind of universal heads up about what was going on would be nice.

·
·
·
·

I would agree that a service status page would be good

·

They indicated in this post that they do not like to give out real-time updates until they know what is going on, as it may provide information to a potential attacker. It seems better for them to make sure everything is safe before they tell the world that there is a problem.

·
·

That's fair enough, but letting people know they are aware there are issues helps to quell the panic.

I was thinking of something like this https://status.dropbox.com/

·
·
·

Same thing though. “We are aware of issues” = notifying the world there are issues, which could draw attention to something that would not be good to communicate until the situation is under control.

·
·
·
·

I think it's obvious there are issues when the site shows old data or nothing at all. As it gets bigger and there's serious money at stake there could be a lot of upset people out there who want reassurance. I don't expect them to announce security vulnerabilities unless they have already dealt with them.

·
·
·
·
·

Attackers are not necessarily going to be using the website 24/7, but posting an announcement to a place that is specifically for announcing outages is something that may give an attacker an alert.

I fully understand the seriousness, and the amount of money at stake. If you read that post I shared, they gave their policy on this type of thing. What you (and other users) want to happen in order to feel more safe is actually something that would make you less safe. Given the seriousness of what is at stake, not communicating anything until the situation is under control makes a lot of sense.

·
·
·
·
·
·

What you're saying makes a lot of sense, @timcliff. Thank you for your helpful explanation.

·
·
·
·
·
·
·

Thanks Terry :)

·

Cachet is even with this ironic name a very nice opensource project just for this, i am using it myself a longer while.

Thanks for reporting what happened!
I was expecting much longer downtime and was happy to see it recovered quickly.

Too much centralization around these APIs...

Too good to be true. Is this an incident report?

·

It is a badly done incident report.
And I should know that business.
But it is a step in the right direction:))

·

Lol I believe it is

ok..
I can breath now.

Well, it's good to hear that from your side! I'm pretty sure a lot of users were a bit concerned (myself included) about this, because nobody knew exactly what's wrong.

When steemit crashing , I was very scared.
But after about 1 hour it was turned on again,
I was very happy and exciting also...
Thanks Steemit team for notice us...

You are pretty fast! The hardest bugs to solve are that which are hard to reproduce, as this one may be, I am afraid. Good luck with it and hope we will hear good news from you guys soon!

Thank you for new update! Waiting for new update soon to be better!

I took it as a sign that I needed to go to bed lol. Left me a little confused that early in the morning why I was only seeing blogs/comments saying they where 12 or more day old and everything more recent being missing.

Thanks you for communicating with the community in regards to this outage.

I was wondering what that was. Thanks for the heads up! I thought my time machine actually worked this time!

Oke .. thank for information ..

good to know :)

me and a couple of others had more or less puzzled out it was something to do with caching.

Agree with @steevc we must have a separate announcement page or channel.

Never seen a problem like this before hopefully it does not happen too often otherwise there could be a lot of people panicking.

·

This isn't the first time this has happened. Though it may have been a different cause then.

Thank your for your explanation, @steemitdev.

I hope Team Steemit can resolve the probleem soon.

This is my report on my community in Jakarta at the time the problem. Sorry, it is still in Bahasa Indonesia.

https://steemit.com/steemit/@blogiwank/20180420-steemit-error

Thank you for the informations! We can solve all problems!

Thank you, @steemitdev We appreciate your watching out for us.

@steevc true talk, steemit needs an official page like all other social media, as a matter of fact , I will suggest that an important update like this be received on every steemians page.This will keep us abreast of recent antecedent and unfolding events.

Big thanks for the update and fast recovery time!

·

I nearly managed to read the first paragraph in your post about it possibly being a caching issue before it redirected me to a somethings wrong page ;)

·
·

I know what you mean ;) A refresh helps sometimes in that case.