Historical Exchange IndexExchange IndexA quiet registry of crypto exchanges, active and gone.

Exchange record

Bitget

Material concerns / known unknowns

Active status and canonical inclusion are lifecycle facts, not safety endorsements. Flags below are derived from reviewed records and do not constitute a proprietary safety score.

Regulatory record
Material regulatory or registration-related record present
Withdrawal / service restriction
Material restriction event recorded
Home / Active / Bitget

Exchange record

Bitget

Seychelles-registered centralized cryptocurrency exchange founded in 2018 and continuing globally. Bitget announced a phased exit from Japan in August 2026; after a September 24 security incident temporarily disrupted withdrawals, the phased restoration of crypto withdrawals, fiat, and P2P/C2C services was completed on October 2.

CEXActive

Registry sequence

Key facts

Launch date
2018-01-01
Death date
—
Years
2018–—
Origin
Seychelles
Confidence
high
Last verified
2026-10-08

URL handling

Preferred action
Use current URL handling based on status below.
URL status
Live verified
Archived URL

Summary

Seychelles-registered centralized cryptocurrency exchange founded in 2018 and continuing globally. Bitget announced a phased exit from Japan in August 2026; after a September 24 security incident temporarily disrupted withdrawals, the phased restoration of crypto withdrawals, fiat, and P2P/C2C services was completed on October 2.

Timeline

Bitget began operating
2018-01-01launchedmedium

Bitget began operating as a centralized cryptocurrency exchange in 2018.

BitKeep joined the Bitget ecosystem
2023-03-22acquiredhigh

Bitget announced a strategic transaction that brought BitKeep into the wider Bitget ecosystem.

Bitget announced the end of services for residents of Japan
2026-08-03shutdown_announcedhigh

Bitget announced that it would cease serving residents of Japan, stop new registrations after 2026-08-03, place affected accounts in close-only mode from 2026-11-01, and forcibly close remaining positions from 2026-12-31 while keeping withdrawals available.

Bitget confirmed unauthorized transfers from hot and warm wallet layers
2026-09-24hackcritical

Bitget said its security systems detected unauthorized transfers at 18:31 UTC affecting a limited portion of its hot and warm wallet infrastructure. The exchange later revised the affected amount from approximately USD 351.6 million to approximately USD 387.5 million after classifying additional affected assets on Zcash and TRON. Bitget later said attackers exploited a vulnerability in a third-party security product to steal intranet access credentials and forge withdrawal commands that bypassed risk verification; private keys were not compromised.

Bitget temporarily suspended withdrawals pending security review
2026-09-24withdrawal_suspendedhigh

Bitget temporarily paused withdrawals as a precaution while reviewing the September 24 wallet security incident. A phased restoration plan was then announced, with BTC withdrawals confirmed open again on September 28 and broader restoration scheduled through October 2.

Bitget began phased withdrawal restoration
2026-09-28reopenedhigh

Bitget confirmed that BTC withdrawals on the Bitcoin and BSC networks reopened at 08:00 UTC on September 28 after additional security validation. ETH, USDT, other supported tokens, fiat and P2P services were scheduled to resume progressively through October 2.

Bitget completed phased withdrawal and related-service restoration
2026-10-02reopenedhigh

Bitget announced that withdrawals for supported tokens other than BTC, ETH, and USDT had resumed together with fiat and P2P/C2C services, completing the phased restoration plan that followed the September 24 security incident.

Evidence

Bitget2026-04-07official_statementmedium reliabilityentityarchive
Bitget—official_statementhigh reliabilitylaunch_datearchive
Bitget—official_statementhigh reliabilitystatusarchive
CoinGecko—database_referencemedium reliabilityentityarchive
Bitget2023-03-22official_statementhigh reliabilityeventarchive
Bitget2023-03-29official_bloghigh reliabilityeventarchive
Bitget2026-08-03official_statementhigh reliabilityeventarchive
Bitget2026-08-03official_statementhigh reliabilityeventarchive
Bitget / Gracy Chen2026-09-24official_socialhigh reliabilityevent
Cointelegraph2026-09-24news_articlemedium reliabilityeventarchive
Bitcoin Magazine2026-09-24news_articlemedium reliabilityeventarchive
Korea Economic Daily2026-09-25news_articlemedium reliabilityeventarchive
Bitget2026-09-25official_socialhigh reliabilityevent
Bitget2026-09-24official_statementhigh reliabilityeventarchive
TokenPost2026-09-25news_articlemedium reliabilityeventarchive
Bitget2026-09-28official_bloghigh reliabilityeventarchive
Bitget2026-10-02official_bloghigh reliabilitystatusarchive

Related records

Notes and record state

Record note
On 2026-09-24 at 18:31 UTC, Bitget detected unauthorized transfers affecting a limited portion of its hot and warm wallet layers. The estimated impacted amount was revised to approximately USD 387.5 million. Bitget's investigation states that attackers exploited a vulnerability in a third-party security product to obtain intranet access credentials and forge withdrawal commands; private keys were not compromised and cold wallets were not affected. Independent XRPL analysis reports 102,976,680 XRP transferred from Bitget-labeled wallets during the incident. Bitget says the vulnerability was remediated and the incident contained. BTC withdrawals resumed on 2026-09-28, ETH on 2026-09-29, USDT on 2026-09-30, and on 2026-10-02 Bitget confirmed that withdrawals for other supported tokens together with fiat and P2P/C2C services had resumed, completing the phased restoration plan. HEI therefore returns the global exchange status to active. Asset tracing, recovery, and post-incident security work may continue without implying an operational limitation. Operational restoration was rechecked against Bitget's October 2 completion notice on 2026-10-08.
Revision state
Records may be incomplete, approximate, contested, or revised as better evidence becomes available.
This record may be incomplete or revised. Dead-side entries prefer archived URLs over original domains. Dates, causes, and classifications may change when stronger evidence becomes available. Contact / corrections

Navigation

Registry
Active-side
Contact / Corrections
GitHub Issues