News World That's Worth

Salesforce Resolves Global Outage Impacting Multi-Region Services During Peak Dreamforce 2026 Conference Salesforce Inc. experienced a significant global service disruption affecting platform availability, API response times, and data synchronization for enterprise clients worldwide. According to official system status reports, the incident began at approximately 09:30 BST (08:30 UTC) on September 16, 2026 . Following targeted remediation efforts, Salesforce confirmed that system recovery and service restoration were finalized by 12:19 BST (10:56 UTC) . Incident Response and Code-Level Mitigation Salesforce deployed rapid infrastructure-level and code-level fixes to restore service availability: Global Impact Scope: The outage affected core CRM modules, customer support portals, and integrated developer APIs across multiple geographic instances globally. Targeted Remediation Protocols: Salesforce engineers initiated emergency service restarts alongside code-level patches to address...

GitHub CTO Reveals Surge in AI Code Commits Led to 7-Hour Outage, Accelerates Azure Migration GitHub has published a detailed technical post-mortem addressing its 7-hour major outage on August 17, 2026 . Expanding on initial reports that pointed to an Istio service mesh misconfiguration, GitHub Chief Technology Officer Vlad Fedorov clarified that the root cause was a systemic capacity failure triggered by unprecedented global traffic spikes. Fedorov explained that the incident was a direct continuation of infrastructure challenges highlighted in April. On August 17, incoming traffic reached record-breaking peaks that overwhelmed compute capacity in GitHub’s primary Central US data center region , initiating a cascading failure across interdependent microservices. Restoring the platform proved exceptionally difficult due to tightly coupled architectural dependencies: Cascading Outages: Core services collapsed sequentially as shared routing layers reached resource exhaustion. Thunderi...

GitHub Outage Breakdown: Istio Limits, Connection Loops, and VS Code Copilot Bug Cause 7-Hour Downtime GitHub experienced a major cascading outage lasting over seven hours, leaving millions of developers unable to push code or access repositories. Following the incident, the engineering team published a preliminary post-mortem detailing how a convergence of unexpected traffic spikes, misconfigurations, and a client-side retry bug in VS Code triggered the prolonged disruption. The incident originated in the Central US region when an influx of user traffic coincided with a hidden configuration bottleneck in GitHub's internal Istio service mesh. When the auto-scaling mechanism triggered, it failed to account for Istio sidecar proxy limits. As new instances scaled up, sidecar allocation hit hard system caps, causing the primary HAProxy load balancers to crash sequentially until the entire regional gateway went offline. The outage was severely amplified by aggressive internal and e...

Taiwan Simulates Total Network Blackout by Throttling Mobile Data 99% During Annual Defense Drills During its annual nation-wide defense exercises last week, Taiwan introduced a critical new tactical scenario: simulating a total communications blackout caused by potential cross-strait conflict or targeted cyberattacks. As part of the 30-minute training window, air-raid sirens sounded while emergency push notifications were broadcast across mobile networks, instructing citizens to immediately take cover in designated buildings and underground shelters. To test societal resilience under severe infrastructure disruption, authorities implemented a 99% reduction in mobile internet speeds . This severe throttle rendered data applications virtually unusable, restricting mobile networks strictly to basic voice calls and SMS text messaging. Fixed-line broadband infrastructure remained unaffected throughout the exercise. The blackout simulation was conducted first in Taichung on Monday, follow...

GitHub CTO Issues Apology After Multiple Outages, Citing "The AI-Driven Coding Explosion" Vladimir Fedorov , Chief Technology Officer at GitHub , has formally apologized to the developer community following a series of service instabilities that saw the platform suffer two major outages within a single week. These incidents have raised significant concerns among top-tier developers, notably leading to the creator of Ghostty announcing a migration away from the platform. The Anatomy of the Outages The platform faced two distinct technical failures: April 23: A failure in the merge queue system disrupted repositories and hampered merge requests. April 27: A major search functionality outage triggered by a crash in the Elasticsearch infrastructure. The "AI Impact": A 30x Capacity Challenge Fedorov explained that the root cause lies in a fundamental shift in how software is developed. The rise of AI-powered coding assistants has led to an unprecedented surge in pl...

Mitchell Hashimoto Departs GitHub : Why the Creator of Ghostty is Moving Away Mitchell Hashimoto , the renowned software developer and creator of the popular open-source terminal emulator Ghostty , has announced that he will be migrating the project’s source code away from GitHub. This marks a significant departure for a developer who has been an integral part of the GitHub community since its earliest days. The "Breaking Point" Hashimoto, who joined GitHub in February 2008 as user #1299 , has been a daily active user for nearly two decades. However, he cites a growing frustration with GitHub’s reliability: Unacceptable Downtime: Hashimoto noted that recent service outages have become too frequent, with many lasting for extended periods. Operational Friction: For a project like Ghostty, which demands serious, consistent maintenance, these outages have become a major bottleneck. Hashimoto stated that GitHub no longer feels like a reliable "home" for mission-critica...

  OpenAI Rumored to Develop "GitHub Rival" as Relationship with Microsoft Fractures According to a report from The Information , OpenAI is reportedly developing its own internal source code management system to rival GitHub . The decision stems from growing frustrations within OpenAI regarding GitHub’s recent performance issues and frequent service outages, which have reportedly hampered development workflows. From Internal Tool to Potential Market Competitor While the software does not yet have an official name, it is expected to remain in development for several more months. Sources suggest that while the project was initially intended solely for internal use , there have been high-level discussions within OpenAI about eventually offering the platform as a service to external customers . Such a move would position OpenAI as a direct competitor in the version control market. Strained Ties: The Microsoft-AWS Friction The move away from GitHub is seen as another sign of the d...