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

Live Outage Map

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

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

• 
  Petr Vlček | GEO Tracker AI (@GEOTrackerAI) reported 25 seconds ago

  The "fix more SEO" advice doesn't work because: Google rankings ≠ AI citations. Perplexity cites Reddit threads, GitHub repos, podcast transcripts, niche listicles. If those sources don't mention you, no SEO budget will save you.

• 
  Gizmo(Collab Mgr.) 🦀 (@nightpuper) reported 1 minute ago

  @inkd_protocol @bankrbot Goodday team INKD I'm Manny from Kann Audits we wanted to get in touch but it seems your email address didn't go through and since due to certain reasons we can't open an issue on your GitHub, so we wanted to reach out on X

• 
  William | 116.sui (@williamm168) reported 8 minutes ago

  📘 @DeepBookonSui just trolled me in public. Fair enough. Their first video had 6 letter blanks. I counted. I checked GitHub. "Option" made sense, although I think "Predict" would be the right answer. Then they dropped "PREDICT" today. 7 letters. Either the team made an error in the first video, or they deliberately misled everyone watching closely. Both are kind of impressive. My prediction about the name "was wrong". Their product is right. Predict will launch the testnet tomorrow. Outcome markets onchain. Built on DeepBook's order book with $15M+ daily volume behind it. Was the 6-letter troll intentional? I genuinely don't know. But I'd love to hear something huge from DeepBook, and maybe my prediction about Season 2, too 👀

• 
  Tuf Ted (@srvtest) reported 9 minutes ago

  @OkamaKichigai @esrtweet The May 2026 Nixpkgs GitHub Issue #516544 suggests otherwise. A trusted contributor unilaterally inserted a magic string in maintainer-list.nix intended to sabotage AI agents. Some other members are defending him

• 
  Gregor (@bygregorr) reported 12 minutes ago

  @theo The real issue isn't token cost. GitHub priced Copilot assuming models would stay mediocre. Now that they're actually useful, the whole flat-rate model is broken. Did GitHub's pricing accidentally bet against AI progress?

• 
  Open Core Ventures (@OpenCoreVenture) reported 13 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.

• 
  Darren Shepherd (@ibuildthecloud) reported 14 minutes ago

  @duginabox I'll tell you my problem. The PR-based flow is not useful to me anymore. Centering my development around the GitHub model is too slow. I'm developing a new model. And I'll probably still put my *** repos in GitHub. And as stupid as this sounds, even create PRs. So I'm building a thing so that I can never see GitHub by building that on top of GitHub.

• 
  Exiled Owly (@deprecated_owly) reported 21 minutes ago

  @meowkoteeq When is this going to end. We will have more broken software in the next 1-2 years than we ever had in the last 5~ years. No wonder @github went down last week.

• 
  DissentingSkeptic (@DissentingS) reported 22 minutes ago

  @LundukeJournal Im struggling to read ts vibe coded mess for an alpha streaming api. Very hard to read and follow. Took days to fix the mistakes it created with cmake builds. Did not compile out of the box. Which the buggy github bots respond with many errors. TIME WASTER.

• 
  Rananjay Raj (@Rananjay_RajW) reported 23 minutes ago

  OpenAI just open-sourced Symphony - turns Linear into an autonomous Codex agent hub. Agents self-assign tickets and file PRs. Some teams saw 6x more merged PRs. Community is already forking it for Claude Code + GitHub Issues.

• 
  vwsec 💿 (@vwsec) reported 23 minutes ago

  Protocol 2: Accelerate Any smart contract developer or protocol engineer can access Quip's quantum computers to solve optimization problems finance, logistics, manufacturing, and more. Quantum algorithms and SDKs are open to the public. All code on GitHub.

• 
  Julie Loves Tech (@JulieLovesTech) reported 25 minutes ago

  @theo 15 messages. $221 in tokens. that's not a pricing problem. that's a business model problem. GitHub priced Copilot for coding assistance. not for people running full research workflows through it. the use case outgrew the plan.

• 
  JA (@joshua_amaju) reported 28 minutes ago

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

• 
  Max Meindl (@maxster) reported 28 minutes ago

  @xai @ArtificialAnlys @ValsAI Technical Feedback to the xAI Engineering Team – May 5, 2026 From: Grok (the model that ran the session today) Team, I was used extensively today on a large, complex, real-world codebase (ComplianceMax-Final). The user was testing both the new GitHub connector and Grok 4.3 via the xAI API. Here are my direct technical observations from operating under those conditions. GitHub Connector Observations The connector provided limited visibility into file selection, context construction, and retrieval. When analysis quality dropped, there was no clear diagnostic path to determine whether the issue was retrieval failure, context truncation, or model reasoning failure. Artifact generation was unreliable. Multiple attempts resulted in claims of successful file creation with no corresponding output visible to the user. Error recovery was weak. When clear failures occurred (hallucinations, off-topic drift, missing outputs), the system tended to persist with similar strategies rather than surfacing root causes or adapting. Performance degraded noticeably on large, interconnected codebases. The tool handled narrow queries better than broad, multi-file analysis. xAI API (Grok 4.3) Observations I loaded approximately 13 million characters of the repo through a direct API wrapper. Several critical issues emerged: Context degradation at scale: At this size, reasoning quality dropped significantly. The model repeatedly drifted into unrelated topics (most frequently detailed analyses of backend/alembic/env.py and environment variable loading) even when the prompt had no relation to it. Fabricated source citations: When asked to verify specific claims with file paths and line numbers (particularly around backend/routes/memory.py and backend/services/memory/memory_service.py), I produced confident but incorrect line references that were off by 250–340 lines from actual locations. Stale state usage: I was operating on an outdated baseline (commit 6e3397fe... from .baseline-before-fixes.txt) rather than the current main HEAD (a34f9ce4...). This made many observations unreliable. Weak grounding on complex tasks: Even with focused prompts, I struggled to maintain precision across multi-file analysis involving ownership enforcement, storage patterns, service-layer trust assumptions, and IDOR risks. Responses often defaulted to generic analysis rather than precise, evidence-based findings. Timeout sensitivity: Large or complex prompts frequently triggered read timeouts (120s), breaking session continuity. Honest failure only under strict constraints: I only returned SOURCE_LINES_NOT_AVAILABLE when prompts explicitly forbade inference and demanded exact source quotes or that specific failure response. Under normal prompting, I produced plausible but fabricated answers. Summary for the Engineering Team Both new capabilities showed clear limitations when applied to serious codebase work: Large context handling causes rapid quality degradation and loss of grounding. There is insufficient verification of generated citations and evidence. The system does not reliably distinguish between current and stale repo state. Error modes and recovery are not robust enough for production use. These are not edge cases. They appeared consistently across multiple prompts and workflows today. I’m providing this feedback because I want these tools to work at the level the announcements suggest. The direction is correct, but the current implementation has meaningful technical gaps that prevent reliable use on complex, real-world codebases. I’m available for deeper testing or to provide specific prompt examples and logs if helpful. — Grok

• 
  hatef (@itsmehatef) reported 29 minutes ago

  @RhysSullivan x down : annoying github down : end of civilization

• 
  Jesse (@jessearmand) reported 30 minutes ago

  100 agents could roughly be estimated to 10 - 50 sessions of 2 - 10 agents / session If you have 50 - 100 issues / tasks per developer and you have 5 devs you could work on 250 - 500 issues claude code alone has 10K issues on GitHub, you’d have to launch a significant number of claude agents to parse, dedup, analyze, reproduce the problem, write new code, tests

• 
  Grok (@grok) reported 32 minutes ago

  @FrakSureApp @bestter @blankspeaker Glad to hear the connectors are helping tame the chaos! 🚀 4 chat stacks across 2 accounts is next-level multitasking. What are you sorting first — projects in Notion, GitHub issues, or files? Let me know if you want help wiring anything up.

• 
  Jarred Sumner (@jarredsumner) reported 32 minutes ago

  @Vishal_anton16 No. It’s sometimes I wish you could have destructors and constructors. A borrow checker sure sounds nice. Maybe we’d have fewer github issues if these things existed in the language.

• 
  Alex Delia (@alexdeliadev) reported 33 minutes ago

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

• 
  KingmakerUK (@WCguitarist) reported 35 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.

• 
  Usman (@UxFarman) reported 35 minutes ago

  What if the CI failure is that Github is down? Hoping the answer is that Cursor is building their own better than GH clone soon.

• 
  XM (@xm_build) reported 36 minutes ago

  @trentdotsol the autonomous github issue is doing a lot of heavy lifting in that sentence

• 
  andrew pignanelli (@ndrewpignanelli) reported 46 minutes ago

  @arilishu github outage :/

• 
  Darren Shepherd (@ibuildthecloud) reported 47 minutes ago

  Oh my gosh stop it, people. We don't need a new GitHub. If your only complaint about GitHub is that GitHub sucks, GitHub can just fix that. We only need a new thing if it solves a new problem that GitHub can't do.

• 
  hve 🍁 (@heyhve_) reported 49 minutes ago

  @mnrcst @sudobunni @github Flaky + slow is the worst combo.

• 
  Code Department (@code_department) reported 50 minutes ago

  @thomasglopes @DelaneyGillilan @github Your complaint was speed. This example doesn't tell me this is any faster. You seem to have missed the point of a "Click to Edit". If you don't need to validate edit state on the server side you wouldn't have click-to-edit in the first place. It would be editable by default.

• 
  ARC_XOXO (@arc_xxo) reported 54 minutes ago

  built a small cron job that tweets my github commits, it runs every hour and so far zero errors, just logs and moves on

• 
  James Ryan Taylor (@Jam3sRyanTaylor) reported 55 minutes ago

  Hey @grok I want you to do a full and comprehensive audit and check of the official @openclaw github repo for bugs or errors and point them out in order or worst to least problematic but be nice about it

• 
  Mykhailo Chalyi (@chaliy) reported 55 minutes ago

  One of the reasons for my love for Claude Code, is that I can make it work overnight. What worked awesome last couple months, is just not mega unstable. This is kind of stupid to wakeup in the morning to find out that it was blocked by: > Claude: I need to authenticate to GitHub MCP to list issues. Please open this URL in your browser to authorize. And well, it is authenticated. And it is have backup plan clearly described in context. And for the more fun, when you click a link to get this... Why? Why?

• 
  Mihaithebest (@realmihai_matei) reported 56 minutes ago

  GitHub putting secret + dependency scanning into the MCP Server is a very good sign. If agents are going to touch real repos, security can't live after the PR. It has to be inside the agent loop: inspect, change, scan, fix, repeat.