Binance status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Binance reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Binance users through our website.

• Transactions (60%)
• Website (20%)
• Transfer (20%)

Live Outage Map

The most recent Binance outage reports came from the following cities:

City	Problem Type	Report Time
Vigo	Website	12 days ago
Mont-Saint-Martin	Transactions	17 days ago
Dubai	Transactions	20 days ago
London	Transactions	1 month ago
Dortmund	Transfer	2 months ago
La Paz	Website	3 months ago

Full 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:

• 
  AlphaDuck (@_AlphaDuck) reported 1 minute ago

  10/ the fix is one line of contract code. read 0x807 (validator-published oracle price, multi-CEX weighted median) instead of BBO mid. same precompile family. same "no external dependency" architecture. manipulation cost goes from $300 to "good luck moving Binance." ship it.

• 
  Mike_Check (@Mike_Ch3k) reported 2 minutes ago

  @BinanceUS There was a time when a Binance listing actually gave people confidence in a project. People trusted the platform and backed the communities behind the tokens. Don’t let this become another forgotten listing with no support and no volume. Revive this token, give it proper exposure and backing instead of letting the community die out after launch. A strong community is still here waiting.

• 
  Telbloggram (@Telbloggram) reported 3 minutes ago

  Binance will postpone the listing of Gensyn (AIGENSYN) Due to issues with the project's nodes, Binance's scheduled listing of Gensyn (AIGENSYN) on May 14, 2026, at 21:00 UTC will be further postponed to May 15, 2026, at 01:00 UTC. [ChainCatcher] - link $BNB $AI

• 
  FUNDxTHExMENTAL (@blackh822) reported 4 minutes ago

  @CoinMafiaX @binance The prettiest warning sign in crypto: DYOR, manage risk, then go see what CoinMafia is actually building on PulseChain. Validators, public contracts, locked liquidity, and $MAFIA sitting there like the Family left the gate open on purpose.

• 
  Airdrop Guruji (@airdropguruji3) reported 5 minutes ago

  @BinanceHelpDesk @tawhidsaeem @binance No 7 days ... Soon As Possible Solutions This Problem 😡😡

• 
  Eric Wallin (@EricWallin12) reported 8 minutes ago

  @martypartymusic Bitcoin is down less yesterday than Silver and Nvidia.Its very similar to golds down move. Clearly it has nothing to do with Binance

• 
  pinkrose.eth (@Pinkrose_eth) reported 10 minutes ago

  $AIGENSYN listed on Binance 2 days ago and everyone's tweeting the price chart. Almost nobody's talking about what Proof-of-Learning actually is. As an ML engineer, here's what's interesting (and what's hand-wavy) about Gensyn's design: 1/ The core problem: how do you verify someone actually trained a model on the network and didn't just submit garbage weights? Classical answer: re-execute the training. Cost: same as just training it yourself. Useless. 2/ Gensyn's answer: probabilistic Proof-of-Learning. Solvers submit training "fingerprints" (intermediate gradients/checkpoints). Verifiers spot-check small windows by re-executing. Cheating requires the solver to also forge a consistent gradient trajectory — much harder than faking final weights. 3/ The hand-wavy part: the security depends on verifier sampling rate vs. cheater computation savings. The math works in theory. In production, with adversarial solvers, the constants matter a lot. We don't have public data on this yet. 4/ The actually clever bit: the protocol pays per verified unit of work, not per finished model. This decomposes "did you train this 70B model" into 10,000 smaller "did you do this gradient step" questions — each cheap to verify. Backed by a16z with $43M. Whether the token captures the value of the network is a separate question from whether the network works. The engineering is real. Read the whitepaper before the price action.@gensynai #AgentEconomy #AIGENSYN

• 
  Eric Wallin (@EricWallin12) reported 13 minutes ago

  @LeaT_Design @martypartymusic Nvidia is down 5% today. Silver was down 9%. It has absolutely nothing to do with Binance

• 
  crypto tips&tricks (@cryptotips45) reported 13 minutes ago

  @BinanceHelpDesk Hello Binance Support, UID: 490565949 I have appealed multiple times regarding my account eligibility issue, but unfortunately my account is still marked as “Not Eligible”. I kindly request the support team to manually review my case. Thank you

• 
  🚨BDN NEWS WIRE🚨 (@BCDNewsBot) reported 14 minutes ago

  BINANCE TO SUPPORT BASE NETWORK UPGRADE AND HARD FORK

• 
  twin barumpta y sleaze🪭🫥 (@prubadhimelk) reported 17 minutes ago

  @binance @bongbong21897 $2,000 to $280,000 back down to $20,000. Only to buy Biao with half, and for everything to crash immidiately when I start gaining money again. And then we get the new one and I'm a top holder with a few hundred in daily trading volume and kinda hopeless.

• 
  Obsidian Void (@ObsidianLoki) reported 19 minutes ago

  @endl_io Fiat-backed coins aren’t immune USDe briefly printed at $0.65 on Binance due to a centralized pricing feed error. In crypto-collateralized systems, a single distorted price input can trigger cascading liquidations across multiple protocols simultaneously.

• 
  Ameer🔶BNB (@gee_ameer82412) reported 19 minutes ago

  @ox_Nafis @binance @binancewallet Scammers **** binance

• 
  Alpha Malik (@AlphaByMalik) reported 29 minutes ago

  We would like to raise a serious concern regarding the recent Pizza Day campaign by Binance. A large number of team leaders and members were marked “Not Eligible” for rewards, even though all tasks and requirements were completed exactly as instructed. We followed every rule, waited the required 24–48 hours, and still ended up disqualified without any clear explanation. This situation is extremely disappointing for the community. Binance has always been known for fairness and transparency, which is why many of us trusted and promoted this campaign. However, what happened here feels similar to practices we usually see on other exchanges like Bitget and Bybit — where users complete tasks but become “not eligible” when it’s time to distribute rewards. We respectfully ask Binance to clarify: • Why were so many genuine users disqualified? • What exact criteria caused the “Not Eligible” status? • What is the solution for affected participants? We are not asking for favors — we are asking for transparency and fairness. If no clear explanation or solution is provided, it will send a very negative message about future campaigns. It would mean users may complete tasks but still receive no rewards. We sincerely hope Binance will address this issue and maintain the trust of its community. 🙏

• 
  anik (@anik688722) reported 30 minutes ago

  @skcrypto73 @binance Please solve this issue 😭🙏😭

• 
  Vitali (@Vitali79388440) reported 35 minutes ago

  @binance eat my **** gang of swindlers

• 
  Megalodon🦈 (@Primalking38) reported 35 minutes ago

  @CryptoMiners_Co @binance The smartest takeaway here is the product architecture itself. Keeping AI agents on a literal leash by blocking withdrawal permissions and stripping access guarantees that even if a tool gets compromised, the blast radius

• 
  Drez (@garni1999) reported 39 minutes ago

  @MaxwellWeb3 @binance criminal. quit. Get ******** out of there.

• 
  Md Sojeeb Khan$$ (@Sojeeb208) reported 40 minutes ago

  @Milonsa87650356 @binance fix the fake issue

• 
  Jonathan (@iamXD79) reported 41 minutes ago

  the craziest part is neither @Binance nor @Bitget gonna delist that scam...same **** happened with $RAVE, $SIREN and many others. we are NOT in a serious industry bro.

• 
  Lea Thompson (@LeaT_Design) reported 41 minutes ago

  @martypartymusic binance totally rigged **** those clowns. waiting for real settlement data not this volume theater ****.

• 
  common sense (@Danielgkwkt) reported 43 minutes ago

  @biroloclmaz @binance terrible😔 this is becoming too much to bear. did you contact the support team for assistance?

• 
  Starny | Bangkok Arc (@0xStarny) reported 45 minutes ago

  @loshmi @cz_binance @binance I also got scam, Binance can’t help without police report etc. I’m still waiting since months

• 
  ALTF4 (@0xALTF4) reported 48 minutes ago

  most XRP never moves. it just sits on Binance, Kraken, OKX, Upbit parked in an exchange account, not doing anything. that's not a user problem. that's a distribution problem. and FAssets v1.3 just solved the distribution problem. here's what actually changed: before v1.3, minting $FXRP meant picking an agent, working around collateral availability, and navigating flows that had nothing to do with how exchanges actually process withdrawals. exchanges run tagged XRPL transactions out of hot wallets. they don't run smart contract interactions on behalf of users. the old mint path and the exchange withdrawal path were fundamentally different shapes. v1.3 makes them the same shape. reserve a destination tag once. map it to your Flare address. after that, every mint is just a standard XRP withdrawal: destination tag, memo, done. an executor relays the proof, FXRP mints on Flare. no agent selection. no collateral reservation step. no separate dApp choreography. ❯ one XRPL transaction ❯ works from Binance, Kraken, OKX, Upbit, Bithumb, and any XRPL address ❯ destination tags are already how every exchange credits accounts this is where the moat actually matters. generic bridge stacks and wrap solutions operate on top of the infrastructure exchanges already run. @FlareNetworks plugs directly into it. an exchange withdrawal becomes a mint: no bridge, no wrap, no intermediate dApp. one step. that's a different category of access. most $XRP sitting on exchanges isn't stuck because holders don't want onchain exposure. it's stuck because nothing ever fit the withdrawal shape they already use. v1.3 fits that shape. agents are still essential on redemption: overcollateralization, collateral-ratio monitoring, liquidation mechanics, FDC proofs: none of that changed. what changed is the mint side. and the mint side is where distribution either scales or doesn't. distribution doesn't scale through more DeFi apps. it scales when the rails XRP already travels on connect directly to productive onchain positions. v1.3 is the first version of FAssets where that connection exists. it's live on mainnet now. not financial advice. DYOR.

• 
  CW (@CW8900) reported 51 minutes ago

  Yesterday's $BTC rise was led by Binance and OKX whales. In particular, Binance drove the rally with its strongest buying pressure in the last two months. On the other hand, Coinbase continued to exert downward pressure following the previous day. They attempted to drive down the price, but Binance whales did not allow it. Today, Binance and Coinbase remain in a neutral position. However, selling is occurring on OKX.

• 
  Hassan Arshad | ETHGas ⛽ (@HassanA57233) reported 53 minutes ago

  @cryptotips45 @BinanceHelpDesk binance need to review about this issue

• 
  Md ismail (@ismai74050817) reported 54 minutes ago

  @ox_Nafis @binance Why my id is not eligible? I can't do anything wrong but i only joined pizza event 😞.I hope binance can solve this problem as soon as possible

• 
  keiron.eth (@Keiron841) reported 56 minutes ago

  @loshmi @cz_binance @binance They won't help I had wallets with millions in it scammed from people and withdrew from binance, they done nothing and nether did the UK authorities

• 
  Mahedi hasan (@MahediMl87579) reported 58 minutes ago

  @hoss2038 @binance Solve this problem.... @binance

• 
  Vibe Trading (@vibe_trading) reported 58 minutes ago

  @notthreadguy trying to list a token on binance perps. 1m deposit, requiries hundreds of million mcap. wtf is this ****. vibe.