Topic - memo.cash site status

Back to topics Threads View 10 followers

685d
The memo website lost network connectivity for a bit and memos weren't able to broadcast. Site is back to normal now. Sorry for the outage.
679d
Memo receiving node had an outage. Actions were still being broadcast but weren't being received. The node has been restarted and is functioning normally.
678d
yeah, one of my memos was lost. If someone doesn't get me, that must be why.
678d
I don't think this problem is fully fixed maybe? I am broadcasting "psots
678d
Woops... I am broadcasting "posts" via blockchain but they dont get picked up. Broadcast same thing via memo.cash and works. Same exact OP_RETURN... why not syncing on your server?
678d
Blockpress have the same issue. They don't sync their website to the blockchain. Memo.cash was working for name changes and profile text changes before... now not responding.
678d
What I mean is... it works when you do it on the site.. but not when I use a javascript or python script to follow your protocol on the blockchain. You're not querying the blockchain.
678d
NO I WAS WRONG!
678d
WAS A BUG. SORRY SORRY SORRY
678d
Nothing wrong about being wrong:)
619d
Unfortunately had an outage with receiving memos this morning. Site is healthy now. #memo #memostatus
563d
Memo site is running into some issues related to the fork. Doing what I can to keep the site alive.
562d
Sorry, there were a few more site issues this evening, caused by some bugs in the memo code. Site should hopefully be stable now.
535d
Memo SV site had an outage today. It is resolved now.
533d
When a memo.cash android application? Better on #bitcoin #BSV.
398d
There has been an increase in the number of broadcast errors in last 12 hours. It is being investigated.
398d
Apologies for having to turn on the Cloudflare interstitial a few times today, someone is trying distributed brute-force login attempts.
398d
Also a reminder to use strong passwords and not re-use across sites :)
398d
Can you characterize which accounts they were trying to compromise?
389d
?:^)
320d
Memo site had a network outage caused by a node upgrade. We have failed over to a backup node for the time being.
260d
Memo site had a short outage due to a code update. The issue has been resolved, sorry for the inconvenience.
130d
There was a site outage today caused by a full disk on the master db. It has been resolved and site has returned to normal functionality.
119d
There have been some reports of transactions not propagating. The issue looks to be resolved but I am investigating root cause.
118d
I am aware of site slowness and am looking into it