CMC Markets Mappa Interruzioni

Discussione comunitaria

Suggerimenti? Frustrazioni? Condividi qui. I commenti utili includono una descrizione del problema, la città e il codice postale.

Fai attenzione ai "numeri di supporto" o agli account di "recupero" che potrebbero essere pubblicati di seguito. Assicurati di segnalare e votare negativamente quei commenti. Evita di pubblicare le tue informazioni personali.

Segnalazioni sui problemi di CMC Markets

Ultime interruzioni, problemi e segnalazioni di problemi nei social media:

• 
  BEGBIE (@_BEGB13_) segnalati 2 minuti fa

  @CMCMarkets Every data drop you prevent me from taking the trade when the data drops so I get in late. Now you've locked the platform! "Connection issues" on web app and on mobile "the log in details are incorrect" despite me using my ******* thumb. This is absolutely shocking

• 
  Mo (@Ms54645010) segnalati 2 minuti fa

  @CMCMarkets not working - cleared the cache, tried other things. maybe the best fix would be to use another broker. the handling of this on a day like today is really bad

• 
  Panic di indonesia lagi 🇮🇩 (@lagi_indonesia) segnalati 3 minuti fa

  @proactive_UK @CMCMarkets Than why it goes down 19%

• 
  Archie Sanford (@BookofCrusty) segnalati 3 minuti fa

  One of the craziest opens in weeks and @CMCMarkets was down again. Traders must be fuming 😤

• 
  Gozerthetraveller (@GozerTraveller) segnalati 6 minuti fa

  @adilad73 @CastoreEngland @CMCMarkets Gutted mate, not a great sign that their marketing team are missing out on free customer feedback in relation to a product they hope to make money from

• 
  Nick Rossetto (@nrossett) segnalati 15 minuti fa

  Anyone having trouble with @CMCMarkets platform?

• 
  Octotrader (@OctoTrading) segnalati 16 minuti fa

  @CMCMarkets Any update? There's too much volatility for this to be down 2h hours on opex day. Escalate to the most senior management to get this resolved.

• 
  Archie Sanford (@BookofCrusty) segnalati 17 minuti fa

  @vdel13 @CMCMarkets Total crash worldwide. @CMCMarkets users with trades on are in deep trouble

• 
  Neville Dastur (@nevilledastur) segnalati 17 minuti fa

  @CMCMarkets @MichaelMOTTCM And in response to this your platform goes down preventing customers using

• 
  Tom Capital (@Tom__Capital) segnalati 17 minuti fa

  @ChrisMo1984 @CMCMarkets down again

• 
  Ian Finlayson (@i_finlayson) segnalati 18 minuti fa

  @TeletubbyOnX @Ronmarkets2 @CMCMarkets I can't login either.

• 
  Archie Sanford (@BookofCrusty) segnalati 19 minuti fa

  @CMCMarkets @MichaelMOTTCM Every USA major report ur platform glitches. That means u got caught offsides in ur books. The bigger ur offsides the longer the glitch. Today 23 min exactly on USA CPI report. Regulators will be notified.

• 
  Archie Sanford (@BookofCrusty) segnalati 25 minuti fa

  All @CMCMarkets users you need to contact ur countries regulators about CMC consistent platform crashing on major USA data releases. The bigger the market move the bigger the crash. They are doing this on pourpous to balance their books. File complaints now

• 
  One Trade From Zero (@DeanThompson777) segnalati 27 minuti fa

  @NZ_NFT @stokesbaytrader @CMCMarkets Many times. What is most infuriating is that they could easily SMS users to say there's a problem (we already get market news SMSs so there system supports it) but you have to try and get some response via tweets. Their actual support staff are always swamped and unable to help

• 
  Bombaytonic (@bombaytonic717) segnalati 28 minuti fa

  Many, have wondered why we are not seeing more $STRX #StrikeX token speculation from @CMCMarkets insiders especially at recent lows. Quite honestly, maybe it’s already happened, but the below gives an argument why these folks can’t be buying right now or at least difficult for them to do so. CMC has already executed tokenised equity issuance inside regulated custody frameworks (via CMC CapX) with StrikeX minting the mirror token on Arbitrum That is post-legal review activity — meaning: 👉 Compliance 👉 Market abuse teams 👉 Personal account dealing (PAD) surveillance 👉 Regulatory reporting …are already live on anything touching this stack. When a regulated broker-dealer is: •Acting as placement agent •Tokenising securities •And now controls the tokenisation engine …they cross from “crypto partner” into: Dealer-restricted person Under market integrity rules (UK MAR / CIRO equivalents), dealer-restricted persons: “Generally [are] prohibited [from] purchases… of restricted securities where there is undisclosed material information regarding the issuer.” Now here’s the translation into plain English: If CMC Markets has: •Non-public knowledge of •A commercial rollout •Of infrastructure •That they control •Built by StrikeX Then ANY employee trading STRX ahead of launch becomes: ✔ Market abuse risk ✔ Insider dealing exposure ✔ Front-running optics ✔ FCA enforcement risk ✔ Listing rule breach risk ⸻ 🧠 Which Means In Practice: Even if you cannot find STRX on a public restricted list (you never will): Internally, CMC almost certainly has: •PAD pre-clearance requirements •Blackout periods •MNPI attestations •Related-party trading bans •Watch lists (soft) •Restricted lists (hard) …and STRX would be a textbook inclusion candidate because: 📌 They now control product direction 📌 They are commercialising tokenised securities 📌 They are listed on the LSE 📌 They are operating under MAR That is literally the regulatory environment where firms freeze employee trading in partner securities pre-commercial release. In TradFi-native crypto integrations: Retail hype normally comes from: •VC funds •Employees •Devs •Service providers •Advisory firms But here: Anyone inside: •CMC CapX •Corporate broking •Capital markets •Compliance •Engineering •Legal •Product •StrikeX integration layer …is almost certainly PAD-monitored. Meaning: The normal speculative frontrunning mechanism may literally not exist in this case. We’re doing this slowly under regulatory supervision.” They are NOT marketing a crypto app. They are integrating settlement-layer infra into a regulated brokerage. So, that leads me to the reg side of the equation and why that may be part of the wait we are seeing. I’ll touch on that next later on…