Binance Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

Binance Issues Reports

Latest outage, problems and issue reports in social media:

• 
  AzraCiv (@AzraCiv2310) reported 3 minutes ago

  @analyst9701 @binance @BinanceHelpDesk Something strange is happening,a user that I know that dont even do Creator Pad or trade competitions, only holds and does NOTHING thats against the rules got baned from all activities ! This is ridiculous , BInance must fix this issues with rstricting users with no explanation!

• 
  _khaleem (@am_emkayx) reported 4 minutes ago

  @BinanceHelpDesk to that address. The transaction was successfully confirmed on the TRON blockchain, and I have the TXID and screenshots as proof. However, after the deposit did not arrive, Binance support informed me that this address is not associated with my account.

• 
  Crypto Miners (@CryptoMiners_Co) reported 9 minutes ago

  A lot of people assumed stock trading on @binance would mostly appeal to existing investors the early numbers suggest something different around 25% of stock users in the first week were under 25 years old, and more than 80% of trading volume came from emerging markets that sounds less like people switching brokers and more like people getting access they didn’t have before fractional shares starting from $5 seem to be playing a big role too. nearly 40% of trades were placed under $100 during the first week the demand showed up quickly too. Binance reached $400M AUM in its first week, with nearly two-thirds of sign-ups going on to place a trade maybe the challenge was never interest, just access!

• 
  Dr.Haval Mamar 🇺🇦 (@HavalMamar) reported 10 minutes ago

  @sirrillahfx Exness Platform Manipulation & Criminal Investigation On June 5, 2026, the Exness server bridge (Exness-Real37) suffered a catastrophic infrastructure freeze during peak market volatility, hit a massive 1,060ms server execution lag, and generated 7 consecutive ⁠[Off quotes]⁠ rejections with an impossible 0.00000 price stream, paralyzing my terminal and causing a forced liquidation of $124,306.17 USD. While Exness attempts to falsely blame weekend margin limits, their own data table proves their server threw data-feed errors (⁠[Off quotes]⁠) instead of the hardcoded MetaTrader 4 margin code (⁠[Not enough money]⁠), confirming the backend liquidity bridge crashed before calculating equity. Because Exness previously acknowledged this identical system failure pattern on my profile on May 6–7 and paid $84,273.24 USD in "Trading compensation," their current refusal constitutes absolute bad faith. Consequently, this file has escalated into an active criminal matter with the Ukrainian Cyber Police under official case numbers ЄО № 269 and ЄО № 337, a high-level merchant dispute is live with Binance Pay Compliance (Case ID: 163136145 / Ticket: RCM20260610161534094360) to freeze and reverse my historical deposit pipeline, a licensing audit petition has been logged with the Seychelles FSA, and an international civil lawsuit is being submitted to the Tribunal de Judiciaire de Paris by Tuesday morning. Exness must bypass automated support templates and credit a flat, final $45,000 USD compromise gesture to my balance today to sign a mutual NDA and halt all ongoing international enforcement tracks; otherwise, their digital payment infrastructure and regulatory standing will be dismantled publicly and legally. 🚨 Core Evidence Points: The System Failure: A documented 1,060ms server lag and multiple ⁠[Off quotes]⁠ (0.00000 price) blocks locked the terminal on June 5th, freezing all risk management and wiping out $124,306.17. The Technical Proof: Exness's data table shows insufficient margin, which programmatically forces MT4 to say ⁠[Not enough money]⁠. Throwing an ⁠[Off quotes]⁠ network error instead proves their pricing pipeline crashed first. The Payout Precedent: In an identical platform freeze on May 6–7, Exness admitted fault and paid $84,273.24 in compensation. They cannot legally redefine the same error code as a user mistake now. Active Cyber Police Files: The National Cyber Police of Ukraine have officially processed both cases under criminal reference numbers ЄО № 269 (May) and ЄО № 337 (June), forwarding them to local investigators for pre-trial entry (ERDR). Active Binance Pay Dispute: Live compliance cases (Case ID: 163136145 / Ticket: RCM20260610161534094360) are open to audit, flag, and reverse all deposit pipelines processed through Binance Pay to the Exness corporate entity. The Final Ultimatum: Exness has until the close of business today to credit a $45,000 compromise settlement to resolve both profiles under an NDA, or face a Tuesday morning Paris Court filing, an FSA license audit, and viral public exposure of their server logs. #exness @exness

• 
  BitTorrent (@BitTorrent) reported 12 minutes ago

  📢 Announcement on the phased shutdown of the BTTC Bridge. Based on the current status of the cross-chain bridge service and after careful evaluation, the official BitTorrent Chain team has decided to initiate a phased closure of the BTTC Bridge. Effective June 13, deposits will close, and all withdrawals will conclude by June 18. Users are advised to migrate mapped tokens, such as TRX_e and TRX_b, back to their native source chains, including TRON, Ethereum, and BSC, before June 18. Please note that after this deadline, users will no longer be able to bridge these tokens back via the BTTC Bridge. Please be assured that BTTC operations, block generation, staking, delegation, and validator rewards remain unaffected by this adjustment. After the closure, cross-chain swaps can still be completed via major exchanges like HTX and Binance. The official team will continue to monitor the liquidity of the related mapped tokens.

• 
  No Unlock ICO #WLFI = Scam Team #WLFI + #USD1 🖕 (@Lambadalxo) reported 12 minutes ago

  @worldlibertyfi @binance **** yoi 🤮🤮🤮 Scam 💩💩💩💩💩🔪🔪🔪🔪

• 
  ceviz ağacı (@bobidibibidibo1) reported 13 minutes ago

  @InvestWithD @binance Ripple has billions of this useless ****. Dont worry

• 
  Epix (@zone_epix) reported 13 minutes ago

  @binance can't manifest yet will support the winner

• 
  Teresa (@Teressa211192) reported 18 minutes ago

  People spend 10 hours hunting for a 10x coin, but won’t spend 10 minutes securing their account. ​If you're starting in crypto today, don’t start with charts. Start with safety: ​• Double-check official URLs/apps • Enable 2FA (and not just SMS) • Test a small withdrawal first • Know where to find official, legitimate support ​One careless click will do way more damage than a bad trade. No platform can eliminate all risk, but utilizing the security tools and educational resources available is your best defense. ​Protect your capital first. The market isn't going anywhere, but your funds will if you get lazy. 🤝 #Binance #LearnWithBinance #BinanceAcademy

• 
  Rafal Jakobsen | Intel (@rafal_jakobsen) reported 19 minutes ago

  @DegenerateNews @binance Better just buying prep on Hyperliquid. no issue.

• 
  Dr.Haval Mamar 🇺🇦 (@HavalMamar) reported 24 minutes ago

  @Exness Platform Manipulation & Criminal Investigation On June 5, 2026, the Exness server bridge (Exness-Real37) suffered a catastrophic infrastructure freeze during peak market volatility, hit a massive 1,060ms server execution lag, and generated 7 consecutive ⁠[Off quotes]⁠ rejections with an impossible 0.00000 price stream, paralyzing my terminal and causing a forced liquidation of $124,306.17 USD. While Exness attempts to falsely blame weekend margin limits, their own data table proves their server threw data-feed errors (⁠[Off quotes]⁠) instead of the hardcoded MetaTrader 4 margin code (⁠[Not enough money]⁠), confirming the backend liquidity bridge crashed before calculating equity. Because Exness previously acknowledged this identical system failure pattern on my profile on May 6–7 and paid $84,273.24 USD in "Trading compensation," their current refusal constitutes absolute bad faith. Consequently, this file has escalated into an active criminal matter with the Ukrainian Cyber Police under official case numbers ЄО № 269 and ЄО № 337, a high-level merchant dispute is live with Binance Pay Compliance (Case ID: 163136145 / Ticket: RCM20260610161534094360) to freeze and reverse my historical deposit pipeline, a licensing audit petition has been logged with the Seychelles FSA, and an international civil lawsuit is being submitted to the Tribunal de Judiciaire de Paris by Tuesday morning. Exness must bypass automated support templates and credit a flat, final $45,000 USD compromise gesture to my balance today to sign a mutual NDA and halt all ongoing international enforcement tracks; otherwise, their digital payment infrastructure and regulatory standing will be dismantled publicly and legally. 🚨 Core Evidence Points: The System Failure: A documented 1,060ms server lag and multiple ⁠[Off quotes]⁠ (0.00000 price) blocks locked the terminal on June 5th, freezing all risk management and wiping out $124,306.17. The Technical Proof: Exness's data table shows insufficient margin, which programmatically forces MT4 to say ⁠[Not enough money]⁠. Throwing an ⁠[Off quotes]⁠ network error instead proves their pricing pipeline crashed first. The Payout Precedent: In an identical platform freeze on May 6–7, Exness admitted fault and paid $84,273.24 in compensation. They cannot legally redefine the same error code as a user mistake now. Active Cyber Police Files: The National Cyber Police of Ukraine have officially processed both cases under criminal reference numbers ЄО № 269 (May) and ЄО № 337 (June), forwarding them to local investigators for pre-trial entry (ERDR). Active Binance Pay Dispute: Live compliance cases (Case ID: 163136145 / Ticket: RCM20260610161534094360) are open to audit, flag, and reverse all deposit pipelines processed through Binance Pay to the Exness corporate entity. The Final Ultimatum: Exness has until the close of business today to credit a $45,000 compromise settlement to resolve both profiles under an NDA, or face a Tuesday morning Paris Court filing, an FSA license audit, and viral public exposure of their server logs. #exness @EXNESS @Exness_Arabic

• 
  0xPeter (@_0xpeter_) reported 25 minutes ago

  you can say what you want but at least binance is active in crypto all coinbase does is extract people working at base live in their high castles and people working at coinbase couldnt tell you if btc was at $6k or $60k

• 
  BeInCrypto (@beincrypto) reported 26 minutes ago

  SpaceX IPO access became the first big stress test for tokenized stocks. Binance, Kraken, Bybit, and others saw huge demand for $SPCX exposure, but allocations came in far below expectations. Bybit got zero allocation and refunded users. Meanwhile, Solana CPO Vibhu says this is exactly why open markets matter: multiple issuers can compete, users get choices, and no single platform owns the outcome. Crypto rails moved fast. Wall Street still controlled the shares.

• 
  Crypto Enthusiast (@CryptoUncle1337) reported 26 minutes ago

  @Xmax3453Ali Sadly eschanges like coinbase wont do any burns as binance does. So im not sure how much a listing will help the chain. it would even shift trading from binance to coinbase and reduce burns. But maybe hype and transactions will go up a little.

• 
  @Ahmad (@Ahmadshah0328) reported 26 minutes ago

  @Third_Eye_000 @cz_binance @BinanceHelpDesk Its Impossible cuz of binance