![[Update: GitHub is back now] It’s not just you — GitHub is down](https://img-cdn.tnwcdn.com/image?fit=1280%2C720&url=https%3A%2F%2Fcdn0.tnwcdn.com%2Fwp-content%2Fblogs.dir%2F1%2Ffiles%2F2016%2F01%2FScreen-Shot-2016-01-27-at-4.50.36-PM.png&signature=188ea074c2a1b09352c115194795811d)
Story by
Nate Swanner
Former Reporter, TNWTNW's former West Coast writer in the PNW (Portland, Oregon). Nate loves amplifying developers, and codes in Swift when he's not writing. If TNW's former West Coast writer in the PNW (Portland, Oregon). Nate loves amplifying developers, and codes in Swift when he's not writing. If you need to get in touch, Twitter is your best bet.
Update 2: After nearly three hours, GitHub is up and running again as of 8:23PM PST.
Update: As of 7:17PM PST, GitHub’s Status page reports that the platform is recovering.
The place where you’re probably hosting your code is down.
This afternoon (or evening… or morning, depending on where you are) GitHub began giving failure errors for those trying to log on. Down Detector shows is showing a lot of activity, all since around 4:00PM PST.
We’re investigating a significant network disruption affecting all https://t.co/2qUwMFsmyu services.
— GitHub Status (@githubstatus) January 28, 2016
We’ll be keeping an eye on this, and will update when it’s reliably back up. Until then, come up with creative things to tell your Product Manager about why you’re not making commits.
Get the TNW newsletter
Get the most important tech news in your inbox each week.
