bug-bounty274
google223
facebook189
microsoft176
apple128
exploit102
rce95
xss88
csrf53
writeup51
defi48
smart-contract47
access-control44
ethereum44
open-source44
account-takeover40
sqli39
bragging-post39
aws37
ssrf37
ai-agents36
docker36
malware35
web335
smart-contract-vulnerability33
react32
dos31
cve31
subdomain-takeover29
cloudflare29
idor28
privilege-escalation27
wordpress26
supply-chain26
browser26
authentication-bypass25
solidity25
oauth23
node22
cors22
auth-bypass21
race-condition21
denial-of-service21
automation20
cloud20
vulnerability-disclosure19
api-security19
tool19
lfi18
clickjacking18
0
5/10
incident-analysis
GitHub published a detailed postmortem of three major availability incidents (Feb 2, Feb 9, Mar 5) caused by rapid usage growth, architectural coupling in authentication/user management database clusters, insufficient load shedding mechanisms, and latent failover configuration issues. The incidents revealed single points of failure across critical infrastructure including Actions runners and Redis clusters, with mitigation strategies including user cache redesign, infrastructure isolation, and migration to Azure.
infrastructure
availability
outage
database-scaling
caching
load-shedding
failover
redis
github-actions
incident-response
architectural-coupling
capacity-planning
resilience
GitHub
Azure
Redis
GitHub Actions