← Back to GitHub History
critical✓ Resolved
Incident with Actions
Status
resolved
Duration
2h 53m
Updates
9
Coverage
0 articles
INCIDENT TIMELINE
✓ ResolvedWed, Aug 26, 2026, 06:05 PM
This incident has been resolved.
monitoringWed, Aug 26, 2026, 05:54 PM
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigatingWed, Aug 26, 2026, 05:32 PM
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
investigatingWed, Aug 26, 2026, 04:50 PM
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
investigatingWed, Aug 26, 2026, 04:49 PM
Pages is operating normally.
investigatingWed, Aug 26, 2026, 04:14 PM
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
investigatingWed, Aug 26, 2026, 03:48 PM
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
investigatingWed, Aug 26, 2026, 03:23 PM
We've identified an issue with a database primary and are failing over to a replica immediately
investigatingWed, Aug 26, 2026, 03:12 PM
Pages is experiencing degraded performance. We are continuing to investigate.
investigatingWed, Aug 26, 2026, 03:11 PM
We are investigating reports of degraded availability for Actions
📊 TECHNICAL DETAILS
Internal ID
e72d1642-cc4e-4cd6-a6da-1f97e338ec1f
External ID
y1t7p9fzrlj2
🕐 Started
Wed, Aug 26, 2026, 03:11 PM
🔄 Last Updated
Wed, Aug 26, 2026, 06:05 PM
✓ Resolved
Wed, Aug 26, 2026, 06:05 PM
CRITICAL
Impact Level
2h 53m
Total Duration
9
Status Updates
Affected Components
ActionsPages
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed