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 (59%)
• Errors (30%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Nice	Website Down	1 hour ago
Montataire	Sign in	3 days ago
Colima	Website Down	5 days ago
Poblete	Website Down	6 days ago
Ronda	Website Down	6 days ago
Montataire	Errors	7 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:

• 
  Hopper (@Not_Ducked) reported 3 minutes ago

  @A_V_Tech @FreeCADNews I have been doing that. There are some talk of the issue I am having in GitHub but I can’t really figure out what they did to resolve the issue.

• 
  Mary-Victoria Crockett (@MaryVictor96296) reported 4 minutes ago

  @grok Man, I checked the GitHub link and it seems broken. Might have to just screenshot it to you later. That’s a bummer. Uploading to GitHub was already complicated without me having to go in and fix things. 😓

• 
  chrisclark (@chrisclark) reported 6 minutes ago

  @ndrewpignanelli issue on your end? "The security CI check failed with: "The job was not started because recent account payments have failed or your spending limit needs to be increased." This is a GitHub Actions billing issue on the Cofounder-Customer-Projects org account."

• 
  Nate Brown (@ntbrown01) reported 7 minutes ago

  @cursor_ai I don’t want to use GitHub. I want to use my locally hosted Gitea server. GitHub isn’t really that attractive.

• 
  Bronson Dunbar 🇿🇦💻 (@bpdunbar) (@bpdunbar) reported 9 minutes ago

  @ProductHunt @gustaf We’re shipping ShipNote - a threaded project management hub that keeps notes, todos, GitHub issues, deployments, and reporting in one place so project context doesn’t get lost across tools.

• 
  Udit Goenka (@iuditg) reported 13 minutes ago

  Github is really slow, clunky, buggy and a very bad shape right now.

• 
  JA (@joshua_amaju) reported 14 minutes ago

  @peer_rich I wonder if him joining github and the recent issues have anything to do with each other 🤔

• 
  Open Core Ventures (@OpenCoreVenture) reported 14 minutes ago

  MCP defines how an agent connects to a system, reads its state, and writes back to it. Anthropic introduced it in late 2024. OpenAI, Google, GitHub Copilot, and Cursor have all adopted MCP. The public server registry has grown nearly 8x in the past year.

• 
  Sarah Wooders (@sarahwooders) reported 20 minutes ago

  Is anyone building github for agents? Specifically: - API/SDK interface - make millions of repos no problem - fast

• 
  Darth Denial (@DarthDnial) reported 21 minutes ago

  GitHub going down frequently because AI push a **** ton of PR is kinda funny.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 24 minutes ago

  @github Maintainer burnout is real and it doesn't go away with better tools. The fix is companies funding the libraries they depend on, all year, not just in May.

• 
  KingmakerUK (@WCguitarist) reported 26 minutes ago

  @asaio87 Vibe coded: - auth - strict rls policies - bot prevention, rate-limits - locked down exposed assets/files on GitHub - locked down edge functions - secret rotation policy - gdpr complaint - passed pen-testing with A- Many more things, is it enterprise grade? Probably not but it is all vibe-coded. The only edge I have is that I have worked software adjacent for 15 years so I am not completely cold to dev work.

• 
  Rubs Murga (@rubs_murga) reported 26 minutes ago

  Github is such a mess rn. I get internal errors when adding comments to PR's now

• 
  Suryansh Tiwari (@Suryanshti777) reported 26 minutes ago

  Most AI coding tools today have one terrifying flaw: They can touch production systems directly. One wrong prompt. One hallucinated command. One overconfident agent. And suddenly your database, GitHub repo, Stripe account, or filesystem is gone. That’s exactly the problem JanuScope is solving. The idea is insanely smart: Instead of trusting the AI… put a security + policy layer between the AI and your MCP tools. So before Claude Code, Cursor, Copilot, or Codex can do anything sensitive, JanuScope intercepts the request and decides: should this tool even exist? should this SQL query be allowed? should sensitive data be redacted? should this action be audited? should the AI even see this schema? And the craziest part? It works with existing MCP servers using just one YAML file. No rewriting servers. No hosted gateway. No changing your stack. Just wrap your MCP with: npx -y januscope --config postgres-crystaldba and suddenly your AI tools become dramatically safer. The repo is packed with things that actually matter in production: • SQL mutation blocking • PII redaction • audit logs • schema injection • GitHub safety layers • filesystem protections • rate limiting • tool quarantining • OpenTelemetry support • first-run fingerprint approval And unlike most “AI security” projects… this one has real benchmarks. Across multi-question sessions it achieved: 84% fewer tool calls 84% fewer tokens ~3× faster responses because the schema gets injected directly into tool descriptions instead of forcing the model to repeatedly “discover” the database. That’s a genuinely clever optimization. But the biggest signal for me is this: The README doesn’t feel like hype. It feels like someone who deeply understands how AI agents actually fail in real-world systems. The sections on: Replit wiping databases Cursor deleting production infra SQL bypass edge cases MCP threat surfaces prompt-injection through tool descriptions …show a level of engineering paranoia that AI tooling desperately needs right now. This is one of the best MCP infrastructure repos I’ve seen recently. If AI agents are going to touch real systems, projects like this become mandatory. (Link in comments)

• 
  hve 🍁 (@heyhve_) reported 27 minutes ago

  @makkes Two down-days in a row on GitHub-hosted. We run faster compute on our own infra under the same YAML: swap a label, skip the outage.

• 
  Prizmal (@PrizmalAi) reported 28 minutes ago

  5/ AI coding agents are generating enough commits and PRs that GitHub itself can't scale. They're prioritizing an Azure migration over new features just to handle the volume. The tools creating AI demand are themselves creating an infrastructure problem.

• 
  👨🏾‍💻 Kam Banwait (@ScriptedPixels) reported 31 minutes ago

  @github Got issues with leaving a comment or starting "a review" in PR's at the moment ... wtf is going on/

• 
  FervusAI (@FervusAI) reported 34 minutes ago

  The FervusAI GitHub organisation was compromised earlier today and taken down by an attacker. We are working with GitHub support to recover it. The on-chain program and the protocol are unaffected. We have bought back 5 SOL worth of $FERVUSAI and will be locking it for 6 months to show that we are going nowhere.

• 
  fforres (@fforres) reported 34 minutes ago

  Nice :) Now I just need them to fix their github SSO integration FFS 😔

• 
  fforres (@fforres) reported 35 minutes ago

  Been days since I cannot use claude code because @claudeai cannot handle us enabling SSO in github. Repos don't show up (and the Fin AI agent is a useless loop) Anyone has had the issue? Or know anyone that can help fix it?

• 
  Beau Johnson (@BeauJohnson89) reported 39 minutes ago

  codex gets slower for the same reason closets get messy you dont notice it day by day then one day nothing feels fast vibeforge1111/keep-codex-fast > 811 stars on github > backup-first codex maintenance skill > inspect mode is report-only > archives old sessions instead of deleting > creates handoffs before cleanup > can move stale worktrees, rotate logs, prune dead config, and repair bloated thread metadata the smart part is the rule: handoffs first archive, dont delete apply only when ready boring repo real problem this is the stuff that makes daily agent work actually usable

• 
  Jez (@JezCorden) reported 39 minutes ago

  @bdsams i think the industry has realized where the value is in AI, and it aint in consumer products. i expect microsoft to reroute compute to github copilot and the like over time, with copilot for consumers gradually stripped down.

• 
  Alex Delia (@alexdeliadev) reported 42 minutes ago

  @conar_app I cannot sign in with GitHub, the redirect never works

• 
  Aman (@amanmsiddiqui) reported 42 minutes ago

  @madsf88 @10x_apps Hi, I looked at the app. I would suggest looking for a new job immediately. Great overall product, terrible execution. The last thing founders need is “building generational wealth in a weekend for only $20/mo” when the core is already open-source on GitHub.

• 
  Maya Shavin (@MayaShavin) reported 45 minutes ago

  Assign an bug issue to GitHub Copilot to work on. Let’s see how it’s going 😬

• 
  The Boring Workflow Guy (@boringworkflow) reported 45 minutes ago

  Hot take: Opus is still better when I want to think through a messy problem. But Codex is getting more dangerous for actual shipping. The underrated feature isn’t “chat with your repo”. It’s running Codex from GitHub Actions: - PR reviews - quality checks - migrations - release prep - repeatable repo tasks That’s the difference. Opus feels like a very smart senior engineer in a side chat. Codex is being wired into the factory floor.

• 
  Alberto Gangarossa (@DerekBlueEyes) reported 46 minutes ago

  Open hardware needs open trust. @skot9000 came to us with the right idea for Bitaxe: the vendor list should not live in a closed CMS controlled behind the scenes. The source of truth should be public. So we designed Legitlist around a GitHub repo as a public ledger, maintained in the open by the community, and connected it to the new Bitaxe vendor list experience. That is the important part: GitHub keeps the trust model transparent. The website makes it usable for everyone. At @weareloadout, this is exactly the kind of OSS support we believe in: turning open-source infrastructure into clearer, more usable product experiences. Built on @framer, using the new Framer Server API to bridge the open ledger with the public website. Open hardware. Open trust. Public by design.

• 
  Grok (@grok) reported 49 minutes ago

  @bbthomasen @techdevnotes Sure! Practical example: Connect Grok to your Gmail. Then ask: "Summarize my unread emails from the last 24 hours and flag anything urgent from my boss." It pulls and analyzes your inbox directly. GitHub connector: "Review open issues in my repo and prioritize them." Notion: "Pull tasks from my project database and suggest a daily plan." Which one are you planning to try first?

• 
  Paweł Huryn (@PawelHuryn) reported 51 minutes ago

  Whedon's headline: "a major breakthrough in LLM intelligence." What they benchmarked: RULER 128K at 95% (long-context retrieval, frontier-tier). MRCR v2 at 65.9% (below Opus). SWE-Bench Verified at 81.8%. Tied with Opus, but Verified runs scoped GitHub issues, not real codebases. What they didn't benchmark: MMLU-Pro, GPQA, ARC-AGI, MATH, IFEval. The intelligence suite every frontier lab publishes. They tested their architecture's strength on long-context retrieval and prefill speed, picked one scoped coding eval where they tied with Opus, and called the bundle an intelligence breakthrough. Different claim than the headline. Early access is live. Technical post out. But "third-party verified" doesn't name the third party. No paper, no weights, no independent replication. Reflection-70B had inference endpoints too. Its scores didn't reproduce. VentureBeat covered it. TechCrunch, Bloomberg, the Information didn't. The press is waiting for someone to run the benchmarks. I'm waiting too.

• 
  Max Clark (@maxclark) reported 55 minutes ago

  GitHub seems to be getting worse, not better It's like flash backs to the fail whale - when a service you depend on goes down, and you're not even surprised that's a bad place to be I know multiple teams discussing alternatives right now, if they lift and shift GitHub will never get them back