Unverified50% confidenceFactExact time
GitHub 内部使用 MySQL，并通过自研的 Vitess 分片方案和 Orchestrator 自动故障转移工具来管理其数据库集群
1
Sources
50%
Confidence
Long-term
Relevance
8/29/2026
First Seen
Sources
GitHub Actions 宕机原因分析：数据库主节点故障与排查指南
Related Entities
Related Claims
UnverifiedThe GitHub team initiated a failover mechanism, switching the service to a database replica to restore availability.74% similarUnverifiedGitHub Actions relies on backend databases to maintain task queues, runner allocation, workflow execution records, permission verification, and other states; a primary node failure prevented new tasks from being written to the scheduling queue, causing tasks to become stuck in a Queued state.69% similarUnverifiedThe root cause of this GitHub Actions outage was identified as a problem with the database primary node.67% similarPartially VerifiedGitHub's Dependabot tool automatically detects known vulnerabilities based on the GitHub Advisory Database and creates Pull Requests to update dependency versions that pose risks.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/816348API
curl https://kongchang.com/api/v1/knowledge/claims/816348MCP
get_claim(id=816348)