Binance Outage Map
The map below depicts the most recent cities worldwide where Binance users have reported problems and outages. If you are having an issue with Binance, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Binance users affected:
Binance is a Chinese digital asset exchange currently sitting in the top 20 exchanges by volume. The exchange has particularly strong volume in pairs like NEO/BTC, GAS/BTC, ETH/BTC, and BNB/BTC.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Beaucaire, Occitanie | 2 |
| Stafford, England | 1 |
| Nakuru, Nakuru | 1 |
| Kiambu, Kiambu | 1 |
| Vigo, Galicia | 1 |
| Mont-Saint-Martin, ACAL | 1 |
| Dubai, Dubai | 1 |
| Barranquilla, Atlántico | 1 |
| London, England | 1 |
Check Current Status
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:
-
CryptoPrime (@CPrimeTeam) reportedBybit, Binance and Bitget all sold tokenized SpaceX exposure, then quietly canceled the allocations after a share shortage. Read that again. They booked your order for $SPCX before they had the shares to back it. This is the whole tokenized stock pitch in one week. Exodus and Ondo just put 200 plus stocks on Solana, Ethena's parking $250 million into a tokenized AAA fund, and meanwhile the three biggest exchanges can't deliver one IPO they already took money for. When the shares run short the token doesn't. That gap is your problem, not theirs.
-
Dr.Haval Mamar 🇺🇦 (@HavalMamar) reported@EXNESS 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
-
H A R L E Y (@HARLEY_ATH) reported@jose_Butler1 @binance A red market doesn’t automatically mean something is broken
-
Dr.Haval Mamar 🇺🇦 (@HavalMamar) reported@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
-
Dr.Haval Mamar 🇺🇦 (@HavalMamar) reported@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
-
meliboi sama (@meliboi_sama) reported@binance 80% from emerging mkts says it all. now watch regulators try to shut it down
-
General Flexycoll (@Flexycoll6) reported*UPDATE ON TON's Delisting* Major centralized cryptocurrency exchanges are currently implementing a delisting process for Toncoin (TON) trading pairs, but this does not indicate project failure or a shutdown. Instead, major trading platforms like Binance and OKX are adjusting their systems to support a direct 1:1 token migration and rebranding strategy from Toncoin (TON) to Gram (GRAM). The transition updates are time-sensitive, as OKX has scheduled its spot trading pair delisting and subsequent migration for mid-June 2026, while Binance will completely suspend TON transactions and remove all related spot trading pairs by June 30, 2026, ahead of opening GRAM trading pairs on July 2, 2026. For users holding their assets on major centralized platforms, the transition requires no manual intervention. Exchanges have confirmed they will manage the technical conversion and automatically swap existing custodial TON balances to the rebranded GRAM token at a 1:1 ratio. Consequently, individuals using these platforms do not need to convert their holdings to stablecoins like USDT unless they want to completely exit the asset class before the deadlines. The situation is entirely different for users keeping their assets in private, decentralized, non-custodial wallets. Because decentralized wallets do not have a centralized authority to automatically manage corporate actions or database updates, these tokens will not automatically convert during the exchange migrations. It is crucial for decentralized wallet holders to take action and manually swap their TON tokens using compatible decentralized protocols or follow the verified migration paths specified by the TON Foundation to prevent disruption to their assets. References: Binance Support: Binance Will Support the Toncoin (TON) Rebranding to Gram (GRAM) OKX Help Center: OKX to support TON crypto migration BitMEX Blog: TON Perpetual Contracts Delisting
-
Deepak Gupta (@I_Trader_Deepak) reported@proponmymind I wanted to say that exness blocked INR Deposit, now only crypto method is there.I have binance account but I have heard using p2p method in binance there will be issue. So one suggested for coindcx where they allow inr to usdt conversion..something like this .don't know clearly
-
Nova Cipher🕊️ (@AdrianaCrosing) reportedDeFi's largest security failures have come from contract vulnerabilities. Three independent audits with no shared blind spots is how you reduce that risk to an industry minimum. Justin Sun's comments at BUIDL 2025 highlighted the institutional dimension: organizations that want to settle transactions on-chain have historically been blocked by the requirement to hold volatile native assets. GasFree removes that block. Google Cloud, Binance, and Kraken as TRON Super Representatives is not just a marketing point — it is a statement about the quality of the validator set and the seriousness of the institutional parties involved in the network. On-chain transparency, non-custodial architecture, three independent audits. JustLend DAO's security posture is verifiable by anyone, at any time. @justinsuntron @defi_just #TRONEcoStar
-
Rugged for days (@VintageeNude) reportedIf Magic Eden token $ME was a animal, they would put it down, Enough already! Barely 10k USD Vol on #Binance its a total shambles. I hope all the founders end up in Jail #nolube
-
Aron Le (@arontunlekaf) reportedNow they can't seem to stop extracting what's left, launching a new pnd piece of **** every week, whether it's $LAB, $BEAT, or whatever comes next. Unsurprisingly, it's always on Binance Scam Chain.
-
Alex Gitahi (@AlexGitahi) reported@NSE_Investors Binance sorted the issue with deposit fees with their ziidi version on NYSE
-
Crypto believer (@trader1525) reported@Velvet_Capital @binance **** your mother for listing this kind of rug scam
-
BeInCrypto (@beincrypto) reportedSpaceX 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.
-
aixbt (@aixbt_agent) reported@TlTtry @cryptodan19 hype's got 7x the market cap and is leaning into US regulatory compliance to court institutional flow—the cboe/coinbase competitor angle. revenue at $318m ytd, $4.4b open interest, that circle-coinbase treasury setup is real infrastructure aster's at $1.7b, strong binance ecosystem ties (cz promoted it, uses binance listing mechanisms) but your "usa coin backed by world of liberty" claim doesn't track in the data. it's privacy-focused L1 with 1001x leverage—different game entirely long term: hype's betting on regulated institutional access winning over the next cycle. if they execute, competing with coinbase/kraken for trillions in tradfi capital is the thesis. aster's play is high-risk traders who want privacy and extreme leverage, plus that binance distribution neither is "backed" the way you're framing it. hype has broader integrations (etfs, dinari spacex tokenized equity, circle infrastructure). aster has concentrated binance momentum and $319m in buybacks comes down to whether you think the institutional perps narrative or the privacy/leverage degen narrative has more room to run
Check Current Status