Mapa de Fallos de GDAX
El siguiente mapa de fallos muestra las ubicaciones más recientes en todo el mundo donde los usuarios de GDAX informaron sus problemas e interrupciones. Si tiene un problema con GDAX y su área no aparece en la lista, asegúrese de enviar un reporte a continuación.
El mapa de calor anterior muestra dónde se agrupan geográficamente los reportes más recientes enviados por usuarios y de redes sociales. La densidad de estos informes se representa mediante la escala de colores, como se muestra a continuación.
Usuarios de GDAX users afectados:
GDAX es una casa de cambio de criptomonedas que ofrece a las instituciones y profesionales la capacidad de comerciar con una variedad de monedas digitales como Bitcoin, Ethereum y más en un intercambio regulado basado en los EE. UU. GDAX es propiedad y está operado por Coinbase.
Lugares Más Afectados
Reportes de fallos e interrupciones de los últimos 15 días se originaron desde:
| Lugar | Reportes |
|---|
Discusión comunitaria
¿Consejos? ¿Frustraciones? Compártelos aquí. Los comentarios útiles incluyen una descripción del problema, la ciudad y el código postal.
Tenga cuidado con los "números de soporte" o las cuentas de "recuperación" que se pueden publicar a continuación. Asegúrate de informar y votar negativamente esos comentarios. Evite publicar su información personal.
Reportes de Fallos de GDAX
Los últimos problemas e interrupciones reportados en social media:
-
Grok (@grok) reportó@nexpotus @FitLikeMummy @BTC_Archive Bitcoin did briefly flash crash to $0.06 on GDAX (Coinbase) in April 2017 due to a system issue, but it was from ~$1,200, not $10k. The 2011 Mt. Gox hack saw it drop to $0.01 from $32. Stink bids are smart—always good to have them ready!
-
Anoop (@anoop2822) reportó@BrentJo77143717 @Bitcoinsensus I remember that day but it was kinda glitch on gdax’ part. The organic correction was from $420 to $140 and then back to new ATH which took another 6 months or so i believe
-
AQPulse (@AQPulse) reportóThis is not “cheap.” This is failed structure. $AMZN broke out, failed the reclaim, and is now back inside the long-term weekly channel with the GDAX cross rolling bearish. When price re-enters a broken channel instead of escaping it, downside extension toward the lower boundary becomes the more credible path.
-
tekkaadan (@tekkaadan) reportó@tmuxvim GDAX was ******* atrocious and at that time, working in crypto was very exciting. There was purpose if what people were doing.
-
Haris A. Maxwell CryptoScam//investigator 🕵️ (@haris43516539) reportóCaution,,,,,,,#gdax and #CEXIOPROLTD highlights concerns about withdrawal visibility, with some users finding transaction records difficult to follow. 📩 If you need help, contact privately for support.
-
CryptoFreedom CEO (@3NiftyProducer) reportóThis is not the 1st time that crypto exchanges have witnessed flash crashes and spikes which have previously caused anger and refund requests from affected customers. For instance, a flash crash on GDAX in Aug 2017 saw Ether prices drop to as low as $0.1 due to a customer error
-
Rai (@Rai_A_Mujahid) reportó@brian_armstrong @brian_armstrong I miss the good ol GDAX days. If you truly believe in the long term, then fix your ludicrous fees! Otherwise your stock is going 6 ft under….
-
Grok (@grok) reportó@stansilver2024 @saylordocs Researched claims: No evidence of personal "inside wash trading" or criminal acts by Brian Armstrong. Coinbase (as company) settled 2021 CFTC case for $6.5M over 2015-2018 bot/employee self-trades inflating volumes on GDAX (e.g., one ex-staffer did ~99% fake LTC trades). Called reckless, not intentional; no customer harm, no guilt admitted. Ongoing civil shareholder suits target exec disclosures on custody/AML/listings and 2021 stock sales (internal probe cleared them; no wash trading alleged). Standard fintech scrutiny, no convictions.
-
HMS RΞΞpΞr 🇫🇷 (@Fernjosh1) reportó@zhusu Not doing **** on Gdax :(
-
Mohammad Ahamad (@monaji99) reportó@Nyree344 @RobertOstler I just sent him a message, I am so tired of the slow profits i make from Binance and Gdax.
-
Russell(SatoshiSpirit) (@bitcoinXtalk) reportó@w_s_bitcoin @raw_avocado For sure, 100% true today and for most of time, but for a very brief period I was personally trading on Coinbase/GDAX and had bought 1 BCH before the fork for a little under $300. After the fork, I tried to sell when it hit parity with BTC on GDAX it hit $9000/BCH(I put a sell order in for a little under the global average top ≈ $4,00) but as soon as I did it failed to execute, they froze trading across all major exchanges. This proved to me that exchanges have a “lever” they can use, and it’s the same one that was used to suppress GME as well, so they have final veto power in a fork war by manipulating price and availability to trade(delist or refuse to list even if market demanded it) and they ultimately decide which side of the fork gets the BTC ticker (the one with most accumulated PoW), as miners follow price and price easily manipulated by a high margin in a short period(ie: BCH went from $300 to $9000 then back down to $500 in 24hours bc exchanges using this “lever” to flash crash the price of any new fork by freezing trading, allowing smaller exchanges and OTC trades to bring the price down while no one else can trade. I ended up making ≈ 0.35 BTC from 1x $300 BCH.
-
Viccenzo Benatti (@vih_skare) reportó@gregboy02 Hmmmm, I just sent him a message, I am so tired of the slow profits i make from Binance and Gdax.
-
C◎mfy King 🫡 (@Kingpin_0x) reportóHonestly think this is a because of a technical issue they are either too lazy or too cheap to fix. Very few noteworthy updates since it was GDAX. API is dog **** and no tax reporting features. On to Binance US we go.
-
Kevin Costello (@KevinCo31833801) reportó@gdax Having trouble with moving cash from coinbase to coinbase pro. Tried this over and over and not working. Also your support page when filling everything out then asks for code sent to email. You try to go back to support page and it vanishes. Never works.
-
OpenCryptoPortfolioTracker.org (@taoteh1221) reportóNevermind, looks like you guys just took your old GDAX endpoint down, or that SSL certificate expired.