Action stopped working a few minutes ago. All builds are failing. (Private repo)

Is there something happening?
Can confirm. Sent a ticket to enterprise support, no response yet
Same issue here, the action suddenly stopped working.
Me too, but only at private repos. At public repos, the action runs fine...
Same here
Same here
Me too, but only at private repos. At public repos, the actions runs fine...
Same here, our repo is private. Not public. Might be a reason thus?
It looks like it has already happened back in May this year. #254
same here
Same here with private repo
Same here
same here
I came across this issue with private repo.
same here
failing also here for a private repository.
can you please update: https://www.githubstatus.com/ ?
Wasted time trying to debug when it was showing green
same here
same here
+1. Thought I was going mad, this thread is a relief 馃槅
same here
Same here, I think Github's intern screwed up
Same. Can confirm this is affecting private repos. I tried it in a personal public repo and it worked fine.
name: test
on: push
jobs:
checkout-test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
Seems self-hosted actions are also affected https://twitter.com/CryptoChybro/status/1332352039800680448?s=20
oh .. is it the GitHub internal mistake for this issue? so annoying
Sigh.
i just push several version, just think it is unlucky for me for first several fail...
Also experiencing this issue. Seems like there is an extra forward slash added to the repo URL?
Same here.
same issue here
Ditto.
Looks like they're aware of it and they're looking into it: https://www.githubstatus.com/incidents/vts24q167tc8
Seems that something bigger is happening on internet right now, not only Github.
As @kyler-hyuna mentioned it, my own self-hosted pipelines are not running on AWS (Paris), can't deal with the checkout process.
Btw, in France lot of people complained about DNS problems, affecting Orange (internet provider) on several websites (Amazon / Twitch / Github / Paypal / etc...)
Seems that something bigger is happening on internet right now, not only Github.
As @kyler-hyuna mentioned it, my own self-hosted pipelines are not running on AWS (Paris), can't deal with the checkout process.
Btw, in France lot of people complained about DNS problems, affecting Orange (internet provider) on several websites (Amazon / Twitch / Github / Paypal / etc...)
Source please, directly interested by this
same here...
Seems that something bigger is happening on internet right now, not only Github.
As @kyler-hyuna mentioned it, my own self-hosted pipelines are not running on AWS (Paris), can't deal with the checkout process.
Btw, in France lot of people complained about DNS problems, affecting Orange (internet provider) on several websites (Amazon / Twitch / Github / Paypal / etc...)Source please, directly interested by this
Source ? Just my own investigations, and twitter feed by searching 'github down orange' on twitter :D
It started with a "potential" orange dns issue, i wasn't able to reach any github.com source IP.
Then, all my Github Actions self hosted pipelines, went down, not able to checkout any of my private repository.
On Twitter some people with Orange provider were also arguing that they weren't able to reach some other website like Paypal / Amazon / Twitch / Etc ...
I moved to Google DNS on IPv4, same thing
I moved to Cloudflare DNS on IPv4, and it worked again
But basically, it's more than a DNS issue, since AWS has the same problem on their own infrastructure.
The only common thing is that i'm using the french AWS Datacenter. So ...
same here...
same here ...
We are also facing same issue
It is working again, at least for some repos 馃

Seems that something bigger is happening on internet right now, not only Github.
As @kyler-hyuna mentioned it, my own self-hosted pipelines are not running on AWS (Paris), can't deal with the checkout process.
Btw, in France lot of people complained about DNS problems, affecting Orange (internet provider) on several websites (Amazon / Twitch / Github / Paypal / etc...)Source please, directly interested by this
Source ? Just my own investigations, and twitter feed by searching 'github down orange' on twitter :D
It started with a "potential" orange dns issue, i wasn't able to reach any github.com source IP.
Then, all my Github Actions self hosted pipelines, went down, not able to checkout any of my private repository.On Twitter some people with Orange provider were also arguing that they weren't able to reach some other website like Paypal / Amazon / Twitch / Etc ...
I moved to Google DNS on IPv4, same thing
I moved to Cloudflare DNS on IPv4, and it worked againBut basically, it's more than a DNS issue, since AWS has the same problem on their own infrastructure.
The only common thing is that i'm using the french AWS Datacenter. So ...
Had no issue as an Orange user personally (except ofc on the actions), might be because I'm always on OpenDNS servers though, thanks for the update 馃憣
Seems that something bigger is happening on internet right now, not only Github.
As @kyler-hyuna mentioned it, my own self-hosted pipelines are not running on AWS (Paris), can't deal with the checkout process.
Btw, in France lot of people complained about DNS problems, affecting Orange (internet provider) on several websites (Amazon / Twitch / Github / Paypal / etc...)
My self-hosted runner is not working either. New jobs pick up by runner, all failed.
But re-running a job from previous one that was working, it ran just fine.
So now i'm not sure what is going on xD

same
It is working again, at least for some repos 馃
For the moment my pipelines are still not able to checkout any private source code :

check this.
Just a heads up for anybody finding this thread now, seems like service is coming back 馃榿
Just a heads up for anybody finding this thread now, seems like service is coming back 馃榿
Confirm
Just a heads up for anybody finding this thread now, seems like service is coming back 馃榿
Indeed! 馃檪
Is Down again :(

@zoispag Still not working for me. I think it is down again.
@zoispag Correction. It appears to work when I create a new GitHub action token (see #238).
I'm having same issue now with corporate repo.
Cloning doesn't work for most of the workflows.
Only PR checks are fine.
Most helpful comment
Looks like they're aware of it and they're looking into it: https://www.githubstatus.com/incidents/vts24q167tc8