GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Inverness	Website Down	9 days ago
Quito	Sign in	10 days ago
Junín	Errors	10 days ago
Guadalajara	Errors	10 days ago
Paris	Website Down	10 days ago
Quito	Errors	10 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Alonso G (@CryptoDegenTopG) reported 5 minutes ago

  @XPeterKappes @bot @cursor_ai Same issue here. Mine is connected with my GitHub and I am getting the same error

• 
  shaki (@shakiXBT) reported 7 minutes ago

  one more github actions outage and i end it all

• 
  jacob (@thal0x) reported 8 minutes ago

  Another day another GitHub outage

• 
  RM (@TMIchigoGijutsu) reported 18 minutes ago

  When you put foreigners out of South Africa they turn bitter against us that have nothing to do with Xenophobia and Afrophobia. They don't hesitate to attack us on Twitter who don't believe in harming them. They spread technical fallacies online too about middlemen and whatnot. An AI startup in Africa does NOT need to be a frontier lab at all. It needs to solve crop damage, conservation, education, crime, etc. and it is absolutely FREE to do so. They don't even need an investor to start if they have a GitHub account and a loyal userbase. WHy are they breaking us down at this CRITICAL juncture in AFRICA when NOW is the time to act?

• 
  misticos (@iv_misticos) reported 21 minutes ago

  mf github is down because they aren't using @PlanetScale

• 
  Goozbach.yml (@goozbach) reported 23 minutes ago

  <insert xkcd about swordfights> "Github actions are down again" :sigh:

• 
  Alex Lavaee (@alexlavaee) reported 24 minutes ago

  Every major coding agent is racing to add durable workflows. I shipped them 7 months ago. I'm an AI researcher and I build open source software on the side, including Atomic, a verifiable coding agent runtime. Below I predict where every agent platform is headed next. Here are my predictions. Save this and repost it: "Done" becomes a definition, not a claim. Completion gets gated on receipts: checks that ran, review from a reviewer with a clean context, artifacts on disk. Not a model saying done. DSLs lose to runtimes. A drawn graph with a fixed set of node types can't express what engineering loops need: fan-out computed at runtime, typed contracts between stages, branching decided by results. Workflows end up as real programs. In Atomic, they're TypeScript with typed inputs and outputs, sitting in your repo, diffed and versioned like everything else. We’ll see a hybrid of stochastic LM behavior and deterministic tools. Verification hardens. Matching "PASS" out of a model's reply is not reliable. Schema-validated verdicts, independent fresh-context reviewers, and deterministic checks running as durable nodes in the graph is where every platform will end up. Context engineering becomes explicit. Any run long enough to matter overflows its context window, so the runtime compacts the transcript to keep going. Compaction is lossy: summaries drop instructions, and an agent that lost "don't touch the release pipeline" will touch the release pipeline. Two mechanisms fix this. Contract text like the objective, acceptance criteria, and restrictions are pinned and survive every compaction cycle, verbatim. In Atomic, that’s its <keepContext></keepContext> tag feature. And large intermediate output moves between stages as files instead of transcripts. Budgets become enforceable. Token, cost, and duration ceilings per run, enforced by the runtime. This is critical for managing costs and directly controlling verification-time scaling, which is going to be a new axis of test-time scaling. Recursive Workflows / Recursive State Machines become the standard. Workflows calling workflows through typed contracts, checkpointed so a run can pause, resume, and replay across sessions, will become common fault-tolerance strategies. We call the research direction Recursive State Machines (RSMs), our take on RLMs: recursion inside the model made long context tractable, but recursion in the runtime is our attempt at making long work tractable. ----- Atomic has productionized all of this today, open source. If you want the how, ask Atomic itself. The runtime is self-documented and will walk you through its own architecture. If you want the what, run it on complex tasks and start to learn how to use workflows because it’s a completely different way of building software. Working this way is a real shift from driving a coding agent today, and the earlier you start adjusting, the further ahead you are when the platforms catch up. 7 months ago I shipped workflows. Before that, loops. The best part of building ahead of the market is you get to keep shipping while it catches up. Don’t just take my word for it. You can check out Atomic (bastani-inc/atomic) on GitHub to try it for yourself and watch to see if these predictions come true.

• 
  Aurorastar (@G_ameman) reported 29 minutes ago

  02:37:39–02:40:08 02:37:39 You just tell it to keep going until you tell it to stop. 02:37:45 It ended up... 02:37:45 I think we ended up with a 46 time execution improvement over the original. 02:37:51 It's incredible. 02:37:52 Absolutely incredible. 02:37:52 It's just incredible. 02:37:54 Um, I do, you know, I just don't think there's anything that compares to Fable in terms of planning. 02:37:58 So I usually do Fable for planning and for reviewing, and then something else for implementation, like Opus 5. 02:38:08 And it's really nice. 02:38:08 It's a, it's a really nice setup that allows you to not run out of tokens too much. 02:38:14 What I found, it's really interesting because Fable is, in my opinion, the best model right now, but it also makes mistakes. 02:38:18 And the best way to get the best software, I would actually rather have two differently sourced sort of... 02:38:25 I mean, they're not mid-tier, they're all frontier. 02:38:29 But have, let's say Opus 5 and Codex and have one check the other's job. 02:38:35 This is my standard operating procedure now. 02:38:40 I'll have Opus or Fable do the work, and then I always end it, review with Codex xHigh. 02:38:47 And I've also started using Grok just to test it out, and it's also quite good. 02:38:47 And it keeps finding stuff. 02:38:51 And then that's my workflow when I'm having my agents on my own machine do it, and then I push to GitHub. 02:38:55 And then Copilot, I kid you not, has actually gotten good. 02:38:59 Copilot keeps finding stuff that's legitimately broken, which is also incredible acceleration because the first version of Copilot that started doing this was literally retarded. 02:39:09 It would just constantly flag things that were nonsense. 02:39:13 It would constantly flag the same problem over and over again as you would push. 02:39:13 It was really annoying, so I think a lot of people actually ended up turning that off. 02:39:17 And if they did, they should turn it back on because it's actually quite good. 02:39:24 Keeps finding things. 02:39:24 And if you then take that, and we shouldn't be surprised. 02:39:24 Why are we surprised? 02:39:27 Even if you're a good programmer, if you finish a job and you ask your also very good peer to review it, you're gonna end up with better code. 02:39:35 Of course you're gonna end up with better code. 02:39:35 So build that into your process. 02:39:39 Pick one of the agents to drive with. 02:39:39 I've mainly been driving with Claude, which is actually interesting because I have some other reservations about Anthropic. 02:39:47 But the reason I'm sticking with Claude is, in my opinion, they actually have the best harness. 02:39:53 And one of the reasons it's the best harness is it's multi-agent running. 02:39:57 So if you wanna run multiple agents at the same time, you can do arrow left when you're inside a session, then it goes back to Agent View. 02:40:05 And here in Agent View, you can pick up another agent. 02:40:08 So if you wanna do this thing where you have multiple threads going on the Claude Code is just the nicest setup.

• 
  Solomon Hykes (@solomonstre) reported 29 minutes ago

  Guys I promise you, emulating Github Actions locally will not fix your CI. Stop doing this to yourselves.

• 
  Khalid (@KhalidDevLog) reported 31 minutes ago

  github actions is down again 👀.

• 
  dan72ros (@dan72ros) reported 31 minutes ago

  @miriamschwab 2nd (also when I was using cowork) I found that prompting too much in 1 context window there was a massive deterioration / loss of quality etc. I documented in a github doc. Not sure how to share that. I had a terrible experience w/claude

• 
  Jesse Showalter (@imjesseshow) reported 33 minutes ago

  Big one from @usewonder: direct GitHub connection, so I can pull real code down into the canvas. That's the Claude Code approach applied to design. You work against the actual repo, not a picture of it.

• 
  Praveen Bhardwaj (@xpr4win) reported 34 minutes ago

  After staring at the same workflow for 30 minutes wondering why nothing was happening… I finally checked the status page.Turns out GitHub is having a major outage for Actions. 🙃 Anyone else stuck in the same queue right now? #GitHubActions #Outage

• 
  Simon Lee (@smoon_lee) reported 38 minutes ago

  @iam_edh I was, it broke like 2 hours ago, so I gave up. I was happily building and testing and the BAM, GitHub goes down

• 
  Gareth Owen (@TheAnswers42Com) reported 40 minutes ago

  So here's just where I go past the 280 character limit and do a House of the Dead PC infodump as I love this game, and the code behind it's a pretty interesting snapshot of games development in the late 90s, pretty much the wild west of 3D graphics before things like renderers became a solved problem. Nowadays you can just download Unreal and get a world-class renderer and asset pipeline at your fingertips for free, but back then everything was pretty much handcrafted, and you can see that here. The renderer almost instantly gives away its 90s origin - most of the assembly of draw commands and meshes, etc. is done on the CPU, and then rasterization is carried out either by a software renderer onto a DirectDraw surface, or dispatched to a Direct3D 6 device for rasterization. It's from a world before programmable pipelines, and where software rendering was super common. I've been using TypeScript so far as it's just easier than the compile/crash cycle of C++, and the Canvas API of HTML 5 is a pretty good match for DirectDraw in many ways. Assets are stored in a format called RBH - all of them. The RBH file seems to be a form of RIFF/PIFF file, and the payload itself is either an uncompressed BODY, or can also be a PACK file that's been put together using a custom LZ compression algorithm that Tantalus themselves came up with. Game logic, sounds, the camera and cutscene opcodes for the events VM, pretty much everything is in there as an RBH. I knew it was some kind of compression, but chatting with Qwen and Cursor really helped pin down some stuff about it much quicker than I could have a few years ago. I came up with a set of TypeScript decompressors that run using Bun to get it all decoded and turned into formats that can be viewed correctly outside of the game engine, and I've also translated them into Python as well to stand independently of the asset pipeline tests I've been doing. Pretty much all House of the Dead code has been lost to time, but I'm hoping that eventually I can shed some light on it and figure out what made that game tick. It's a pretty special one to me, and I always found it sad that all of the artifacts from its development seem to have been lost. Still working a lot of stuff out, but I've been keeping notes about what I find as I go, and I figure I'll write it up in a wiki on Github as it's pretty interesting stuff. In its current state it's all pretty messy and there's a lot I'm not sure about right now, but in time I think I can crack it. Maybe there is some source code knocking about there on floppies or CDs in a drawer or attic, but even so I doubt if it's survived disc rot. This is probably the next best thing!

• 
  Shreyans Jain (@shreyansj) reported 40 minutes ago

  been a while since Github was down, I was getting worried

• 
  Selasie Sepenu (@SelasiSepenu) reported 41 minutes ago

  Am I tripping or github actions is down again

• 
  Pavan Kumar (@pavank38) reported 42 minutes ago

  If normies are using AI to write “technical code” what is the problem with using GitHub? AI can handle end to end version management with GitHub CLI. beyond shilling the “technical vs non-technical” distinction, what’s the actual use case?

• 
  November (@Nov_006) reported 43 minutes ago

  @ekemini58110 GitHub Enterprise Server is probably the only solution...Your own infrastructure.

• 
  DFIR Lab (@DFIR_Lab) reported 43 minutes ago

  A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected *** provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured *** Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

• 
  Ellie Huxtable (@ellie_huxtable) reported 48 minutes ago

  @itsnotryan @github does it shut down a few times a day?

• 
  Nisha Purushotham (@nisha_gowdaa) reported 48 minutes ago

  I blinked for a second and there is a Github outage #fuckinghell

• 
  Lee Packham (@Joolz) reported 49 minutes ago

  You just know the current @github outage is bad when they clearly hand-wrote that latest status update about Vitess. /cc @QuinnyPig

• 
  KISA aka Copenzafan.eth (@copenzafan) reported 51 minutes ago

  AI agents on a VPS are a terrible idea. And now I’m going to argue against an engineer from Google. His argument is that agents shouldn’t run locally. That includes Claude and Codex, meaning you shouldn’t have a harness on your own machine. I completely disagree, specifically within the bounds of “can I vibe code this?” For example, deploying a website takes a fair amount of resources before the site is even ready. Instead of building it on my PC and shipping it to a VPS, I’m supposedly meant to do the whole thing directly on the VPS. Which means I’m expected to pay several times more than the cheapest plan just to have enough RAM, so my agent doesn’t die along with a frozen server. The same problem comes up if I need to build a graphical app for managing lots of agents. So the agent writes code, has to push it to GitHub, and then I pull updates from there and test the app. Or I have to download the code or build every time. And where am I even supposed to compile that build without GitHub? Sure, you can host an agent on a VPS that counts your calories. But hosting an agent on a VPS to vibe code and build your projects? What kind of inconvenient nonsense is that? Is that why Google keeps shipping Gemini this ugly and dumb?

• 
  Codewithoutai (@Codewithoutai) reported 52 minutes ago

  Geez. Can you all stop being meat proxies for a second so GitHub can fix Actions?

• 
  Julien (@JulienCoulaud) reported 55 minutes ago

  is there any correlation between github being down and all the models being dumb today?

• 
  Delali (@delali) reported 57 minutes ago

  For 7 hours and 47 minutes on 17 August you could not sign in, open a pull request, or run a build, and GitHub's chief technology officer published why. Monthly commits went from 1.4 billion in April to 2.9 billion in August. A component in the Central US data centre stopped scaling at that new peak, which took github[dot]com, authentication, Actions, the API, and Copilot down with it. I plan for my own service going down, although I had never planned for a working day without the host that stores my code. What did you do while Github was down?

• 
  Lucas Pavani (@Pavaniecom) reported 60 minutes ago

  A GitHub issue asking for AGENTS.md sat open a year. 4,997 upvotes, 11 against, closed in August as resolved. The fix: a CLAUDE.md that imports AGENTS.md, or a symlink. That closes the title. Not the problem.

• 
  BowTied Fullstack - Link in bio or NGMI (@BowTiedStack) reported 1 hour ago

  The most compelling use case I've found on a software engineering side has been automating QA where @Grok @Bot has a dedicated testing email account and can actually do full QA login flows without needing to code them in Playwright. I've also setup different roles for Engineer, Reviewer, Researcher, Product, QA, and had them work with each other to get reviews, address feedback etc. I'm still unsure there really is a ton of benefit from this approach vs. auto-reviewers in Github PRs and my existing Hermes workflows. Grok Bot usage quota has been buggy as hell too. I supposedly burned a month's quota in 4 days, but now it says I've only used 7% while simultaneously erroring half the time that quota is fully used. Certainly some rough edges they need to iron out, even beyond the capability limits of Grok-4.6.

• 
  Grant Smith📡 (@S1n1st3rSecuri1) reported 1 hour ago

  GitHub actions being down again is actually insane. Probably the most unreliable platform I’ve used ever.