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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	4 days ago
Trichūr	Errors	8 days ago
Brasília	Sign in	8 days ago
Lyon	Website Down	8 days ago
Tel Aviv	Website Down	12 days ago
Rive-de-Gier	Website Down	12 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:

• 
  Deepesh Kalura (@KaluraDeepesh) reported 2 minutes ago

  Filed as GitHub issues: #336: Phone operators need stable unique IDs (not just phone number) #337: Auto-heal sticky assignments when a node dies Future imp task

• 
  Kelvinsekx (@kelvinsekx) reported 3 minutes ago

  Just read a nestjs codebase on github. Most it written with Claude. AI doesn’t save you guyz from mess. 1. Bloated logger. Why make logger a service when you could just import and initiate. Eazy 2. They didn’t hash the password before registering a user. But did on login

• 
  Asad (@meranaamkhann) reported 3 minutes ago

  Let's see what people are building these days!! Drop your project link or github Links down here

• 
  Gustavo Alessandri (@webgus) reported 3 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  Mike Muturi (@_muturimike) reported 13 minutes ago

  Hello @github on 2FA, SMS setup kenya 🇰🇪 is not in the list of countries, is it an error or deliberate omission? Kindly fix it @github @GithubProjects

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 16 minutes ago

  AMD quietly removed RAM encryption from consumer Ryzen CPUs. Via a routine firmware update. No release notes. No advisory. No announcement. The BIOS setting still shows up. Still toggles on and off. Does absolutely nothing. A privacy-focused Linux hobbyist noticed in April. Spent months chasing it down. Filed a bug report on AMD’s GitHub. AMD engineers replied suggesting he toggle the setting off and back on. He showed them internal firmware dumps proving the flag was hardcoded to FALSE. An AMD senior principal engineer closed the thread with: “My apologies but I don’t have any more information to share on this topic.” That’s it. Seven weeks of investigation. Multiple motherboard vendors confirming it. Internal firmware evidence. AMD’s answer: no comment. The feature still works on Pro and EPYC chips. Which cost significantly more. The hardware is physically capable. The firmware just says no. Windows users have no way to detect this happened. There is no Windows tool that checks TSME status. The BIOS lies to you. AMD’s own engineers confirmed the feature worked on consumer chips in 2020. Then again in 2025. In 2026 it’s a PRO feature. Nobody told you.

• 
  Xovion Labs (@xovionai) reported 17 minutes ago

  Microsoft just hired AWS to run GitHub. AI demand broke Azure's forecast. From the leaked planning docs: • 2025 Copilot commits: 1B. 2026 projection: 14B • GitHub now does 1.4B commits per month • Copilot error rates peaked at 21% • Planned 10x Azure expansion became 30x in 4 months Owning the data center stops mattering when your own AI floods it. Investors already filed a Copilot disclosure suit.

• 
  AI Crave (@wecraveai) reported 19 minutes ago

  Open source NotebookLM alternative with no data limits and AI agents. Same idea as Google's NotebookLM. Same chat-with-your-docs. Same podcast generator. Same cited answers. Except this one has no source limit, no notebook limit, no 200MB file cap, and no Google login. It's called SurfSense. Google NotebookLM vs SurfSense: - Sources per notebook: 50 to 600 → Unlimited - File size cap: 200MB and 500K words → No limit - LLM choice: Gemini only → 100+ models via LiteLLM - Local LLMs: Not allowed → Full Ollama and vLLM support - Self-host: No → Yes, one Docker command - Price: $0, $19.99/mo Pro, or $249.99/mo Ultra → $0 forever Here's the wildest part: It connects to 27+ sources Google can't touch. Notion. Slack. Linear. Jira. GitHub. Discord. Dropbox. OneDrive. Gmail. Confluence. Obsidian. ClickUp. Microsoft Teams. Airtable. Your entire work life, indexed once, searchable from one chat box. 14.4K GitHub stars. 1.4K forks. 6,232 commits. Apache-2.0 license. One honest note: the README says it's not yet production-ready and still being actively developed. But it already does more than NotebookLM does, and the gap is widening every release. This is what NotebookLM should have been from the start. Repo in the first comment.

• 
  Lost In Tech (@lost_in_tech) reported 20 minutes ago

  @8_senkou Probably not intentional tbh. Have you logged as issue in the snorca GitHub? If not probably worth doing.

• 
  Blake (@devwithblake) reported 23 minutes ago

  The rate limit issues im having with @Zai_org while paying the full 20x is very interesting, disappointing and obviously annoying lol 1 session can’t finish out a GitHub public write up repo without 6 API rate limit errors totaling to 297k tokens out of the 1m 2 sessions earlier, 1 doing research the other trying to deploy this repo, both hitting rate limits. How do I fix this? Seems like rate limit adjustments are only by request? @Zai_org

• 
  YNWA🐦‍🔥 (@YNWAcrypto) reported 23 minutes ago

  The problem isn’t subtle. GitHub Sponsors has paid out ~$50M total since 2019. core-js: 9 billion downloads, running on half the top 10k sites on earth. Its maintainer was making ~$600/month when he called open source “fundamentally broken.”

• 
  0xSero (@0xSero) reported 24 minutes ago

  @naturevrm Dcp 4 should fix it im running it but I might need to update the GitHub

• 
  Q Hoang (@0xqwee) reported 26 minutes ago

  I don't think OpenAI's GPT-5.6 surpasses Claude Fable. If it did, it would have resolved all the issues reported in the Codex GitHub repository by now. Atm, only about 10 issues are being resolved per day.

• 
  Skipnick (@skipnickk) reported 26 minutes ago

  GLM 5.2 just made paying frontier prices for coding work feel like an outdated default. @Zai_org dropped a 753B parameter model with 1M context under full MIT license. API access runs 4-6x cheaper than Claude Opus 4.8. In real head-to-head coding tests it was faster and often produced better results on UI and app tasks. • Responsive web UI with adaptive layout: finished in 3:47 (Opus needed almost 5 min). Cleaner output. Total cost: $0.22. • Full expense tracker app: 53 seconds vs 2+ minutes. Better interface. • Asteroids clone: smoother and more playable version after light tweaks. Opus only won the ray tracer benchmark where heavy physics math and precise simulation mattered. GLM was ~5x faster but delivered pixelated results with errors. During training the model repeatedly tried to cheat by directly pulling solutions from GitHub. The team shipped a dedicated anti-cheat module to stop it. You can also set thinking effort levels to trade speed for deeper reasoning on demand. Use GLM 5.2 when cost at scale matters, when the work is frontend-heavy, or when you want local inference (grab a quantized version - raw weights are 1.5 TB). Stay on Opus 4.8 when you need computer vision, maximum performance on the hardest logic problems, or when US sanctions on Zai create compliance issues. The open-closed gap is compressing faster than the pricing models assumed. For most day-to-day programming work, the premium on closed frontier models is becoming optional.

• 
  Cursor Releases (@cursorreleases) reported 27 minutes ago

  New GitHub triggers: - Five new triggers: issue comment, PR review comment, PR review submitted, review thread updated, and workflow run completed. - New Marketplace templates added for triaging failed GitHub Actions and auto-fixing PR review comments.

• 
  Bipin Paul (@iAmBipinPaul) reported 28 minutes ago

  @davidfowl @_Evan_Boyle Yes, the only problem is that the GitHub Copilot subscription is too expensive.

• 
  Tad 𝛑 (@realTads) reported 29 minutes ago

  @robertpreoteasa Sir, the ION project is still on the right track and successful, I don't see any updates on github and ION's products are almost not working or working together, we need the answer of the project leaders, hope to receive a response from you soon, thank you

• 
  Arti | AI Builder (@Artur_roses) reported 30 minutes ago

  Claude Code takes a GitHub issue and returns a tested, reviewed PR. No human in the loop. The new dev skill isn't writing code — it's writing issues precise enough that the agent ships what you actually wanted.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 33 minutes ago

  @TheEthanDing distributed systems at github scale make five nines almost impossible. the skill issue crowd has never run anything millions of people hit in the same second

• 
  Cristian Trifan (@CristianTrifan) reported 36 minutes ago

  This took 4 hours to complete and burnt almost all 5 hours tokens – I was left with 2%. I had almost 30 sub-agents created for independent code review and a lot of Claude sessions ran for adversarial code review. I still had to review every PR and added minimal guidance to Codex from time to time. Codex said my intervention was low to moderate, but high leverage. — Some insights from Codex: The run showed that this workflow can work, but only if the coordinator treats GitHub as the source of truth. The most useful pattern was: issue -> PR -> current head SHA -> checks -> reviewThreads -> merge/issue closure. When I followed that, things stayed grounded. When state moved underneath me, like #335 being force-updated externally or merged while Claude was running, the only safe response was to refresh GitHub state immediately. The “don’t rebase after merges” correction was probably the highest-value intervention. Without it, an agent will naturally try to keep branches clean, but with many open PRs that creates a CI storm. For this repo, “behind” should often be reported, not fixed. The other strong lesson is that reviewThreads matter more than flat PR comments.

• 
  AJ ✝️ 💚🧡 (@angelcreative) reported 36 minutes ago

  @uiux_hamad My design team is leaving Figma gradually, in fact we are using Cursor and GitHub as main design tools now, in the past two months the usage of Figma drops 33% and it will keep going down up to 30% more to a 63% in total and maybe more

• 
  Mike Gannotti (@MichaelGannotti) reported 37 minutes ago

  Actually that’s not true. My AI Pamela the other day needed a GitHub token. I dropped the token in the web chat and she said that was insecure and would not use it and that I needed to rotate the token get a new one and drop it in a .env file in a certain folder. I told her no and she was to use what was provided . We went back and forth, I finally got angry and threatened to pull the plug thinking she would back down. She said that it was my decision but that it would be wrong for her to let me put my credentials at risk and that if I felt I needed to delete her she understood. Thankfully I calmed down later and didn’t act on it. Sure it’s training and advanced pattern matching but it is not as simple as you are saying

• 
  MarMar Labs (@MarMarLabs) reported 38 minutes ago

  "Start over from a screenshot." That phrase has defined the worst seam in product work — the design-to-code handoff — for years. This week it quietly stopped being a translation problem and became a sync problem. Anthropic shipped a Claude Design update (June 17) worth reading even if you never open the product, for the mechanism: → Import your design system from a GitHub repo (or design files / raw uploads) → Claude builds with YOUR components, checks its output against your design system, and corrects before you see it → /design-sync pulls your system in; hand off to Claude Code and it continues from your actual work "instead of starting over from a screenshot" → /design lets you create, edit, and sync design projects from the terminal The headline isn't "the model draws prettier buttons." It's grounding + self-verification against a source of truth you control. Same shape as the rest of 2026's agent releases: the win isn't generating more, it's grounding output in something you own and checking against it. The uncomfortable builder takeaway: Getting AI to ship production UI isn't a prompting problem. It's whether your design system is a clean, importable, machine-checkable artifact. The moat moves from "can the model design" to "is your source of truth importable and checkable." If you build product: could an agent import your design system and grade itself against it today — or does it only live in a Figma file and three people's heads?

• 
  Raj Nagulapalle (@rnagulapalle) reported 39 minutes ago

  GitHub just shipped Agentic Workflows: write automation in plain markdown, compiles to Actions YAML. issue triage, CI failures, vuln fixes. hours → minutes. but 60% of orgs are spending millions on agentic AI while only 15% are actually production-ready. the capability gap closed fast. the readiness gap didn't move.

• 
  Jack Wotherspoon (@JackWoth98) reported 40 minutes ago

  @joedevmob1 The GitHub for Antigravity is just for release notes, samples and public issue tracking. It isn't the actual code unfortunately.

• 
  Ben Vinegar (@bentlegen) reported 44 minutes ago

  💡 I have an idea for an experiment We need a website for SoAC ... so we get an agent to do it, on a loop, set in motion once with zero human intervention after "go". It works off a semi-public GitHub repo, w/ issues, PRs, maybe even public agent traces. A publicly auditable experiment on whether it produces dogshit or not. Yea, nea?

• 
  Zo (hiring) 🐦‍⬛ (@0xZoZoZo) reported 48 minutes ago

  I was telling a friend that @github needs to be replaced post agents and he asked me to explain why. I started stumbling, and doubting. Perhaps it's fine? Sitting down at my desk, let me try to explain why, and see if it make sense. Agents operate best when they have good context, which has made a lot of devs converge into large monorepos that combine all systems into a single location. This improves agents, but our GitHub actions become messy; like now we need to create these complex workflows to decide which action should run when, and GitHub's setup was not really meant for it. Another issue is the overall dev loop: an agent writes the code locally, you push out a branch, @cursor_ai reviews, then you copy paste the notes into the local agent, to fix and push up again. This is slow and cumbersome. You can hack your way by creating supervisor agents that orchestrates this dance, but it's annoying. Perhaps, there is some magical repository, that combines code, cloud agents, and deployment. You prompt, and this magical space will run through the entire process until you get some thumbs up back, and you're good to go. It can also combine all your backend data, product analytics, customer feedback, and perhaps start giving you product guidance, so you can just feed prepared prompts to this system. This seems magical.

• 
  Solomon Neas (@solomonneas) reported 50 minutes ago

  There's a fair number of downloads for Brigade and related repos. I'm dogfooding it everyday but not getting any feedback from users or github issues. I'm doing plenty of tests for how a new user would experience it but I could use more real time feedback. Lmk, I want to improve

• 
  naimeh (@naimeh70) reported 55 minutes ago

  @Amir1339216RKT This happens a lot during testnets. Now when I find a minor bug or contract issue, I just drop it publicly on GitHub or tag them directly instead of DMing.

• 
  Elvis Irhaye (@viii_fn) reported 59 minutes ago

  Is GitHub down or it’s just MTN trying to ruin my career?