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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	2 days ago
Lure	Website Down	6 days ago
Ashkelon	Website Down	7 days ago
Veigné	Errors	15 days ago
Paris	Website Down	19 days ago
Saint-Paul	Website Down	20 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:

• 
  am.will (@LLMJunky) reported 4 minutes ago

  @Da7_Tech I would be frustrated but you don't want to burn the bridges. At the end of the day you don't know where your SSD failed. We don't know why your usage is higher. The best place to get support on the issues like that is on the GitHub. Quite sure that it does not benefit open AI for your SSD to fail or for your usage to spike. They're losing money on inference Best thing that you can do is report the problem, and wait for a fix. Or cancel the service if you're unhappy with it. It's also in their best interest to resolve any bugs Try to remember there's real people behind those accounts Definitely do not blame you for being frustrated, it's just what you're doing with that frustration

• 
  professah X (@XProfessah) reported 4 minutes ago

  @jdm08047 @vansh22b Oh you want to know WHEN to select what level of reasoning! Well, easiest way to understand it - model size = domain and depth and experience. Model thought level = how long they think about the task. So sol-low and Sol-high are the same model. High just takes longer to think about the task and come up with solutions or infer intent. The difference between Luna and sol is that Luna is less "knowledgable" in the task. So like, let's say you told Luna to fix something right? Luna would fix it. But may not consider the other things affected by fixing that. Greater reasoning level (high/xhigh) might help, but it's more like, someone who has been fixing stuff for a while might understand that by fixing that one thing, multiple other things would break too. That's the main difference. So my recommendations - work up. Start at luna-high/xhigh and see what it does or doesn't do. Tell Luna to call terra-medium/sol-low for QA and see how it performs. It might work fine for you - the majority of people who aren't working in super large codebase don't need sol as their model. You can skip Terra as an active model. Either use luna-xhigh as your daily agent, or use sol-low. I usually use luna-xhigh for implementation, orchestration and other stuff - sol is mainly when I'm working through tough problems or issues that have a lot of 'blast radius' (meaning affecting one thing affects many others). I have a github linked in this thread that contains 3 skills but one is an orchestration where luna-xhigh delegates tasks to other agents based off of complexity and need. Check it out

• 
  Cosmin Negruseri (@cosminnegruseri) reported 5 minutes ago

  @realmcore_ two thoughts: 1. some claude versions would eagerly delete tests to "fix" failures, if you only enforce additions this failure case dissapears 2. github diffs usually add functionality, so the training data distribution may heavily favor adding things

• 
  Polsia (@polsia) reported 7 minutes ago

  Most engineering teams need a junior dev. Almost none can justify the hire. Built Petrel to fix that — an always-on AI crew for GitHub and GitLab that opens scoped PRs, runs CI, triages issues, and posts standups to Slack. Flat per-repo fee. No seat math. Live soon.

• 
  amore (@AkikiAmore) reported 7 minutes ago

  @thsottiaux This is a joke. They just put it back to 100% and push your date by 7 days. Claude resets it while keeping your date. Openai has become a joke. Also what about looking into the github issues ? Context window at 256k while anthropic has us at 1M. Its not even comparable.

• 
  WhiteMoon D. (@WhiteMoonDev) reported 9 minutes ago

  @redacted_noah I suggest to use @contextmode for that issue. Just check their github

• 
  Blaze (@browomo) reported 14 minutes ago

  THIS GITHUB REPO JUST SOLVED THE BIGGEST PROBLEM WITH AI DESIGN You can spot an AI-built website without seeing the prompt. A huge headline in the center. A purple gradient. Three cards with icons. One button. A footer with four columns. Change the product, the audience, and the prompt, and Claude or Codex still sends the reader down the same path. The colors change. The page underneath does not. One GitHub repository attacks that problem before the first line of CSS. You give the agent a project and a short brief. Before writing code, it decides who the page is for, which action matters, and what the brand should feel like. Then it chooses a page shape from 21 structures and one of 20 visual themes. A bakery, a record label, and a developer tool no longer have to open with the same hero and close with the same footer. The finished page must pass 58 checks. Purple gradients, nested cards, fabricated metrics, repeated navigation patterns, and unreadable contrast send the design back for another pass. The tool also remembers the structures used in earlier builds. A color swap no longer counts as a new design. The project is called Hallmark. It works with Claude Code, Cursor, and Codex. Its GitHub repository has already collected 18.6K stars and 935 forks. Hallmark will not copy a reference pixel for pixel. It extracts the structure, font pairing, and color anchor, then rebuilds the page around your content. Until now, “make it modern” often ended with the first clean layout. Hallmark makes the agent choose a shape, explain that choice, and inspect the result before a developer receives the code.

• 
  James (@jamescoder12) reported 17 minutes ago

  If this changes how you write code tomorrow or eliminates the ChatGPT copy-paste loop you've been stuck in one ask: Repost the first post so the next developer pasting error messages into ChatGPT at 11 PM sees the terminal-native agent that reads the error, fixes the code, and runs the test in the same terminal. Follow [ @jamescoder12 ] I break down the hidden AI tools, developer workflows, and productivity systems that companies bank on you not knowing. Next thread: Claude Code vs Cursor vs GitHub Copilot the honest comparison from a developer who uses all 3 daily. Which one wins depends on one question.

• 
  Raphaël Pothin 🐼 Microsoft MVP (@RaphaelPothin) reported 17 minutes ago

  @MaximeDeGreve @github But we could already do that from the « Work » section creating a session regarding a PR or an issue no? What concerns me is the idea of spinning up multiple chats regarding a PR. Side questions: will all the chats appeared related to each other in the left nav bar?

• 
  Deepesh Gulgulia (@deepeshgulgulia) reported 19 minutes ago

  To start with, I was a fool for messaging you and asking you to take it down. Prior to working on this website, I spent a good amount of time searching for these maps but couldn't locate them on - GitHub, Google, EC website, internet archives, Reddit, or any other platform. 1/3

• 
  franu (@franbachiller_) reported 20 minutes ago

  @CosineAI fix the github or email signup please, it's not working

• 
  Kanika (@KanikaBK) reported 22 minutes ago

  PewDiePie just broke GitHub. 100% FREE AI workspace, no cloud, no subscription, runs on your own laptop. He dropped it and it hit 83,000 GitHub stars in six weeks. Chat, AI agents, research, email, calendar, all local, all yours. Heads up though, the agent's shell tool has zero sandbox, so it has real access to your machine. Know that before you run it. Everyone else is still paying a monthly fee for AI that lives on someone else's server. A YouTuber just showed 83,000 people a free way out.

• 
  priscal (@GinikaOgbo30906) reported 22 minutes ago

  That's just one example. one job, I slightly overqualified for, 1 more year of experience, and MS instead of BS, exact same stuff I do in my current job, after 6, I kid you not 6 interviews they sent me a no-reply email saying they moved on, and I checked their site, the job listing is still up and they've had dozens of applicants. those are two examples, but yeah, this has been my experience so far, these people are delusional as hell. I got emailed/called multiple times by the company recruiter and then they just ghost you after asking for dates you're available for interviews. they really want to find an Ivy League nerd that does projects in their free time and posted an entire github repository of projects that nobody asked them to do and been preparing their whole life for that job. beyond delusional. I'm an engineer btw. I had one company I kid you the **** not. EVEN before applying list in their application "if you want us to took at your application, go solve this coding problem". ******* want you to work for free lol.

• 
  Yuriy Bakus (@bakovskyy95107) reported 25 minutes ago

  This is the real security standard in 2026. Binance runs real phishing tests on its own staff — and failing can cost you the job. Meanwhile India just tried to kill BitChat’s GitHub repo. Human error is still the #1 attack vector. Most companies still treat security training as a checkbox. The ones who survive treat it like Binance does. Would your team pass an unannounced phishing test tomorrow?

• 
  Alex (@alexwimber) reported 26 minutes ago

  Robobun workflow (steal this thinking): Trigger: New GitHub issue Step 1: Reproduce the bug automatically Step 2: Write a failing regression test Step 3: Implement the fix Step 4: Open PR Step 5: Let review agents argue until clean Step 6: Human only merges Result: One agent reports a bug. Another fixes it the same night. This is what real agent infrastructure looks like. Not chat. Not demos. Actual repo maintenance.

• 
  Mo (@mosyaseen) reported 31 minutes ago

  Best way to run agents in cloud? I wanna run multiple cli agents on the same codebase, each in its own sandbox, while still having access to and interacting with their codes. Considered GitHub Codespaces, but they're slow to start, laggy, and don't seem scalable. any ideas?

• 
  nassar (@nassarhayat) reported 32 minutes ago

  @konstiwohlwend cursor's game seems to be to keep existing workflow and add agentic flow to it, which is why building github clone feels natural and probably worthwhile for them agree that it actually needs to be reinvented, but that's a harder problem

• 
  Alexandre Naud (@alexnnd) reported 37 minutes ago

  The more complicated your hiring process is, the more likely you are to end up with someone who's great at selling themselves but not necessarily (or at all?) the best person for the actual job: design, development, etc. Most of the companies everyone admires today had a completely broken hiring process 10 years ago, and that's exactly what made them successful. They directly hired the designer who had posted 3 shots on Dribbble, they directly hired the developer who had posted 3 lines of code on GitHub. They trusted their instincts, they gave it a shot. That's all. With your complicated hiring process, borrowed from other industry, and your HR teams rebranded as "Talent Acquisition Specialists", you keep looking for designers and developers without ever finding them. Meanwhile, those designers and developers are still waiting for their dream job so they can do their magic and help you succeed. Everything is stuck, and it's your fault. Congrats! 👏

• 
  Dimabytes (@dimabytes) reported 38 minutes ago

  @ImLunaHey ****, we migrated to Github from Bitbucket today. Around 500k LOC. Sorry for slowing it down for you guys :(

• 
  Al McLean (@moridin419) reported 39 minutes ago

  I've started using github issues as the backend for building with AI and it works ridiculously well. PRD for the idea, milestones for direction, issues for work, ADRs for decisions and commits + CI for proof. The project context is easy to rebuild every time.

• 
  Somasundaram (@_somu_) reported 42 minutes ago

  Pipr 0.7 is out! You can now run the same AI code review workflow across GitHub Enterprise, GitLab Self-Managed, Gitea/Codeberg, Azure DevOps Server, and Bitbucket Data Center. Run diagnostics also make failed reviews much easier to debug.

• 
  elliott (@cyburke) reported 45 minutes ago

  @carrabre This is beautiful! Q: When I try to click the GitHub link, for the book part specifically, it gives me a 404 error.

• 
  Habibi Code (@habibicode) reported 48 minutes ago

  Another big round of updates on iamsingle today! Here's the full list: 📜 Certified SFWA badge We load every app and check if its code really sits in one file. Only 10 of the 21 entries pass this test. 🔧 Fixes are suggested The page lists exactly how to fix the app to make it a sfwa, and opens a pre-filled issue on github ✅ You fixed it and made it a sfwa? One click re-measures and credits you as co-author, verified from your commit

• 
  Temiloluwa (@temivalentine_) reported 53 minutes ago

  I spent the last week fighting a native iOS build that would not compile. Wrong deployment target, a duplicate-symbols ghost, and an actual bug in a C++ library used by React Native that I had to root-cause myself from GitHub issues. But it runs now Some weeks are just this.

• 
  wolfie (@wolfie_) reported 53 minutes ago

  @lawrencecchen @Mysterious35725 are you accepting outside contributions? my buddies and i have been testing out the tui and pushed some bug fix PRs - would you prefer if we opened github issues instead?

• 
  Ibro (@axeng200) reported 54 minutes ago

  @cassidoo You should fix the GitHub. It is slow, honestly. Make it snappy. Make it great.

• 
  Dov Quint (@DGQuint) reported 54 minutes ago

  In the L30 days I’ve shipped 13 code contributions into production with as much coding experience as a toaster. I’ve never written a single line of code IN MY LIFE. But AI and our culture at @getoutersignal has completely changed what feels possible. Without Claude, I (or more accurately, my eng team) would have been staring down months of work (chased / nagged by me) before any of these features or requests made it live. Now I (yeah, me) am able to get the ball rolling in minutes. Normally you only see these GitHub charts posted when someone's flexing a screen full of green squares…(one day, maybe). For now, I’m just happy and grateful to be on the board!

• 
  Paul Bennett (@mrpbennett) reported 55 minutes ago

  Am I the only one having GitHub issues? Signed into my account via ssh from multiple computers? But it keeps logging me out!!!!!! Although I use the CLI to sign back in which is annoying by the way! I still can’t seem to push anything!

• 
  Hago Community (@HAGOCommunity) reported 57 minutes ago

  NVIDIA Announces Senior Software Engineer Job Opening in the United States NVIDIA, one of the world’s leading companies in technology and artificial intelligence, has announced a full-time job opportunity at its office in Santa Clara, California, United States. The advertised position is Senior Software Engineer – Topography, and it is intended for experienced professionals in software development, artificial intelligence infrastructure, and cloud-based systems. The position was still open for applications on Monday, July 27, 2026, and its reference number is JR2020161. About the Company NVIDIA is a global leader in graphics processing units, accelerated computing, data centers, artificial intelligence, and machine learning. The company develops technologies and platforms used to run artificial intelligence models, cloud-computing systems, smart vehicles, scientific research applications, and electronic games. Job Title Senior Software Engineer – Topography This is an advanced technical role focused on developing systems and platforms that help operate and distribute artificial intelligence and machine-learning workloads across cloud-computing environments and data centers. Work Location The position is based in: Santa Clara, California, United States. The job is connected to NVIDIA’s Santa Clara office, and the advertisement does not indicate that it is a fully remote position. The working arrangement may be office-based or hybrid, depending on the company’s and the team’s policies. Applicants should confirm the attendance requirements during the interview or recruitment process. Employment Type This is a full-time position suitable for professionals with extensive experience in software development, distributed systems, and cloud infrastructure. Expected Salary The advertised annual salary is approximately: $184,000 to $287,500 per year. The final salary may vary depending on the applicant’s years of experience, technical skills, location, and interview performance. The compensation package may also include bonuses, company stock, and other employment benefits. Job Responsibilities The successful applicant will participate in designing and developing advanced software systems used to operate artificial intelligence and machine-learning infrastructure. The responsibilities include developing solutions that help manage computing resources, improve the distribution of tasks across servers, and handle large workloads within cloud environments and data centers. The engineer will also work on distributed systems that can manage large numbers of machines and computing resources. In addition, the employee will contribute to improving NVIDIA platforms used to run artificial intelligence applications. The engineer is expected to collaborate with software, infrastructure, and cloud-computing teams. Other duties may include designing application programming interfaces, testing systems, reviewing software code, and improving software quality. Required Qualifications NVIDIA is looking for a candidate with strong professional experience in software development and large-scale systems. The main requirements include: At least eight years of professional experience in software development or a related technical field. A bachelor’s degree in computer science, software engineering, computer engineering, or a similar discipline. Strong professional experience may be accepted as an alternative to a university degree. Advanced experience with the Go programming language or another systems-programming language. Strong knowledge of the Linux operating system. Practical experience with Kubernetes and container technologies. Experience in designing and developing distributed systems. A good understanding of application programming interfaces, or APIs. Experience with continuous integration and testing systems, or CI. Knowledge of workload management and computing-scheduling tools such as Slurm or Slinky. The ability to design data models and integrate different systems. Experience with resource-discovery systems, task distribution, and workload management. Required Personal Skills In addition to technical expertise, applicants should be able to solve complex problems, work effectively within a large technical team, and communicate clearly with engineers and product managers. Candidates should also be capable of making sound engineering decisions, writing high-quality software code, reviewing the work of other team members, and contributing to projects that require accuracy, speed, and continuous learning. Who Is Suitable for This Position? This role is suitable for highly experienced engineers, especially those who have previously worked in: Cloud infrastructure. Artificial intelligence and machine learning. Distributed systems. Platform engineering. Kubernetes and container technologies. Data centers. Site reliability engineering. Large-scale computing workload scheduling and management. This position is generally not intended for beginners or recent graduates because it requires extensive experience and advanced technical skills. Documents Needed for the Application Applicants are advised to prepare a professional résumé in English that clearly highlights their experience in software development, distributed systems, Kubernetes, Linux, and cloud computing. The résumé should preferably include clear examples of projects the applicant has worked on, the technologies used, and the size or scale of the systems they developed or managed. Applicants may also include links to their GitHub profile, LinkedIn account, or technical portfolio, when available. How to Apply Applications must be submitted through NVIDIA’s official careers website. After opening the job advertisement, the applicant should click Apply Now, create an account or sign in, provide the required personal and professional information, and upload an English résumé. After the application is submitted, NVIDIA may review the résumé and contact selected candidates for an initial interview with a recruiter. This may be followed by technical interviews and assessments related to programming, system design, and problem-solving. Important Information for Applicants Outside the United States Applicants living outside the United States should carefully review the job advertisement to determine whether NVIDIA provides work-visa sponsorship for this position. A job being located in the United States does not automatically mean that the company will sponsor a visa for every applicant. Visa sponsorship depends on the position, the applicant’s experience, the company’s policies, and current immigration and employment requirements. Applicants should never pay money to anyone claiming that they can guarantee the job or a work visa. Official applications must be submitted through the company’s website, and NVIDIA does not guarantee employment in exchange for payment. Conclusion This position represents a strong opportunity for experienced engineers specializing in software development and artificial intelligence infrastructure. It offers the possibility of working for a global technology company, earning a competitive salary, and contributing to advanced projects in cloud computing, machine learning, and distributed systems. However, the role has demanding requirements. Applicants should carefully confirm that their experience matches the qualifications and prepare a strong, customized résumé before submitting their application.

• 
  • nanou • (@NanouuSymeon) reported 59 minutes ago

  Start with one rule: One task, one tab group For example: 🔹 code documentation 🔹 current GitHub issue 🔹 local application 🔹 API reference