bug-bounty252
google211
facebook176
microsoft172
apple125
rce95
exploit88
xss57
defi48
smart-contract47
writeup47
ethereum44
open-source44
access-control42
sqli39
aws37
ai-agents36
docker36
csrf36
web335
account-takeover35
ssrf35
malware34
bragging-post33
cloudflare33
smart-contract-vulnerability33
react32
dos31
cve31
subdomain-takeover27
supply-chain26
idor26
privilege-escalation25
solidity25
wordpress23
browser23
cors23
node22
denial-of-service21
authentication-bypass21
oauth21
automation20
race-condition20
vulnerability-disclosure19
auth-bypass19
tool19
cloud19
machine-learning18
llm17
pentest17
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