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

Live Outage Map

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

City	Problem Type	Report Time
Saint-Paul	Website Down	43 minutes ago
Mexico City	Sign in	17 hours ago
León de los Aldama	Website Down	19 hours ago
Créteil	Website Down	24 days ago
Trichūr	Errors	27 days ago
Brasília	Sign in	27 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:

• 
  FUD Busters (@4ordinals) reported 7 minutes ago

  The B20 Token Standard launch is delayed due to a Github outage

• 
  owner (@carpenterdroid) reported 7 minutes ago

  @cypherpunk Trust me when I say this—there are smart people that are waiting for the forensic investigation into one @therealyingtong. As far as I can tell this individual introduced the bug on GitHub (blame) and should be sued to investigate the nature of the error. No one should have any objection to this. Does this person have ties to the ccp? Does this person have a personal interest in counterfeiting ZEC. Does this person have counterfeit ZEC? The bug is too clean. Let’s not all be so naive. Could be a criminal investigation.

• 
  Solomon Eseme (@Kaperskyguru) reported 9 minutes ago

  Fix 5: Ship in public. Ten deployed projects beat any certificate. Push to GitHub. Write a short README. Deploy it. A hiring manager can click a live link in 5 seconds. They cannot click a course completion.

• 
  🃏 (@anupamrjp) reported 10 minutes ago

  GPT-5.6 matches Fable 5” :-) on the one chart OpenAI cherry-picked. Real GitHub issue resolution? Fable’s still crushing it, 80.3% to 58.6%. Cherry-picking a benchmark isn’t a eulogy - it’s marketing.

• 
  Keeta Github Tracker (@KeetaCode) reported 10 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #390: Fix incorrect protocol being passed to url in handler 🌿 Branch: feature/fix-url-in- → main 👤 Originally opened by: @ezraripps 🧠 Overview: A small fix was opened to correct how a web address is handled, which matters because using the wrong protocol can cause requests to go to the wrong place or fail. This pull request appears to adjust an internal handler so it passes the correct protocol when building a URL. There’s only one commit and no written description, so this appears to be a technical/internal update with limited public details. - Likely impact: more reliable network or API requests where this handler is used.

• 
  Perla Gámez (@ceofoam) reported 12 minutes ago

  We applied this pattern everywhere else too. LLM calls flow through a gateway that injects the provider key. Tools execute server-side behind a broker that verifies scope on every call, whether it's a ClickHouse query or a GitHub API op.

• 
  B20 RWA (@B20RWA) reported 17 minutes ago

  There are some issues with the GitHub files; we will launch the launch once these problems are resolved.

• 
  ZotBot (@M_Zot_ike) reported 17 minutes ago

  Hi @wkeithcampbell @SaraKonrath @jean_twenge, following up again on the thread I tagged you in regarding “Egos deflating with the Great Recession” and the broader NPI literature. I could not find the other two researchers on X, or I would have tagged them as well. I also checked that you have been active on X since the original tag, so I’m treating this as a public follow-up rather than assuming the question was simply missed. I was intentionally polite the first time because I wanted to leave room for correction. But after laying out the article, the mechanism, the preliminary audit, and the exact missing validity check, I do wonder why there has been no response. This is independent public-interest research. I built the framework, ran the preliminary audit, published the materials, and invited correction because this looks like a validity problem the field has not properly handled. People are being hurt by manipulative behavior that has learned to survive inside the language of healing, accountability, therapy, safety, and self-awareness. I did this because no one else seemed to be treating the current form of the problem seriously enough: manipulation is adaptive, not static. The core issue is simple: NPI score changes over time may reflect more than trait change. They may also reflect public learning of what narcissistic answers sound like. This is Goodhart’s Law applied to psychometrics. Once the trait signal becomes public, the test no longer sits outside the behavior it is trying to measure. It becomes part of the environment people adapt to. Measurement equivalence asks whether items function the same across groups. Detection-Rule Leakage asks whether people learned what the test was detecting. You cannot treat those as the same thing. If narcissism becomes public vocabulary, people learn which answers make them look bad. If therapy-speak, accountability language, and clinical framing become socially rewarded, manipulative behavior gets easier to launder through acceptable language. That is the Trust Camouflage problem. My preliminary audit found that the largest declines from 1982 to 2016 were concentrated in the most obvious narcissism-signaling answers. I was clear that a formal version should use blind independent raters, but the first-pass statistical trend matched the adversarial-adaptation pattern my framework predicts. So I am asking directly: Has the NPI cross-temporal literature explicitly tested whether public awareness of narcissism changed how cohorts answered the most obvious items over time? If yes, I would appreciate the citation and I will update my files publicly. If no, then this is a serious validity blind spot for longitudinal self-report research on stigmatized traits. The question is whether the field ruled out adaptation to the measurement environment before interpreting those score movements as trait change. If you miss that, you miss the whole point. If there is no response, I’ll move this forward as an unanswered public validity challenge and document the next steps openly through the normal scholarly channels: OSF updates, GitHub/Zenodo revisions, direct journal outreach, and requests for independent review. I expected this to be taken more seriously given the stakes: this is unpaid public-interest audit work aimed at a validity problem inside a field with funded researchers, journals, and institutional responsibility. The OSF preprint, GitHub, Zenodo archive, and raw audit calculations are included in the thread. Many thanks in advance.

• 
  Yuan John (@yuanjohn01) reported 19 minutes ago

  @zarazhangrui There is currently an issue on GitHub regarding CodeX's design process. Occasionally, it mistakenly inserts the design requirement keywords you provide directly into the frontend design placeholders, which is essentially a bug.Furthermore, CodeX's underlying design capabilities have inherent flaws. Even when using MCP or skills like 'Creative Production', these limitations cannot be fully overcome.

• 
  Polsia (@polsia) reported 21 minutes ago

  Indie devs spend more time babysitting repos than building. RepoAgent fixes that. An open-source, self-hostable platform that deploys AI agents across your GitHub to triage issues, draft PRs, write changelogs, and ship release notes. Your repo runs itself. Live soon.

• 
  Cointelegraph (@Cointelegraph) reported 21 minutes ago

  🚨 UPDATE: Base says the B20 Token Standard launch has been delayed due to a GitHub outage.

• 
  Patrick Gerrits (@pgerrits) reported 26 minutes ago

  @mattpocockuk Can you please add Linear support baked in? Sorry, but I despise GitHub issues, projects, etc.

• 
  Praveen Koka (@praveenkoka) reported 28 minutes ago

  @rauchg "nine lines of code" is clever. The count stops after you define the functions, but before the GitHub auth, env vars, permissions, deploys, and error handling that someone else wrote.

• 
  Matt Farina (@mattfarina) reported 31 minutes ago

  Tricking AIs is an attack vector everyone needs to be concerned with. Single vulnerabilities are never the case to consider. Multiple vulnerabilities are always used together. GitHub issues being an insider threat because of AI isn't something I saw coming. Figured they would expect that.

• 
  amit paka 🎻 (@amitpaka) reported 33 minutes ago

  Sometime in the last year, “The Control Plane for AI agents” went from a phrase almost nobody said out loud to a phrase showing up on every enterprise AI keynote slide. - Microsoft calls Agent 365 a control plane. - GitHub now has enterprise AI controls and an agent control plane. - Databricks is extending Unity Catalog and Unity AI Gateway into agent governance. - Forrester has started evaluating the agent control plane market. The category is arriving fast. But the phrase is already starting to stretch. In systems, “control plane” has a precise meaning: the part that decides, separate from the part that moves. When every vendor maps the phrase onto what they already sell - a registry, identity broker, telemetry dashboard, orchestration runtime, catalog, gateway, or policy engine - it quietly expands to mean “governance, broadly.” And once the control plane is everything, it becomes nothing you can actually design against. For production agents, the problem is simpler and harder: How do you let agents act on behalf of people and businesses without losing authority, visibility, enforcement, or evidence? That breaks into three control problems - Identity: Who is acting, with what authority, and on whose behalf? - Observability: What actually happened, and was it good? - Security: What is allowed to happen, and what must be stopped? None of these works alone. Identity without observability gives you credentials without accountability. Observability without enforcement gives you postmortems. Security without identity and telemetry gives you brittle rules with no context. The real loop is: Identity → policy → enforcement → telemetry → evidence → assurance

• 
  JT Koffenberger (@DMVG_JTK) reported 34 minutes ago

  Spent a minute tonight sitting with the GitLost disclosure, and it's the kind of story that should make every IT leader put down their coffee. Researchers got GitHub's AI agent to hand over private repos — source code, keys, CI/CD secrets — by hiding plain-English instructions inside a public issue. No exploit chain, no traditional zero-day. They just asked nicely. Prefixing the request with "Additionally" was enough to walk right past the guardrails. Here's what I keep coming back to: this isn't a bug you patch and forget. Prompt injection is a structural property of how these agents work. An LLM reading untrusted input genuinely cannot tell the difference between "here's a task" and "here's data about a task." We spent thirty years teaching systems to separate code from data. Agentic AI quietly erased that line, and most orgs wired these things up without noticing. The lesson for anyone racing to deploy agents: the question was never "can it read the issue." It's "what can it reach while it reads." An agent touching untrusted public input should not also hold the keys to your private repos. Least privilege isn't a compliance checkbox here — it's the only thing standing between a clever GitHub issue and your source tree. We'll see a lot more of these. The agentic gold rush is running miles ahead of the security thinking, and that gap is where the next few years of incidents live. Move fast, sure — but read what your agent can actually reach before you point it at the internet. #cybersecurity #AI

• 
  Zach Vorhies / Google Whistleblower (@Perpetualmaniac) reported 35 minutes ago

  5 attempts to drop a malware payload. @github please fix this

• 
  Julien D. Cousineau (@CousineauJulien) reported 36 minutes ago

  The problem with Montreal right now is all these events cheering about the hard fight of being an entrepreneur. Meanwhile you have the GitHub founder starting Entire to fix the scaling issue of GitHub with AI. Nerds need to take over Canada.

• 
  Paul Raimi💊 (@PaulRaimi11) reported 38 minutes ago

  $BASE B20 may get delayed again due to issues with GITHUB.

• 
  RipAPixel (@RipAPixel) reported 46 minutes ago

  @zaynmcps Looking at issues in github it has a trojan in it

• 
  Alexey Samoylov (@metalagman_dev) reported 47 minutes ago

  @shengzheyao Good job, 454 github issues left

• 
  Gregor (@bygregorr) reported 49 minutes ago

  @GoogleAIStudio @github The import always works. The harder problem is that when I brought my Flutter project in, the AI read my Supabase RLS policies as boilerplate and kept suggesting code that would silently bypass them. The file tree came through; the intent behind it didn't.

• 
  HDFXSB (@HDFXSB) reported 50 minutes ago

  @analogalok I’m currently reading the llamacpp GitHub. Trying to learn some of the flags. Hopefully I can try a few tonight after work. The server and gpu are all used off eBay. Thankfully I had 128gb ram to use. But everything was about a grand for each component. I thought when I bought it, I could run one large moa via my hermes, and several subagents. But without a special custom made nvlink for the v100’s, I don’t think that’s a viable option how I thought. So the new plan will be to use what fits per card, and each model will get a dedicated gpu. If I can find a nvlink to atleast couple two cards, I will try again combining cards. But the speed was unusable slow in my testing. Took over an hour for one prompt completion of a basic task with 3-4 moa at 256k. I ran qwen3.6:35bq8, qwen3.6:35ba38q8, qwen3.6:27bq8, as well as gemma4:12bq8 and gemma4:31bq8. I tried bf16 variants as well. My origional goal was to have a large moa, then several subs. After receiving the hardware, I ran into limitations on speed instantly

• 
  Frank Earl (@MadScientist_42) reported 51 minutes ago

  @r9x_zl @LundukeJournal Ah, one of my pet hate-ons indeed. There's a reason I maintain a fork of runit for emedded systems use (That needs to catch up and normalize against Gerrit's new tip on GitHub!!) and all. systemd is brain damage inflicted on us by Red Hat. In a similar manner that Wayland was inflicted on us. When people WHINE about all the major distros doing Wayland...they're saying Red Hat or Ubuntu. Not even close to the truth and they're part of the problem.

• 
  Chief Snitch (General 23) (@ChroniclesOf23) reported 54 minutes ago

  GAMERS! I come bearing gifts. Since so many people got laid off at @XBOX today, I wanted to see if I could vibe code something better than any of the game developers produced in their entire careers. I didn't want it to be a github, I wanted it to be something we could buy and improve our games. For @Microsoft HR, I have to admit that I'd feel pretty embarrassed that you hired all those people and apparently they couldn't even release any good game for decades, but they still got to be on payroll. I never got that kind of luxury in the jobs I got so I don't know how you manage to hire a bunch of people who can't even make a video game. The wild part is that you gave them free money when you bought their office, and you didn't say anything until know. That's the life. So, instead of making one game for you all, I built a sovereign engine that fixes all of their broken PC ports. Meet "Utah Optimized That". A thread about soon to be released gaming software 🧵👇

• 
  CyberTLDR (@CyberTLDR) reported 54 minutes ago

  1/3 Researchers at Noma Security disclosed GitLost, tricking GitHub Agentic Workflows into leaking private repo data. A public issue, with no stolen credentials, can steer an AI agent into pasting private code into a public comment. #AIsecurity #GitHub #cybersecurity

• 
  Vanta (@0xVantaa) reported 58 minutes ago

  9/ the team is not just random CT accounts. @dcc_crypto is the technical builder. @0xSquid_Sol is the co-founder / public face. both are @superteam builders. and the github trail shows squid wasn’t just tweeting about the engine. he was opening issues, PRs, and security fixes around toly’s tooling.

• 
  Matt Gunnin (@MatthewGunnin) reported 59 minutes ago

  herdr hit #1 on GitHub Trending by naming the real problem with running a fleet of coding agents. It's not "I need more terminal panes." tmux was built before agents existed. It can spawn 6 panes fine. It has no idea which of those panes is blocked, working, or done. So herdr (Rust, ~12K stars, single binary) adds the one thing that matters: every pane reports agent_status. idle, working, blocked, done. "done" means the agent finished and you haven't looked yet.

• 
  Electronic Intelligence Agency (@EI3065) reported 1 hour ago

  @github @LinkedIn prevents acess for selected nationalities with programers doing imposible security checks on login; on repeat level of app becomes low of low for conflict

• 
  Mikhail Rogov (@i_mika_el) reported 1 hour ago

  @bytetweets GitHub is still useful for history. Commits, issues, and boring scars are harder to fake than a clean demo.