Topic - memo.cash site status

Back to topics Threads View 10 followers

1601d
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.
1595d
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.
1595d
yeah, one of my memos was lost. If someone doesn't get me, that must be why.
1595d
I don't think this problem is fully fixed maybe? I am broadcasting "psots
1595d
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?
1595d
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.
1595d
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.
1595d
NO I WAS WRONG!
1595d
WAS A BUG. SORRY SORRY SORRY
1595d
Nothing wrong about being wrong:)
1536d
Unfortunately had an outage with receiving memos this morning. Site is healthy now. #memo #memostatus
1479d
Memo site is running into some issues related to the fork. Doing what I can to keep the site alive.
1479d
Sorry, there were a few more site issues this evening, caused by some bugs in the memo code. Site should hopefully be stable now.
1451d
Memo SV site had an outage today. It is resolved now.
1450d
When a memo.cash android application? Better on #bitcoin #BSV.
1314d
There has been an increase in the number of broadcast errors in last 12 hours. It is being investigated.
1314d
Apologies for having to turn on the Cloudflare interstitial a few times today, someone is trying distributed brute-force login attempts.
1314d
Also a reminder to use strong passwords and not re-use across sites :)
1314d
Can you characterize which accounts they were trying to compromise?
1305d
?:^)
1236d
Memo site had a network outage caused by a node upgrade. We have failed over to a backup node for the time being.
1176d
Memo site had a short outage due to a code update. The issue has been resolved, sorry for the inconvenience.
1047d
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.
1035d
There have been some reports of transactions not propagating. The issue looks to be resolved but I am investigating root cause.
1034d
I am aware of site slowness and am looking into it
217d
That to be ok