Outage in Blacksmith

GitHub returning 429s when downloading first party actions

Resolved Minor
July 28, 2025 - Started 3 months ago - Lasted about 10 hours

Incident Report

We are monitoring reports of GitHub returning 429s when downloading first party actions such as actions/setup-go etc. The error string being reported is of the form: ``` Error: Response status code does not indicate success: 429 (Too Many Requests). DC04:39E04E:636AE0:858F56:6887975E ```
Components affected
Blacksmith Github → Actions

Need to monitor Blacksmith outages?

One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.

Start Free Trial
Latest Updates ( sorted recent to last )
INVESTIGATING 3 months ago - at 07/28/2025 03:32PM

We are monitoring reports of GitHub returning 429s when downloading first party actions such as actions/setup-go etc. The error string being reported is of the form: ``` Error: Response status code does not indicate success: 429 (Too Many Requests). DC04:39E04E:636AE0:858F56:6887975E ```

IDENTIFIED 3 months ago - at 07/28/2025 05:01PM

GitHub have declared an upstream incident, we will continue monitoring these failures we are seeing sporadically - u003chttps://www.githubstatus.com/incidents/s6d4x8c6cvv5u003e

Latest Blacksmith outages

Github reporting degraded performance for Actions - 6 days ago
Jobs not being picked up - 6 days ago
Jobs not getting picked up - 6 days ago
Control Plane Endpoints Down - 13 days ago
Increased queue times in the US region - 13 days ago

The Status Page Aggregator Built for IT Teams

With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.

Start free trial

No credit card required · Cancel anytime · 4522 services available

Integrations with Slack Microsoft Teams Google Chat Datadog PagerDuty Zapier Discord Webhook