bug-bounty267
google223
facebook191
microsoft178
apple129
exploit104
rce99
xss88
writeup55
csrf52
defi48
smart-contract47
ethereum44
open-source44
access-control42
account-takeover39
sqli39
aws37
docker36
ssrf36
ai-agents36
web335
malware35
bragging-post33
smart-contract-vulnerability33
cloudflare33
cve32
react32
dos31
idor28
subdomain-takeover27
wordpress26
browser26
privilege-escalation26
supply-chain26
solidity25
cors24
oauth23
node22
authentication-bypass21
auth-bypass21
cloud21
race-condition21
denial-of-service21
automation20
tool19
lfi19
pentest19
vulnerability-disclosure19
machine-learning18
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