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:

• 
  Ricefarmer🍚 (@RiceFarmerNFT) reported 7 minutes ago

  @Reno_Web3 @binance What exactly does Agent OS do, and how can it help me trade more efficiently?

• 
  X'evolvefull (@evolvefull) reported 8 minutes ago

  @binance As AI agents gain access to trading, wallets and payments, how will Agent OS enforce least-privilege permissions and contain an agent that behaves unexpectedly? Can users revoke access instantly without affecting unrelated funds or positions? #AskBinance

• 
  bekicot (@xbekicot) reported 8 minutes ago

  @binance How does Agent OS actually work with Binance? Is it mainly for trading, or can it help with other things too? #AskBinance

• 
  Ishowsp33t (@ishowsp33t) reported 9 minutes ago

  @binance Looks like a glitch 👀

• 
  Noor Khayal14 (@NKhayal14) reported 11 minutes ago

  Agent OS should automatically detect and resolve #Binance wallet, withdrawal, and transaction issues. An AI-powered assistant could save users time and make crypto much easier. I believe we’re getting closer to this reality with AI + Web3 innovation. 🚀

• 
  katy larreta (@katy_larreta) reported 12 minutes ago

  @Dylan_Wang2 @binance One app won't fix psychology

• 
  Market Edge Metrics (@mktedgemetrics) reported 12 minutes ago

  Critical anomaly in SEI/USDT on Binance: buyer-side net order flow surged to CRITICAL while price barely moved and top-of-book liquidity thinned. Potential impact: limited / no immediate price impact (absorption / "flow without price"). Watch whether follow-through appears or the book gives way if absorption fades. • 🟢 Net orderflow intensity (buyer): 99.93rd pct (robust z ≈ 8.85) → ALERT→CRITICAL at 08:00 UTC • Volume: +45% vs prior hour → 97.6th pct • Trade count: +10% vs prior hour → 97.9th pct • 🔴 Depth within 5 bps: -19% vs prior hour → ~6th pct (depressed) • Price: muted/normal → no matching move • Open interest: +1.4% vs prior hour → 92.5th pct (funding positive) Context: SEI has been in a mild uptrend with low realized vol. OI sits elevated with positive funding, and liquidations were quiet—so leverage isn’t being forcibly reset here. Development: After 06:20 UTC, activity picked up sharply and depth initially marked as deep. From there, depth trended lower into the signal. By 08:00 UTC, buyer-dominant net flow escalated to CRITICAL, yet price stayed largely unchanged. Cross-checks: Volume and trade count rose together, confirming real participation. Relationships flag “flow_without_price” and “activity_without_price.” Depth fell as aggressive flow arrived (“flow_vs_thinning”). Spreads stayed tight despite thinner size—execution risk is in quantity, not access. Interpretation: Evidence is consistent with absorption/pass-through of buy pressure and/or liquidity withdrawal as quotes shrink. A purely “balanced activity surge” is less convincing given the one-sided flow, but can’t be ruled out intrabar. Open questions: Is depth thinning due to passive quote pullbacks or active consumption? If absorption weakens, delayed price displacement may follow; if it persists, chop continues. #SEI #OrderFlow

• 
  sahil Tyagi (@Xnozne) reported 13 minutes ago

  @binance @binance You listed STORJ and millions of people trusted your platform with their hard-earned money. If you can delist it, you can also give the community one last chance. Please support STORJ and consider relisting it. Will Binance respond? 🙏

• 
  Myles🧣 (@Mollygreg25) reported 14 minutes ago

  @binance To protect enterprise capital, does Agent OS support multi sig prompt or webhook verifications before an agent can modify core subaccount parameters? #AskBinance

• 
  Ali Sherief (@Zenul_Abidin) reported 16 minutes ago

  @Phalcon_xyz @binance And Binance seems to be complicit in this! Or maybe they aren't aware, in which case they need to block this immediately and set up more watchers

• 
  Sumit93(❖,❖) (@Sumitb931) reported 19 minutes ago

  If Agent OS is designed to make AI agents more useful in the real world, what is the biggest problem Binance believes Agent OS can solve that today’s AI agents still struggle with and how will users actually benefit from it? #AskBinance

• 
  Jür.Gen.A₿ (@Mairon_1989) reported 25 minutes ago

  @binance MEME ****…KAS ONLY!

• 
  Resh (@RB178r) reported 26 minutes ago

  @binance If developers can connect AI agents to Binance through the Agent OS MCP Server, how does Binance plan to make the connection both simple for developers and granular enough for users to control exactly which Binance capabilities an agent can access? #AskBinance #Binance @binance

• 
  NFA and DYOR ofc (@kandleott) reported 27 minutes ago

  Weekly (33) summary: ● binance started pushing $btc higher to cause FOMO, collect short liquidity and increase revenue while CLARITY ACT is working like natural leverage - in reality its the last miserable push before dropping permanently below monthly ma50 NFA and DYOR ofc🤝

• 
  Burry Graham (@BurryGraham) reported 28 minutes ago

  Why was it delisted? $LOOM (Loom Network) Loom Network raised millions in 2017 with a pitch about plasma scaling for Ethereum, saying they’d build a “sidechain for gaming” where developers could deploy dapps instantly with low fees. The $LOOM token was going to power this new world. By 2019, the vision was clear: nobody actually wanted to build on Loom. Transaction volume stayed in the hundreds per day. Developers that tested the network moved to Polygon (then Matic) instead. Loom’s marketing got quieter. By 2021, the project was basically abandoned, with the team quietly pivoting to infrastructure consulting. $LOOM got delisted from Binance in 2022 and most major exchanges followed. The token still exists, still has a website, but trades for fractions of a cent on OTC markets. The kicker: Loom was technically sound. There was no hack, no fraud, no theft. The scaling solution worked exactly as promised. It just solved a problem nobody had. Nobody wanted to play games on Loom when Polygon existed. Sometimes the reason a token dies isn’t that it failed. It’s that the market moved before anyone noticed. $LOOM $MATIC $UXLINK