Bitfinex incident

Trading engine issues

Major Resolved View vendor source →

Bitfinex experienced a major incident on June 5, 2018 affecting Web Server and Trading Engine and 1 more component, lasting 2h 5m. The incident has been resolved; the full update timeline is below.

Started
Jun 05, 2018, 10:47 AM UTC
Resolved
Jun 05, 2018, 12:52 PM UTC
Duration
2h 5m
Detected by Pingoru
Jun 05, 2018, 10:47 AM UTC

Affected components

Web ServerTrading EngineBackend WorkersWebSockets

Update timeline

  1. investigating Jun 05, 2018, 10:47 AM UTC

    The platform is experiencing issues in the trading engine, our admins are aware and are working on bringing the platform back to normal operations. We will publish updates on https://bitfinex.statuspage.io and on https://twitter.com/bitfinex to keep users updated.

  2. identified Jun 05, 2018, 11:10 AM UTC

    The cause of the platform outage has been identified. The platform admins are addressing the issue as we speak and will bring the platform back online as soon as possible.

  3. identified Jun 05, 2018, 11:28 AM UTC

    We are continuing to work on a fix for this issue. We are close to being able to relaunch the platform. The admins are running checks to be able to resume normal operations shortly

  4. identified Jun 05, 2018, 11:50 AM UTC

    Bringing back the platform back online is taking longer than expected. We are running tests in order to safely resume normal operations. If no issues are detected, relaunch can be within the next minutes, it can take longer if we do encounter unexpected outcomes of the tests. We fully understand users wish to receive a clearer ETA, but at this point, we cannot be more specific. Apologies for any inconvenience caused.

  5. identified Jun 05, 2018, 12:02 PM UTC

    We are close to relaunch, we expect within the next few minutes

  6. monitoring Jun 05, 2018, 12:14 PM UTC

    The platform is back online. The cause of the issues was with our infrastructure provider. We will closely monitor the platform. Apologies for the inconvenience.

  7. resolved Jun 05, 2018, 12:52 PM UTC

    The platform is back to normal operations. The cause of the outage was an issue with our infrastructure provider. This has been addressed.