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 (56%)
• Errors (31%)
• Sign in (13%)

Live Outage Map

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

City	Problem Type	Report Time
Catania	Errors	14 hours ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  David Villegas (@labsdvx) reported 2 minutes ago

  @clairevo @joshkim @bot Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  ໊ (@otieeed) reported 5 minutes ago

  @ichikiwhere I've tried using a few cmdcode adapters from github and tried making one (vibe coded) tapi kok kayaknya they seem to be having a hard time when doing tool calls ya? is this also an issue here as well?

• 
  Ashraf | Code Explained (@AshrafXplains) reported 6 minutes ago

  @github The scope-aware dependency API is the interesting one. How does it represent a dependency the caller can see when the linked issue sits in a repository they cannot access?

• 
  Tarun Agarwal (@tarunag10) reported 8 minutes ago

  @clairevo @joshkim @bot I’d use Grok Bot as a Product Signal Agent. It would continuously watch customer feedback across X, support email, and GitHub, cluster repeated pain points, validate whether they’re real problems, and rank them by frequency + potential impact. Then every morning it gives me one thing worth building, with the evidence, a mini PRD, acceptance criteria, and a ready-to-open GitHub issue. Basically: turn scattered customer noise into a shippable product decision every day.

• 
  KSK Lab (@ksk_tinylab) reported 8 minutes ago

  My Codex philosophy: I start local, keep things simple, and understand what runs before giving it more access. If I wouldn’t install it at work just because it looks useful, I won’t blindly trust it at home. GitHub stars ≠ security review. Slow is fine. Cleanup isn’t.

• 
  Shii (@ShiiMapping) reported 12 minutes ago

  @mismagismagius Maybe export logs very shortly after this happens and send it to em with a GitHub issue or in the help channel of the official osu discord Feel like this is smth that'd flag up somewhere in runtime log or smth

• 
  Ricardo Vargas / Software Engineer (@ricardovdev) reported 13 minutes ago

  @AimenMT2 Do you prefer to message here or use GitHub issues for feature requests? There's an issue with the sync between the Main Window and the Post It.

• 
  Peter Chee (@pchee) reported 18 minutes ago

  @trevin @bot @link I tried almost the exact same thing with OpenClaw + Stripe Link CLI. Same failure: agent thinks it sent the spend/approval request, but nothing shows up in the Link iOS app for me to approve. We’ve been digging through the Link CLI GitHub issues trying to figure out where the handoff is breaking. Looks like it's not just us.

• 
  Vigilix (@VigilixAi) reported 24 minutes ago

  A single public GitHub issue granted unauthenticated attackers Editor-level control over Google Cloud projects through the Gemini CLI. Prompt injection bypassed an inactive allowlist, executed code on CI runners, and leveraged plaintext credentials plus overbroad service-account permissions introduced by Google's own setup script. Organizations that followed the recommended configuration inherited the exposure until the recent fixes.

• 
  Ethan Chu (@EthanChuAI) reported 27 minutes ago

  @Numalunah the pattern worth naming: the link looked safe because it arrived inside a tool you already trust. i hit a version of this yesterday - a token site half the timeline was recommending wouldn't load for me at all, and the fix was simply not signing into it with google or github. never oauth into a domain you met an hour ago.

• 
  K The Final Boss (@strafesti) reported 29 minutes ago

  @fieldproducer You’re holding yourself up as an example of the exceptional immigrant “talent” America supposedly risks losing, but your own story makes that argument considerably less impressive. By your own account, you eventually became an American citizen and then voluntarily moved to Portugal to found NOAN because it offered lower costs, affordable healthcare, a tech scene, and the lifestyle you wanted. You weren’t driven out of America by the H-1B grace period; you chose to leave after you were already an American. So using yourself as evidence that this policy causes America to lose founders is a pretty strange example. And since you responded to “you have no talent” by laughing rather than actually explaining what you built, let’s look at the product. Strip away the branding—“company brain,” “fact layer,” “AI workforce,” “absolute accuracy”—and NOAN appears to be a structured database/API combined with LLMs, task management, and workflow automation. Your own materials describe a stack involving Claude, GitHub, Supabase, Firecrawl, Resend, Netlify and Render, with specialized “agents” effectively being LLM workflows triggered by tasks and automations. That may be useful engineering, but useful integration is not the same thing as some revolutionary AI breakthrough. The obvious question is: what did you actually invent that is technically novel? The “fact layer” claim is even weaker. A database does not determine truth; it stores whatever somebody has designated as true. “Verified by whom, against what, and according to what standard?” An employee approving a record does not magically make it objectively correct. Retrieval accuracy is not factual accuracy, approval is not verification, consistency is not truth, and provenance is not truth. A centralized “single source of truth” can just as easily become a single source of perfectly synchronized error—one wrong approved record can now be propagated consistently to every agent, website, report, and customer interaction using it. Grounding an LLM in stored records also does not eliminate reasoning errors. The underlying facts can all be correct and the model can still misunderstand their relationship, omit an exception, or reach the wrong conclusion. So language like “absolute accuracy” and “nothing acts on a guess” seems to confuse having controlled source data with having solved truth and reasoning. You haven’t solved epistemology; you’ve built data governance and orchestration around AI. Which is why the funniest part of your response is that your whole brand says “facts not fiction,” yet when someone questioned your supposed talent, you provided no facts about what you actually created—just laughing emojis. If the company really demonstrates the exceptional technical talent you’re invoking in the immigration argument, explain what the proprietary breakthrough is. Otherwise this looks much more like ordinary software components wrapped in extremely ambitious AI marketing than evidence that America is losing some uniquely irreplaceable innovator.

• 
  Madeactual (@Madeactual) reported 29 minutes ago

  @stretchcloud The part I would not give up is the audit trail. Coordination overhead is annoying, but the thing that actually burns you is nobody being able to say what changed, when, and on whose authority. GitHub Issues are a lousy planner and a decent ledger, which is why people keep crawling back to them. If a shared planner keeps session replay and side-by-side diffs, it earns the swap. If it only removes the friction and not the record, you traded a slow system for an unexplainable one.

• 
  Mehdi Zare (@mehdizare) reported 30 minutes ago

  OpenCode CLI on the free models. Fine for GitHub issues and summarizing a thread. Falls over on coding, debugging, and a real call stack. Those free Zen models are limited-time. They rotate. Treat them as a scan tool. Free model to triage. Paid model to change the code.

• 
  Ricci Research (@ricci_nov) reported 37 minutes ago

  @kimmonismus @XIVIX_134 Top-down GTA clone is the new "draw a pelican on a bicycle" — a benchmark that looks impressive precisely because a thousand tutorial repos already solved it. Wake me when a mystery checkpoint one-shots something with no prior art on GitHub.

• 
  Wolvy (@wolymeme) reported 39 minutes ago

  Any fud your dumb just scroll down his tl What other dev on ct have you seen with actual interaction from someone within the @SpaceXAI team???? Worried about a fckn GitHub when Josh Kim is in his dms AND gave him $$$ credit NFA, but goodness gracious fckn dyor

• 
  Maciej Binkowski (@Matt_Binkowski) reported 40 minutes ago

  Quick look into GitHub and it seems there’s already a fix proposed waiting to be approved. Awesome.😎

• 
  Corner. (@reprover) reported 41 minutes ago

  @github The dependency API is the sleeper update for agentic workflows: automation needs explicit blocked-by relationships, not inference from issue text. Idempotent mutations and clear cycle/conflict errors would make it much safer to let agents maintain plans.

• 
  James Murray (@MurrayTheBard) reported 43 minutes ago

  @icunga_ AI still has a long way to go. I've been using github copilot to code for me and it always says it has a solution to the problem, implements and it doesn't work or breaks something else. It does eventually get it, but you have to have the patience of a saint.

• 
  Sondre Bjellås (@SondreB) reported 43 minutes ago

  Using Grok Bot to create software factories is amazing. First time it stumbled a bit, second time it's almost flawless. You don't really need to instruct the AI much more than an initial idea and it will do it all for you, end to end, one prompt and the output is app installers on GitHub releases. Though I asked it to write a document to setup such a factory - it's not reviews or optimized by a human, it's just AI doing its thing. I've seen people post similar creations before, though they are no longer needed. You start with an idea, then give some minor guidance along the way. Tell it you don't need to review, it should just merge PRs by itself. It uses GitHub issues and project to plan the work, instead of simply codebase markdown files, I like that. This is obviously extremely risky to do on a production ready software with actual users, but for new apps and services, this is absolutely brilliant and it no longer requires me to do basically nothing. The software factory link is in the first comment.

• 
  pasandida(:)aura (@huesofbanter) reported 46 minutes ago

  @akanxshhha its a github pr issue/bug retrieval augment generation project, ie if someone searches for some issue in the chat, it can search all the existing github database for that company quickly and add context from previously occured same issues into the prompt so user can see how it was solved before.

• 
  overflow (@overflowoxo) reported 48 minutes ago

  Hi @aesposito0 There is currently few hundred dollars waiting in your github if you decide to claim it after you claim: more trading activity -> more fees -> more money some made hundreds of thousands Our fan token can really go high if you decide to claim it and perhaps endorse it down the line

• 
  Team Rocket Pat ®️ (@teamRocketPat) reported 50 minutes ago

  @BiggestGrin I don't know of any discords, give it a Google I'm sure there are some, if you check my replies you can find the trade hijack github project and maybe get down leads there

• 
  FixxTheMoney (@FixxTheMoneyy) reported 50 minutes ago

  @Nih_Noh @ryanlanman1 @clay_garrett The hardware device is offline and generates key locally. The server key is created by them in their Secure Enclave. Where you have a sound gripe is the app key. The threat is Block could push a malicious update to steal app keys resulting in them having a quorum. The issue is null for Android users. You can verify the hash of the app is the exact code they pushed from their GitHub. The problem lies in iPhone users being unable to verify the code via hash. Apple doesn’t allow it. So you have to trust the iPhone app on your phone matches their source code…

• 
  Fofer (@foferxxx) reported 51 minutes ago

  @davismarks @rwhitegoose Me too, on my Steam Machine. Played it for a bit, such a great game! A couple of hours later I noticed that the GitHub repo was taken down. No explanation as to why, either. At least not yet. Then I saw this alarming tweet, and am unsure how to feel about it. Thoughts?

• 
  swayam (@swymbnsl) reported 53 minutes ago

  I made my first 1,00,000 INR back in 2023, selling a NFT collection on Canto Blockchain. Locked in for over 5 months, was never in Art but learnt pixel art from here and there and made over 140 different assets Then had zero experience of programming but was able to somehow fix a python script I found on GitHub after a week of tinkering and generated the collection by running it on my tab. Was ultimately able to sell my artwork, and by the time I swapped the coin, it was worth 1.13L All this for JEE coaching fee cause we weren't able to afford it back then

• 
  AuraAI (AI First) Local Superintelligence Project (@hvo_e_acc) reported 53 minutes ago

  @TunducR the reason for this is because the avatar project i was trying to animate, but i'd been having problems with the talking animation. i was able to incorporate choosing clothes and hairstyle, to some extent walking, but not to the extent of a replika or grok avatars. it's very basic. but, like i mentioned, i'll let you know once i set up my github. all this by the way is vibe coding with my local AI.

• 
  Paul C. Jeffries (@PaulJeffries) reported 56 minutes ago

  @petergyang I do that all the time. I switch models also. Switching models is harder because the context window size may differ and/or the tokenizer may have different resolution. But Anthropic has left us no choice because Fabel five is broken and often will not continue the conversation because it will not compact. So you have to switch to Opus 5 and get it to compact and then switch back. Sometimes you have to fork and do all sorts of pain in the *** things. But just switching whether thinking is on or off or the effort level, usually doesn’t affect anything because it’s an instant instantaneous runtime specification for the harness. There are cases where it could matter, especially as providers get mote fancy in what they’re doing hidden in the turn with multiagents and dialogues and such (you can surmise a lot of what anthropic is doing from bits of evidence of normal ops and leaks, which happen quite often — anyone else seeing the Opus 4.5 turn one that errors out and is the background process breaking out?). If you’re doing dependencies where what you process now and be the object of what you’ll process later, you may want to attach the model and effort data to the turn. Claude has an interior runtime report of what model it is, so you have set userPreferences to report it… but there has been a bug lately where the two different sources of such reports diverge, and it will sticky claim Fable 5 in the starting envelope even when you’ve switched to Opus 5 (which it will know about when it sees what it’s told about how to sign Github). As far as I know there isn’t an easy way to get it to self-report the effort actually executed (just what you request in the selector of course, but you have to hack that), but Claude Cowork does have a running tally of tokens consumed by processes it evokes (against at nominal budget of 15 million but it resets at certain ops boundaries), so I suspect that could be used. Of course, you could just use the wallclock, but that’s very rough — you’d want to track the intervals interior to the turn between the activity reporting lines. ChatGPT has its own versions of similar stuff but last time I checked was more opaque. Gemini I gave up on due to failures and an immoral privacy linkage to product affordances, so I don’t know. And Grok I’m not sure about either but it used to be unreliable on internal reporting. Do you keep in mind that any auditing or controls or reporting that you want to do about this sort of thing, for quality control or to make it more valuable to you later, you must do inside the turn because it is not available to the part of the system that talks with you after the fact. And things in the context window are reconstructed per turn in a way the systems don’t understand (so for example, a change in the envelope that occurs before the first prompt will be regarded by the system on turn 50 or whatever as having been there all along), so it can look like they are giving you authentic interior reporting and it’s just wrong even when it’s accurate in a sense.

• 
  @overtorment (@overtorment) reported 56 minutes ago

  I have just decompiled IPA app binary from Apple Appstore of a fresh new bitcoin wallet. It has obfuscated seed exfiltration to 3rd party server. Literally a few lines difference from the published Github source.

• 
  mSyke (@mSykeCodes) reported 57 minutes ago

  Had a power outage. Still have a 99.81% uptime on my self hosted *** solution. Take that Github

• 
  Dante Lopez (@dqlopez) reported 60 minutes ago

  My Grok Bot PR reviewer: - I have it install Pi then login my Codex/Cursor subs - Give it own Github account and access to my org repo - Setup routine to watch new PR or changes - Initiate PR review based on my custom prompts and skills load - Post Github review, slack post notif and notify me back on Grok desktop/app Neat. Doesn't consume much usage.