Service Disruption Post Mortem – August 31st

Service Disruption Post Mortem – August 31st

On Friday 31st August, 2018, the Bitfinex platform encountered an issue which forced us to suspend trading for a total of roughly 60 minutes. At 14.55 UTC the platform started encountering issues originating from our cloud hosting provider restarting a core matching server.

Our team begun assessing the damage immediately. Here we ensured that no data was lost and we flushed the pending queues to the database.

Once the integrity of the system was established, the restart and resync procedure was performed, as well as a series of automated and manual tests to ensure all functionalities were in order.

A list of all executed trades during downtime can be found here.

Please note in the above file that Type: Synchronising ME refers to trades executed as we recovered data that was not fully synced and saved onto our databases.

All users were kept informed via twitter.com/bitfinex, as well as bitfinex.statuspage.io. We are taking concrete steps to avoid a recurrence of this type of event and we sincerely apologise for the impact of our unplanned downtime.

The Bitfinex team

Stay up to date with Bitfinex on Twitter, LinkedIn, Telegram, Facebook & YouTube. 

The Bitfinex APIs are designed to allow complete access to the features provided by Bitfinex. Learn more about our API documentation here.

We’re hiring! Check out our open positions and get in touch. 

https://ift.tt/2C5LoeO

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more