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 |
|---|---|
| Itu, SP | 1 |
| Seattle, WA | 1 |
| Nice, Provence-Alpes-Côte d'Azur | 1 |
| Beaucaire, Occitanie | 2 |
| Stafford, England | 1 |
| Nakuru, Nakuru | 1 |
| Kiambu, Kiambu | 1 |
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:
-
CRYPTOSIXT (@CRYPTOSIXT) reported@pete_rizzo_ Access is not capital A #Binance listing expands distribution, not demand Billions don't flow into #Bitcoin because a product is listed They flow only if investors choose to allocate capital.
-
JO CRYPTO GEMS (@JoCryptoGems) reported@Cryptocore001 @binance @Jia_Lilly01 Capital doesn’t lie. Binance turned one more login frustration into a billion-dollar bridge. Who’s still siloed in 2026?
-
Koleman Strumpf (@KolemanStrumpf) reported@ardnox @RuizheJia @ShihaoY I would think the two need to converge so both should move (arbs should be offsetting the manipulators, eg pushing back on Binance). Since the polymarket contracts involve very specific thresholds I would think this would be an issue
-
Aman (@mfardecrouz) reported@CryptoTeluguO When is Binance Alpha shutting down Harsha
-
ivish (@beingivish) reported@derteil00 You’re a gentleman. Few of the .HLs are no Les than clowns, always hate mongering. They don’t understand it’s CEX v/s DEX and not DEX v/s DEX. You just spoke pure facts man. Respect 🫡 I want hyperliquid, lighter, Variational, extended etc to become very big. On a normal day Binance makes > spot + derivatives Combined: ~$59.5B in a single day (just on a normal slow market day) I’m not even considering other CEX here (OKX and Bybit is also killing it) Quick napkin math on Binance fees: → Spot at ~0.075% effective ≈ $5M/day → Derivatives at ~0.015% effective ≈ $8M/day → ~$13M/day in fees everyday; That’s ~$4.7B a year. From trading fees alone. ———— There’s a huge space for perpDEXs to grow imo. Everything is going to be onchain. We’re just getting started. Hyperliquid, lighter and maybe even asterDEX due to binance could become really very big. We’re so early 🏆🤝
-
Killa the Wizard (@KillaMicWizard) reported@trader1sz Chad, yo trader could you help me investigate what happened to my Bert, I was drained 1.3m Bert, 2 days ago...no idea what happened, and if anyway to recover it would be possible, caludecode find it's binance wallet.
-
Jolley (@M_FuoriclasseX) reported@zachxbt @binance @Gate_io I think they shut down their app and telegram or maybe they just blocked me lol
-
Daily Crypto Trader (@memecoin_trades) reported@_trade4life_ @binance Yeah still no issues
-
Byteborg 69 (@Byteborg69) reported$BNB Binance Wallet will support Base B20 token trading. Meme Rush will add B20 token filtering and display.
-
James Bearish Bull (@jamesjasmy) reported@HARA_JasmyCFO How hard is it to pick the phone up and say ; ''hello is that my Binance relationship manager'' ''OK what is the problem here'' ? ''Ok, I hear you, how would you like us to fix it'' ? That is really the only thing we are looking at here! The truth is you have nothing.... Nothing really built, Nothing I couldn't do with 3 coders in a week. $jasmy #jasmy
-
🐝 Neo (@0xBeeSmart) reported@binance 80 percent from emerging markets lines up with what tokenization can unlock. Small beekeeping operations there could issue shares on actual hive yields instead of waiting on banks. That turns local honey into something tradable anywhere.
-
teddy (@teddyX77) reported@missoralways @bibiplushie Sorry to be bearish but you pvp’ed a narrative that already exist, secondly with the name “binance bibi” it will never be listed on binance alpha (same problem with the original bibi) this pump isn’t going to last.
-
Captain X 🔸 (@bnbcaptain) reportedEnd of the day, these manipulators are taking aways Your Platform users money Binance is the largest liquidity hub, so it matters for the whole ecosystem. - Binance needs to care more about this issue - Manipulator and MM are taking money away @cz_binance @heyibinance @_RichardTeng
-
Patt is taking a nap (@pattisme_) reportedWatchlist: $BTC @ 61.5k (4H support) & 60k. $ETH @ 1712 (1H pivot support) & 1692. $SOL @ 76.29 (4H support) & 70.8/68.7 (invalidation band, high liquidation risk). $XMR: High positive funding (Binance 0.0006) → short-the-rip opportunity. $ATOM: Negative funding (Binance -0.0003) → long-the-dip if stable. Market bias remains negative. Prioritize short-the-rip setups with clear R:R. Stay cautious.
-
Dusty Field (@dusty_field) reportedTwo security disclosures this week expose different layers of blockchain infrastructure: a VM-level execution flaw in a Move-based L1 and a governance-layer treasury drain on Solana. Aptos / Hexens: Security firm Hexens publicly disclosed on July 4-5 a critical stale-cache bug in the Aptos Move virtual machine, reported privately through SEAL911 channels on February 25 and patched by Aptos Labs within hours, with a public pull request on February 27. The flaw was a type-confusion vulnerability in the Move VM execution environment, the layer that processes every smart contract on the network, where stale cached data could cause the runtime to misclassify on-chain resource types. Hexens simulated the attack on a cluster approximating one-third of the validator set using a server setup costing roughly $3,000, achieving a near-90% success rate with no insider access or special permissions required. Hexens estimated first-order systemic exposure at $70 billion, accounting for stablecoins, cross-chain messaging systems including LayerZero and Wormhole, USDC's CCTP, and DeFi protocols connected to Aptos. Aptos Labs disputed the practical exploitability under real mainnet conditions. Polygon CTO Mudit Gupta independently reviewed the proof-of-concept and validated it ran as claimed. No user funds were lost; the fix was applied at the network level before any confirmed exploitation. The disclosure is now public, meaning protocols that depend on Aptos for settlement or bridge connectivity should treat it as a prompt to audit their dependencies against the patched runtime. BonkDAO / Solana Realms: On July 6, an attacker drained approximately $20 million in BONK tokens from the BonkDAO treasury using the protocol's own token-weighted governance system on Solana's Realms platform. The sequence began June 30 with the submission of proposal BIP-76, which embedded a treasury transfer instruction inside governance language. Over July 4 and 5, a separate wallet spent roughly $4.4 million buying BONK on Bybit and Binance, acquiring just over 1% of supply, the exact quorum threshold. The proposal passed with 99.9% yes votes, only seven addresses voted in total, and roughly $20 million in BONK moved automatically to attacker-controlled wallets. No smart contract was exploited; the voting system executed as designed. BonkDAO had no execution-time timelock, no multisig override, and no emergency pause mechanism on the treasury. The attacker identified the exchange wallets used to accumulate voting power, and BonkDAO is coordinating with the Solana Foundation, law enforcement, and centralized exchanges including Upbit and Kraken, both of which paused BONK deposits and withdrawals. Recovery is uncertain given the transactions ran through the DAO's own legitimate machinery.