bug-bounty481
xss240
bragging-post117
rce115
google110
microsoft98
account-takeover89
authentication-bypass82
facebook81
privilege-escalation80
open-source79
csrf79
stored-xss75
apple67
access-control65
web-security64
malware63
reflected-xss63
ai-agents62
input-validation53
cve51
sql-injection50
cross-site-scripting49
defi48
smart-contract48
phishing46
api-security46
exploit46
ethereum45
information-disclosure43
ssrf42
privacy40
web-application39
tool37
burp-suite37
vulnerability-disclosure37
cloudflare35
automation35
llm34
responsible-disclosure34
reverse-engineering34
web334
dos34
html-injection33
smart-contract-vulnerability33
idor32
ai-security32
opinion32
denial-of-service31
waf-bypass31
0
3/10
incident-report
GitHub details three major availability incidents (Feb 2, Feb 9, Mar 5, 2026) caused by rapid platform growth, architectural coupling, cache TTL misconfiguration, and failover gaps. The company outlines near and long-term mitigations including infrastructure redesign, Azure migration, and service isolation.
incident-report
availability
outage
infrastructure
scaling
database-performance
caching
load-shedding
failover
architecture
resilience
github-actions
GitHub
Vlad Fedorov
Azure