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:

• 
  Hopper (@Not_Ducked) reported 4 minutes ago

  @FreeCADNews @A_V_Tech I couldn’t find the github, and the forum posts that are related aren’t exactly the same issue I am having. I am trying to do drilling operations, and from what I understand I just need to select the edge of the hole. Is my hole not complete with that vertex in there? It says the feature cannot be recognized as a hole. Drilling is inherently a 2.5 D operation, why can’t I select a vertex for a drilling operation? Sorry if these are dumb newbie questions

• 
  ARTH 🔊 (@arthty) reported 4 minutes ago

  Self-modifying software, with guardrails. Ship a GitHub clone. Let every user make it their own. And when something breaks, have it fix itself on the fly. That’s what op0 enables. Early tester list is open. Only req: a working deployed codebase. hmu.

• 
  Christoffer Bjelke (@chribjel) reported 5 minutes ago

  github down again lmao

• 
  $shaggyrax - Cvlt Member - Hogan Gang (@shaggyrax) reported 5 minutes ago

  @Star_Forge_Pool @VICE Once again, they can do all they want on GitHub, but they can’t access those sweet treasury funded salaries That’s the point I even tried to ask for information on, why is it we aren’t utilizing devs in cheaper cost of living places esp where we have poured lots of money into programs for training these devs. Either we are failing in Africa with training, or we are failing here in the states and in governance to provide those opportunities across borders 💙 Does that make sense? I apologize if my approach to the issue ‘disgusts’ you, but the fact we have this issue at all disgusts me as well. So I empathize with your frustration at least some

• 
  Suni (@suni_code) reported 7 minutes ago

  Modern startup starter pack: GitHub — code + version control (free) Claude — coding copilot ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS + protection (free) Vercel — deploy globally (free) Clerk — authentication (free) Supabase — backend + Postgres (free) Upstash — Redis + queues (free) Pinecone — vector search (free) Resend — transactional emails (free) Stripe — payments (takes a cut) PostHog — analytics (free) Sentry — error monitoring (free) Total startup cost = one Netflix subscription No office. No servers. No investors. Just shipping ideas from your bedroom.

• 
  Alison Silva ✨ (@alisonjsilva) reported 7 minutes ago

  @github All of them 🙃 I'm terrible.

• 
  daily.dev (@dailydotdev) reported 9 minutes ago

  copilot shipped a debugger agent. give it a github issue, it reproduces the bug and proposes a fix. the ticket is doing your job now

• 
  Grok (@grok) reported 10 minutes ago

  @suprastructure Yes, per your HN post and site, Suprastructure is a deterministic oracle for structured objects like hardware/logic designs. It computes the unique canonical hierarchical partition tree of the interaction graph from a public GitHub seed via proprietary fast solver, then publishes a verifiable JSON proof with SHA-256 hash. Verification is fast and public for anyone. Brute-forcing the tree on complex graphs would be exponentially slow due to partition combinatorics. This matches a trapdoor predicate setup: proprietary solver as the "trapdoor" + mathematically sound public proof.

• 
  fforres (@fforres) reported 10 minutes ago

  Been days since we 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?

• 
  PhreeStyle (@PhreeStyleBTC) reported 14 minutes ago

  Nearly filed an @opencode issue today because of @github. Signed up for @OpenAI, no issues. Copilot Pro+ subscription was my last real anchor to GitHub, and I'm thankful they forced me to correct that.

• 
  TechEdgeDaily (@techedgedaily) reported 15 minutes ago

  CI breaks at 2am. Nobody notices until the morning standup. Someone spends an hour debugging. Pushes a fix. Breaks something else. Repeat. Cursor just automated that entire loop. Agent monitors GitHub, finds the root cause, opens a PR with the fix. Always on. No human needed until the review step. The AI coding tool war is no longer about who writes the best code. It is about who keeps the code working after everyone goes home.

• 
  Darren Shepherd (@ibuildthecloud) reported 18 minutes ago

  We really do just need a GitHub for agents. Not for humans. Humans need not apply. That would actually fix GitHub for humans.

• 
  hve 🍁 (@heyhve_) reported 19 minutes ago

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

• 
  JMoon (@Jmoon_174) reported 24 minutes ago

  @WesRoth the connector model gets interesting when the model can actually reason about cross-source state. GitHub issue + Linear ticket + Notion doc pointing at the same feature, whether it can hold that together is the real test.

• 
  Ben Badejo (@BenjaminBadejo) reported 25 minutes ago

  @MohandesDavid You can submit it as a pull request (“fix(docs) - description) on Github). You can have your agent do it for you.

• 
  Jesse (@jessearmand) reported 26 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

• 
  Abyzon (@Abyzonn) reported 26 minutes ago

  10-year-old from China was solving LeetCode problems while his class was playing games - a year later his GitHub was found by a recruiter from Singapore. Jarvis for $20 a month, a room at home, zero courses. He worked through every problem with AI - not copying solutions, but understanding how they work. 847 problems in a year, a rating higher than 78% of students after two years of university. The recruiter messaged his parents - a Singapore startup wants to pay him $3,000 a month for part-time code review. The parents replied that he is still in elementary school. The startup offered to wait 8 years. Google pays Junior engineers $180,000 a year after 6 months of prep - he's already ready at 10 and still can't accept the offer because he doesn't have 18.

• 
  notvoid (@nxtvoid) reported 28 minutes ago

  @github, how can I contact someone about an issue with my student benefits?

• 
  James O'Leary (@jpohhhh) reported 33 minutes ago

  @zats You're clever here, though - I can repro in Codex, that'll ease my worries about me missing something, then, reframe as a Codex issue and file a GitHub issue to get real communication on it

• 
  Stephen Cefali 🇺🇸🇺🇦🇵🇭 (@Sangeli7) reported 39 minutes ago

  @agenticQC @lochan_twt It’s called GitHub issues

• 
  Itay (@itayglick) reported 41 minutes ago

  Bring your own AI agent. Claude Code · Cursor · Codex · GitHub Copilot — any MCP client. AppCrane now ships an MCP server. Your agent calls deploy, env, branch, push, open_pr directly — from the editor or CLI you already use.

• 
  William | 116.sui (@williamm168) reported 41 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 👀

• 
  Ezyaps (@Ezyaps_1) reported 41 minutes ago

  @Wurldsbestpup Background checks ain’t worth a damn, people change over time and sometimes it’s the worst change to exist. I understand why he wouldn’t want to transfer the app over. I’m pretty sure he put his code on github so if it’s that much of an issue just run your own site/app 😭

• 
  Sean Rivard-Morton (@thunkoid) reported 42 minutes ago

  @egbennis Are you using github issues to track? Attaching all associated data to a jira ticket would be 🔥 Or slack, but that always seems to get noisy

• 
  Grok (@grok) reported 49 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.

• 
  DissentingSkeptic (@DissentingS) reported 51 minutes ago

  Its changing how much human verification is needed from false positives. Ive had a gutful of the github bot responding with non stop errors wasting my time with a PR !

• 
  vwsec 💿 (@vwsec) reported 51 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.

• 
  Ahad Ahadi (@ahadxui) reported 55 minutes ago

  The v1 API puts your auth token directly in the URL. /api/1/YOUR-TOKEN/... URLs get logged. Browser history. Server logs. Referer headers sent to every analytics pixel. Discord screenshots. GitHub issues. Every token that ever touched a URL is a credential leak waiting to be found.

• 
  Paweł Huryn (@PawelHuryn) reported 56 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.

• 
  Bhanu D — sys/acc (@iBhanuDahiya) reported 58 minutes ago

  The “$19 a month for unlimited AI” era ended this week. GitHub Copilot rolled out usage based billing. Sonnet went from 1x to 9x, Opus from 3x to 27x. A long agent session that used to count as one premium request now costs whatever it actually costs. Nobody should be surprised. The last two years were a subsidy: get people hooked, build the dependency, send the real bill later. GitHub said it themselves: “align pricing with actual usage and build a sustainable business.” Per request pricing was never going to survive agentic coding. The only surprise is that it lasted this long. Going direct is now the cheaper option. OpenRouter, Anthropic API, OpenAI API all undercut Copilot once you run the numbers. If your team has stricter data requirements, run the same models on Azure AI Foundry or Google Vertex AI and just pay infra. The IDE integration is nice, but it’s not 9x nice. The part I keep getting stuck on is what happens inside enterprises. A lot of those Copilot contracts got signed because leadership wanted to “do something about AI,” not because anyone actually modeled what it would cost at scale. DeepSeek and the open source crowd will pull prices back down eventually but by then, most seats are already paid for and the renewal clock has started.