» Published on Wed, 02 Sep 2026 10:59:00 +0000

• Update

  Workaround has been deployed, we're observing the situation

  » Updated Wed, 02 Sep 2026 16:54:00 +0000

• Update

  Update: the source of the problem seems related to an upgrade from GitHub which impact some version of git.

  • Applications running the stack scalingo-26 are not impacted by the incident.
  • Other stacks are impacted

  A workaround is being implemented to ensure all deployments got back in track

  » Updated Wed, 02 Sep 2026 16:22:00 +0000

• Update

  Incident is still ongoing, GitHub requests to download public repositories still have a high rate of errors

  » Updated Wed, 02 Sep 2026 15:21:00 +0000

• Update

  Since 16h19 (CEST), new cases of the same situation are appearing, we are re-opening the incident.

  » Updated Wed, 02 Sep 2026 14:27:00 +0000

• Resolved

  All deployments are now working as expected

  » Updated Wed, 02 Sep 2026 13:12:00 +0000

• Update

  Most deployments are now working as expected, we're observing the situation

  » Updated Wed, 02 Sep 2026 13:11:00 +0000

• Update

  Incident is still ongoing, part of deployments are still failing when cloning public repositories. Workaround is to retry one or multiple times.

  » Updated Wed, 02 Sep 2026 12:05:00 +0000

• Update

  We still identify a large number of 401 responses from GitHub over public repositories, the strategy is still to retry your deployments.

  » Updated Wed, 02 Sep 2026 11:32:00 +0000

• Update

  It has been identified that the situation is getting better. Attempt a few retries of your deployments and they should work eventually

  » Updated Wed, 02 Sep 2026 11:02:00 +0000

• Investigating

  Global issue on GitHub leads to the impossibility of fetching code from public repositories.

  As a result deployments using custom or multi buildpacks may fail or if your dependency manager fetches code on GitHub.

  » Updated Wed, 02 Sep 2026 10:59:00 +0000