Status Page Status Page

Aug 26, 2026 · resolved Aug 27

GitHub component: Pull Requests Original GitHub incident: https://stspg.io/nrbwjftcz72d

Aug 20, 2026 · resolved Aug 20

The system is back to being fully operational.

Aug 19, 2026 · resolved Aug 19

**1. Summary** On August 19, 2026, some customers experienced slower page loading and data display, as well as delays when starting or completing pull request scans. The disruption was caused by a managed memory database entering a repeated restart cycle and not recovering automatically. This created a temporary slowdown in processing. Expected service behavior was restored after corrective actions, including replacement and increased capacity for the affected service. The provider is continuing to investigate why the service was unable to return to normal operation automatically. **2. Key Timeline (IDT)** • August 19, 2026, 16:10 IDT: We identified performance degradation affecting parts of the platform and pull request scanning. • August 19, 2026, 16:30 IDT: An initial corrective change was applied and service behavior was monitored. • August 19, 2026, 16:46 IDT: We confirmed that some delays were continuing and expanded the investigation. • August 19, 2026, 17:14 IDT: We began working with our service provider to investigate instability in the managed memory database. • August 19, 2026, 18:46 IDT: Recovery actions were in progress, with temporary mitigations in place to reduce customer impact. • August 19, 2026, 19:06 IDT: The managed memory database capacity update completed, and platform responsiveness and pull request scanning returned to expected behavior. **3. Root Cause** The managed memory database entered a repeated restart cycle and was unable to recover automatically. This caused delays in the processing systems that support platform responsiveness and pull request scans. The affected service underwent a routine replacement process, followed by a capacity increase during the recovery effort. While the capacity increase completed successfully and restored expected behavior, AWS is still researching why the service did not come back up normally after the restart cycle. Their detailed root-cause analysis is pending. **4. Actions Taken** • Applied corrective updates to reduce immediate processing demand. • Temporarily adjusted the status update process to reduce reliance on the affected service. • Restarted affected processing components to restore responsiveness. • Worked with the service provider to replace affected capacity and complete a capacity increase. • Monitored platform performance and scan processing until expected behavior was confirmed. **4b. Action Items** • Review the service provider’s detailed root-cause analysis when available. • Improve monitoring to detect similar recovery delays earlier. • Add safeguards to reduce the impact of temporary processing slowdowns. • Introduce separate Redis capacity for each service to isolate workloads and reduce the impact of an issue in one service on others.

Aug 18, 2026 · resolved Aug 18

Some GitHub pull request status checks in the EU region were delayed by up to 30 minutes before completing. No checks were lost and no action is needed - delayed checks completed automatically. We identified the cause, and fixed it. We're monitoring closely.

Aug 17, 2026 · resolved Aug 17

GitHub component: Git Operations, Webhooks, API Requests, Pull Requests Original GitHub incident: https://stspg.io/y1fl26l6wpzr

Is Status Page down right now?

No — Status Page is up. All systems operational as of Aug 28, 2:50 AM UTC.

What is Status Page's current status?

Status Page: All Systems Operational. Alert24 checks Status Page's status page continuously and can notify you the moment it changes.

How do I get alerted when Status Page goes down?

Alert24 monitors Status Page and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.