outage

Coinbase released a retrospective report on the large-scale service interruption event on May 7, 2026.The outage lasted approximately 8 hours, with full recovery taking about 12 hours. During this time, trading, deposits, withdrawals, and most core services were unavailable or severely degraded. Coinbase stated that the outage was caused by multiple cooling units failing simultaneously in the cooling system of a data center in one availability zone (use1-az4) in the AWS us-east-1 region, triggering cabinet thermal protection shutdowns, which led to EC2 instances and EBS volumes going offline, affecting multiple internet services.During the recovery process, the Coinbase trading matching engine lost quorum due to the cluster architecture deployed in a single AWS data center losing most nodes. It required urgent code adjustments and the reconstruction of a new node group to restore operation, gradually restarting market trading during the recovery.Additionally, the AWS-managed Kafka (MSK) service experienced control plane failures, preventing the automatic re-election of partition leaders, further blocking quotes, fees, and some settlement and data flow systems, which expanded the overall impact.After manual partition migration in collaboration with the AWS engineering team, the system gradually returned to normal. Coinbase stated that this incident exposed its shortcomings in cross-availability zone automatic switching capabilities and disaster recovery for managed middleware. The company will upgrade its cross-region hot backup architecture, strengthen regular failure drills, and migrate the Kafka system from dual availability zones to a three availability zone deployment, while also working with AWS to advance root cause fixes and improvements.

According to the official announcement from Sui Network, the Sui mainnet has resumed normal operation, and transaction processing and network activity have both returned to normal. The official disclosure states that the two network outages that occurred yesterday and the day before were related to an interaction issue between the "Address Balances" feature introduced in version 1.72 and the Gas billing logic. The Sui core team indicated that the fix deployed yesterday was only a temporary measure aimed at quickly restoring network operation, but this solution carried a known and low-probability risk of outage. Today, the network triggered a variant of the known issue, causing the mainnet to pause again. Currently, the validators have completed the deployment of a long-term fix, and the official claims that the known issues caused by the original vulnerability have been thoroughly resolved, with the network now operating normally. The Sui team stated that they will release a more detailed incident review report in the future, explaining the cause of the failure and the repair process.

Coinbase CEO Brian Armstrong posted on the X platform that there was a service outage at Coinbase yesterday, which is absolutely unacceptable. The root cause was multiple cooling units at the AWS data center failing simultaneously, leading to overheating in one server room. Most of Coinbase's systems are designed with redundancy to handle the failure of a single availability zone, and they did operate normally last night.However, centralized exchanges were not spared, as their architecture is specially optimized for low latency and customer co-location, making it difficult to simultaneously ensure fault tolerance at the availability zone level. While enabling the exchange to withstand availability zone failures would introduce latency issues and disrupt customer co-location, the team will reassess these trade-offs to at least ensure that when a switch to a different availability zone is needed, the duration of the outage can be significantly reduced. He expressed gratitude to the AWS and Coinbase teams who worked through the night to repair the issue and promised to release a detailed technical explanation later.

Coinbase stated that the system detected a high error rate in multiple services, subsequently pinpointing the failure to the AWS US-EAST-1 availability zone use1-az4. The Coinbase system originally had single availability zone fault tolerance, but this failure affected multiple availability zones, resulting in a prolonged interruption of core trading services.The main issues have now been fully resolved, and the team will conduct a comprehensive analysis of this incident and provide further updates after AWS releases the official review report.

As the Ugandan government cut off nationwide internet access during the presidential elections, the encrypted communication app Bitchat became one of the most downloaded apps locally. The Uganda Communications Commission confirmed that the internet shutdown took effect at 6 PM local time on Tuesday and will continue throughout the election period.Reports indicate that Bitchat relies on Bluetooth Mesh networks to enable encrypted communication without the internet, and it has simultaneously topped the download charts on both the Apple App Store and Google Play in Uganda. Meanwhile, several VPN apps also ranked high in downloads, indicating a significant increase in local demand for information access ahead of the elections.The Ugandan government stated that the internet shutdown aims to prevent the spread of false information during the elections, but opponents argue that this move could restrict the flow of election-related information. The executive director of the Uganda Communications Commission had previously stated that there would be no internet shutdown, but ultimately, the measures were implemented. As of early January, it has been disclosed that over 400,000 users in Uganda have downloaded Bitchat.This marks the third consecutive time Uganda has implemented a nationwide internet shutdown during presidential elections. Similar actions occurred during the elections in 2016 and 2021. Reports also mention that Bitchat has been widely used in various countries under conditions of internet restrictions or sudden disasters in recent years, gradually becoming an alternative communication tool in offline environments.

The Ethereum L2 network Starknet released an analysis report on the short-term mainnet outage that occurred this Monday, stating that the cause of the incident was the inconsistency between the execution layer (blockifier) and the proof layer: under specific cross-function calls and rollback combinations, the execution layer incorrectly recorded a state write that had been rolled back, leading to abnormal transaction execution. The related transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity being rolled back.This is the second major interruption since 2025, following a September incident where a sequencer vulnerability caused an outage of over 5 hours and rolled back about 1 hour of on-chain activity.

CyrusOne confirmed that its data center in Aurora, Illinois, experienced a market outage operated by the CME Group for over 10 hours due to human error.On-site staff and contractors failed to drain the cooling towers according to standard procedures before the arrival of low temperatures, ultimately leading to an overload of the cooling system and a rise in temperature. CyrusOne is jointly owned by KKR & Co. and Global Infrastructure Partners, and this incident has raised concerns about the reliability of financial market infrastructure. Previously, on November 28, trading in commodity futures at the CME Group was suspended.

Due to a Cloudflare service outage, both OpenSea and Upbit websites are experiencing downtime, showing a "500 Internal Server Error" message.

According to an analysis report published by Cloudflare's official blog, the large-scale outage on November 18 was not caused by an external network attack, but rather by an erroneous configuration file generated after a database permission adjustment, which led to anomalies in the core proxy system. This triggered interruptions in multiple products, including CDN, security services, Workers KV, Turnstile, and Access, marking the most severe incident since 2019.The report noted that in the early stages of the incident, the team mistakenly assessed it as a DDoS attack, and ultimately completed the fix by rolling back to an old configuration file. The related services were fully restored at 01:06 AM Beijing time on November 19. Cloudflare described this outage as "unacceptable" and will accelerate the improvement of system resilience.

ChainCatcher news, Binance posted on social media that there seems to be a contract outage at Binance, and it is unable to update data in real time.

ChainCatcher news, according to The Block, Hyperliquid experienced approximately 20 minutes of trading execution failure on July 29, causing its native token HYPE to drop by 3.75% to $43. The platform officially confirmed on Discord that services have been restored, and the cause of the failure is still under investigation.During the outage, the trading application BasedApp, built on Hyperliquid, was also affected. Hyperliquid is a perpetual contract exchange based on its self-developed HyperEVM chain, known for its low fees and high performance.

ChainCatcher news, according to official information, Binance has stated that it is aware that most areas in Spain are currently experiencing temporary power outages. Although the Binance platform is not affected, some users may encounter difficulties accessing online services due to local infrastructure issues.Binance advises affected users to carefully check all open positions as soon as possible and manage related risks in a timely manner.

ChainCatcher message, Binance officially stated on platform X that due to a temporary network interruption at the AWS data center, certain services on the platform have been affected. To ensure safety, Binance has suspended withdrawal services. The team is working closely with AWS to resolve this issue as soon as possible. Further updates will be shared promptly.

ChainCatcher news, according to Jinshi reports, on Monday, Elon Musk's social media platform "X" received reports of outages from thousands of users in the United States and the United Kingdom.According to the outage tracking website Downdetector.com, during the first outage, over 21,000 people in the U.S. reported issues with the platform, while 10,800 people in the U.K. reported problems. The platform seemed to return to normal around 2:30 AM Pacific Time. Overall, X was down for about 45 minutes. However, later that day, X experienced another outage. According to Downdetector.com, at 6:45 AM Pacific Time, there were over 8,000 reported incidents of issues on the site. Like the previous outage, it resumed service after about 45 minutes.The cause of the interruption is currently unclear, and X has not yet responded.

ChainCatcher news, OpenAI has confirmed that its artificial intelligence chatbot ChatGPT is currently experiencing a global outage, preventing users from accessing it. This issue also affects the integration with iOS 18.2 and Siri. According to OpenAI, the company has identified the cause of the outage and is actively working on a fix. While their goal is to restore ChatGPT's functionality as soon as possible, no specific timeline for recovery has been provided. (Jinshi)Previous news, OpenAI stated that ChatGPT is currently experiencing an interruption. The issue has been identified, and efforts are underway to roll out a fix.

ChainCatcher message, Sui officials posted on the X platform stating, "Between 1:15 and 3:45 PM Pacific Time on November 21, 2024, the Sui mainnet experienced downtime. All validators fell into a crash loop, preventing any transactions from being processed. The Sui network suffered its first network failure due to a bug in the congestion control code. This bug originated from a recent upgrade to the congestion control code, aimed at better utilizing shared objects. Sui contributors quickly deployed a fix and restored normal network activity within 2.5 hours."

ChainCatcher message, starting around 18:30 on October 3, hundreds of Telegram users reported issues with connecting to Telegram servers. The most reported problems include issues with sending and receiving messages, as well as other connectivity issues on the application.It is reported that this connectivity incident has affected users in countries such as Ukraine, Belarus, Poland, Kazakhstan, Russia, the Netherlands, and Germany.

ChainCatcher news, Tonk Inu stated that the recent Ton network outage may be due to the unusually high network activity caused by the market's enthusiasm for the new DOGS memecoin.Previous news, the Ton network was down, with no blocks produced for nearly 3 hours.

ChainCatcher message, Conduit released a post-mortem analysis report regarding the previous downtime incident of Degen Chain. On May 10, Conduit increased the batch size for Degen and Proof of Play Apex to 10MB to reduce costs, which delayed the time for data to be batch published from these networks to their parent chain. On May 12, this configuration was reverted to fix the batch publishing. This led to reorganizations on both networks, as the batch was published after a 24-hour forced inclusion window. Arbitrum Nitro will insert any inbox messages before any transactions in the batch and replay those transactions using the new timestamps.After the reorganization, nodes returned with corrupted databases due to their depth not being well handled by geth. This required resynchronizing the data directory from genesis. The synchronization time for each network exceeded 40 hours, with a replay rate of about 100M gas/s. Once the nodes were resynchronized, Conduit attempted various transaction replay strategies, although not all transactions could be recovered, as some relied on precise timestamps.After negotiating with each rollup team, Conduit discussed and concurrently tried various strategies to bring the network online and restore the state prior to the reorganization. The Degen Chain network was restored online 54 hours after the outage. The Apex chain of Proof of Play was restored around the same time but became available to the public only after implementing another recovery solution.Conduit stated that it has improved alerts and monitoring for the Orbit chain to cover such situations and is committed to working with Offchain Labs to enhance the observability of all Orbit chain operators. The team will continue to invest in and research mechanisms to better simulate mainnet conditions and transaction payloads in a testing environment. The Degen Chain Explorer is now displaying the latest status of Degen Chain normally.

ChainCatcher news, Coinbase Support posted on X platform that earlier this week the platform experienced a brief outage caused by an error related to the Coinbase Card rewards service. Due to this bug, some Coinbase Card users saw incorrect points displayed in their accounts.All customers' funds are safe. This was not caused by any security issue. The team will continue to work on mitigating such issues in the future.