Incident with Actions, Pull Requests and Issues
GitHub Actions experienced a 500 internal server error, affecting Pull Requests and Issues functionality. No official fix URL provided.
since
Here's why. Incidents from Monday, October 12, 2026 (UTC), ranked byBreakage Velocity.What is Breakage Velocity?A live score of how fast an outage or regression is spreading. The more people hit it, and the faster, the higher it climbs; it cools off as things calm down.Open-ended scale: under 25 low · 25+ elevated · 100+ high · 300+ extreme.
12 outages, 2 still active today. Worst: Linux (37 d 16 h).
GitHub Actions experienced a 500 internal server error, affecting Pull Requests and Issues functionality. No official fix URL provided.
since
systemd-resolved, the DNS resolver in systemd, has broken DNSSEC verification. The issue caused internet connectivity issues for users who had DNSSEC enabled, including the OP of this Hacker News thread. No official fix URL provided.
since
There is a delay in data appearing in the UI and API, impacting customers triggering pipelines and those relying on outbound webhooks and email/SendGrid notifications. The issue has been resolved.
– UTC
Customers experiencing increased build failures or deployment issues that take longer to start. Build and deployment failure rates have decreased, but some builds remain queued.
– UTC
Groq experienced model performance and availability issues affecting the minimaxai/minimax-m2.7 model. The incident has been resolved and the model is operating normally.
– UTC
Fireworks AI experienced a service degradation affecting GLM 5.3. The incident has since been resolved and the service is operational.
– UTC
The Compliance API experienced a delay in data for the 'Delayed Costs' feature, affecting users who rely on this data. The issue has been resolved and all impacted services are fully recovered.
– UTC
Fireworks AI experienced a service degradation affecting GLM 5.3. The incident has since been resolved and the service is fully operational.
– UTC
Fireworks AI experienced a service degradation affecting Kimi K3, resulting in operational issues. The incident has now been resolved and the service is operational.
– UTC
Fireworks AI experienced a service degradation affecting the GLM 5.3 model. The incident has been resolved and the service is fully operational.
– UTC
GroqCloud experienced console errors affecting multiple regions. The incident has been resolved and all services are operating normally.
– UTC
Fireworks AI experienced a service degradation affecting GLM 5.3. The incident has since been resolved and the service is operational.
– UTC