Outage in Blacksmith

GitHub returning 429s when downloading first party actions

Resolved Minor
July 28, 2025 - Started 27 days ago - Lasted about 10 hours

Need to monitor Blacksmith outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Blacksmith, and never miss an outage again.
Start Free Trial

Outage Details

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
Latest Updates ( sorted recent to last )
INVESTIGATING 27 days 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 27 days 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

Track All Vendor Statuses & Outages Instantly

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 · 4400 services available

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