# Outage Articoli collegati

Il Centro Notizie HTX fornisce gli articoli più recenti e le analisi più approfondite su "Outage", coprendo tendenze di mercato, aggiornamenti sui progetti, sviluppi tecnologici e politiche normative nel settore crypto.

Base Halts for Two Hours: A Single Invalid Block Reveals the Centralized Reality of L2s

Base, an Ethereum Layer-2 Rollup, experienced a two-hour network outage starting around 00:03 UTC on June 26. The halt was caused by a consensus issue that led to an invalid block being sequenced, which prevented the generation of new blocks after block 47806542. The team identified the problem, restored block sequencing by 01:51 UTC, and confirmed full recovery of ecosystem infrastructure synchronization shortly after. This incident highlights the operational reality for many L2s: while they leverage Ethereum for security and data availability, their day-to-day usability heavily depends on their sequencer and internal systems. Base employs a high-availability sequencer system with one active leader, but this setup did not prevent the outage when a consensus-level problem arose. This follows a previous 33-minute outage in August 2025 related to a faulty sequencer handover process. The downtime occurred near the scheduled activation window for the "Beryl" network upgrade, which has since been postponed. Beryl introduces the native B20 token standard, among other improvements. The incident has sparked renewed discussion about Base potentially launching its own network token in the future, shifting the conversation from mere speculation to questions about how a token might relate to sequencer decentralization, governance, and accountability in such failure scenarios.

Foresight News06/26 06:42

Base Halts for Two Hours: A Single Invalid Block Reveals the Centralized Reality of L2s

Foresight News06/26 06:42

GitHub, Transfixed by AI

On the night of February 9th, GitHub suffered a major outage caused by a simple configuration change—reducing a cache refresh interval from 12 to 2 hours—that triggered a cascade of failures. This was not an isolated event, but part of a broader pattern. In early 2026, GitHub experienced at least 8 major incidents, failing to meet its promised 99.9% availability. These outages stemmed from structural issues: explosive growth in load, tight service coupling, and insufficient protection against abnormal traffic. This unprecedented load is driven by AI Agents. In 2025, GitHub handled ~1 billion commits. By 2026, weekly commits reached 275 million, projecting to ~14 billion for the year—a 14x increase. AI tools like Claude Code now contribute 4.5% of all public repository commits, with weekly submissions surging 25x in just three months. AI-generated pull requests jumped from 4 million to 17 million per month in half a year. Unlike human developers, AI Agents work continuously, generating commits at a scale that overwhelms infrastructure designed for human rhythms. The surge also shattered GitHub's business model. Copilot's flat-rate pricing, based on assisting human developers, became unsustainable as Agentic AI sessions consumed resources worth hundreds of dollars for a few dollars in fees. In response, GitHub imposed usage limits and, by June 1st, shifted to a pay-per-use "AI Credits" system. Facing this new reality, GitHub realized a 10x scaling plan was insufficient. It announced a need to *redesign* its architecture for 30x current scale—decoupling services, adding fault isolation, and improving change management to prevent cascading failures. Other platforms like Stripe and AWS are facing similar challenges with AI Agents. Fundamentally, GitHub is transitioning from a human collaboration platform to an "exhaust pipe" for automated AI workflows. Its detailed post-mortem reports aim to maintain trust during this turbulent rebuild. The February outage was not just a technical glitch, but a signal of the software industry's entry into a new, AI-driven era.

marsbit06/04 10:40

GitHub, Transfixed by AI

marsbit06/04 10:40

活动图片