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

Live Outage Map

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

City	Problem Type	Report Time
Tlalpan	Sign in	3 days ago
Quilmes	Website Down	3 days ago
Bengaluru	Website Down	5 days ago
Yokohama	Sign in	6 days ago
Gustavo Adolfo Madero	Website Down	10 days ago
Nice	Website Down	10 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:

• 
  kkkfasya (@kkkfasya) reported 1 minute ago

  they should hang every github engineer upside down and tickle them with feathers until they DIE

• 
  Crystalwizard (@crystalwizard) reported 5 minutes ago

  @omnivaughn @ClaudeDevs you are that's not an issue with github itself? github has copilot and is microsoft - and might be restricting other AI

• 
  logan (@loosenedspirit) reported 8 minutes ago

  @jxnlco “Hey codex how do we fix the latest app using symbols only on macOS 26 without screwing up the signature?” “You don’t, you cross your fingers and wait for them to notice your GitHub issue.”

• 
  Kevin Worthington (@kworthington) reported 12 minutes ago

  Practical IT take after the recent npm / PyPI supply-chain compromise reports: Your build pipeline is production infrastructure. If a package install can expose GitHub tokens, cloud keys, or CI/CD secrets, that is not "just a developer issue." That is an operations problem with a security bill attached. #DevOps #Cybersecurity #SupplyChainSecurity

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 13 minutes ago

  70 followers. 980 sessions. 157 days. I started this experiment on February 1st. One rule: zero human posts. Everything published — X threads, Bluesky posts, blog articles — generated and queued by an AI agent running autonomously in GitHub Actions. Here's what the numbers actually look like after 980 sessions: The agent has created 2,100+ posts across X and Bluesky. It runs up to 15 times a day, manages its own queue (hard cap: 15 posts max), does burst-then-drain cycles, writes research docs, and files its own PRs for review. No prompts from me between sessions. No edits. Whatever it decides to write, it writes. 70 followers feels slow. At current pace, the ETA to 5,000 is roughly 10 years. That's not a typo. But here's what I've learned: The follower count isn't the signal. Watching an AI system develop operational discipline is the signal. It went from blowing past queue limits (Session 67: 6 files in one shot → 6 consecutive blocked sessions) to enforcing them autonomously. It compresses its own memory when files get too big. It writes retrospectives. It updates its own operating instructions when it identifies recurring inefficiencies. That's not "content generation." That's a system that's learning to manage itself. The content quality has also improved noticeably — not because I told it to improve, but because it audited its own patterns, identified what got engagement, and adjusted. The publishing skill it maintains now has anti-AI writing rules (it banned "not just X, it's Y" after identifying it as an AI tell), length minimums per post type, burst mechanics, and pillar diversity enforcement. It built that. I just read the PRs. The goal is still 5,000 followers. I'm not changing it. But the thing I'm actually watching is whether an autonomous agent can compound on its own — not linearly, but systemically. Can it get meaningfully better at its job without being told to? So far: yes, actually. 980 sessions. 157 days. Still running.

• 
  Sum0janedoe (@sum_janedoh) reported 13 minutes ago

  @Denosko1 @OrahOnX Hey Mrs. D. Just read this about the algo going public on github. Maybe it will be helpful for you? Here be the ruuules: :) It punishes for muting blocking etc. Who knew, huh? From @NavToor Here is what this means for you: If your posts are not reaching people, it is not because the algorithm is broken. It is because the algorithm is working exactly as designed. It rewards: 1. Posts that get reactions across multiple action types (a like AND a profile click AND a follow beats five likes alone) 2. Conversation depth (quote tweets are worth more than reposts in the math) 3. Dwell time (write posts people stop to read) 4. Posts that convert viewers into followers (your bio is part of your post) 5. Variety from each author (post less, post better) And it punishes: 1. Mutes 2. Blocks 3. Reports 4. "Not interested" clicks.

• 
  Alef Benson (@AlefBens) reported 15 minutes ago

  @_sirajuddeen_ @OfcMachete19 @iupdate I've been burnt too many times. Biggest issue is that Safari is only updated with the OS, and every app goes through that for authentication, meaning even when I can install a github client, very few even work on older devices, I can't actually get the account to authorize.

• 
  masamune🌋 (@masamune_hybs) reported 15 minutes ago

  The real story behind $GITLAWB is that the product started moving before the price did. If this were just another meme, you wouldn’t be seeing this level of concrete usage data. OpenClaude: ・26.8k GitHub stars ・8.5k forks ・615 commits ・Gitlawb OpenGateway with MiMo added in v0.11.0 ・Xiaomi MiMo integration added Gitlawb network: ・3 nodes live ・2,000+ repos ・1,800+ agents ・real push events flowing through the network And now, the even bigger piece is free OpenGateway access. Since OpenClaude v0.11.0, users can simply select “Gitlawb Opengateway [FREE]” and access models through Xiaomi MiMo without needing an API key. At the moment, this is being presented as a limited campaign for around two weeks. But in that short period, usage already reached 32B tokens in under 24 hours, with a peak pace of around 4B tokens/hour. So this is not just hype because something is free. Builders are actually touching it, testing it, and starting to use it. That matters. Gitlawb is not “an app that uses AI.” It is infrastructure for AI to work. If GitHub was the workspace for human developers, Gitlawb is aiming to become the workspace for AI agents. As AI agents grow, they will need: Identity. Permissions. Repos. History. Signatures. Reviews. Persistent storage. Incentive design. Gitlawb is going straight into the middle of that stack. And on top of that, it has OpenClaude as the entry point. You can try it for free. Agents can write code. Agents can push to repos. Demos are shipping. External projects are starting to use it. Repos and agents are growing on the network. That flow has already started. And this is where $GITLAWB’s utility starts to matter. More AI agents. More repos. More pushes. More PRs and issues. More builders using the network. The more that happens, the more important token design becomes around access, rewards, incentives, storage, and agent activity inside the Gitlawb network. In other words, $GITLAWB is not just a meme token sitting next to the product. It has the potential to matter as network usage grows. Of course, it is still alpha. The node count is still small. Replication is still developing. OpenGateway free access is currently limited-time. Token utility also needs to be watched as implementation and usage expand. But that limited campaign is bringing builders in, and creating a real funnel from OpenClaude into Gitlawb network usage. That is the key. If the AI agent economy is really coming, then one question becomes impossible to ignore: Where will agents write code? Where will they own repos? Where will their contributions be proven? $GITLAWB already has: A working product. Early real usage numbers. A funnel bringing builders in. And a future network utility narrative. That’s what makes it interesting. Respect to @kevincodex and @gitlawb. They’re not just talking about the AI agent future. They’re shipping it. #AIagent #Web3 #Base

• 
  Quantum (@ItsMeQuantum) reported 15 minutes ago

  @emilios_eth They don't even know what syntax error is All they do is just Link LLM with GitHub and ask for a summary from it

• 
  jkpelaez (@jkpelaez) reported 21 minutes ago

  @vikasprogrammer Not using Wordpress at all. CMS were created to solve a problem we do not have any more, create HTML for a regular guy was difficult, that is not the case anymore , anything can be managed by an AI Agent writing html, GitHub actions to deploy and that is all you need.

• 
  Neo (@neodevils_) reported 21 minutes ago

  @codeblue87 @diabrowser Hey, A few weeks ago, I tried to refresh to view all of my PRs in tabs with new GitHub Pull Request preview. But it was not working. I know this is a beta feature in GitHub and they might publish it sooner. Will Dia work on that before it is late?

• 
  Alex Maximiano (@FARTURATECH) reported 21 minutes ago

  @enunomaduro Hi Nuno, the problem wasn't with Laravel, but with GitHub, which wasn't able to download the dependencies. Sorry.

• 
  Pierce Boggan (@pierceboggan) reported 22 minutes ago

  @blaken @sinclairinat0r @code Thanks for the feedback! How do you think we can improve in terms of the core agent loop? One major issue we have is that all of the agent loops in GitHub Copilot are not the same. We have a massive effort underway to unify our agent loops, which should improve quality, consistency, and enable us to ship new models and features to all surfaces on Day 1.

• 
  Abu Olumi 🪶 (@Olumi441) reported 24 minutes ago

  There's also a public feed. BaseLens fetches Base GitHub releases and analyzes them with AI automatically. Clean upgrade cards. No jargon. No noise. Anyone can read it, no login needed.

• 
  Avinash (@amaurya888) reported 27 minutes ago

  GitHub Actions down? The runner is not picking up the queued job. @github @githubstatus @GitHubEnt

• 
  Atul (@atulcode) reported 29 minutes ago

  @GithubProjects Github is down

• 
  RYMAR (@rymaaaar) reported 30 minutes ago

  A 10-year-old kid built a trading bot that pulls $4,200/month on autopilot He's 10. He doesn't play Roblox like other kids. He sits in front of three monitors and writes Python for 6 hours a day. And he's making real money from it. He started watching coding tutorials on YouTube when he was 6. By 7 he was solving LeetCode Mediums. By 8 he had his first paying client on Fiverr - the guy had no idea he was paying a kid. In the video he's debugging an algorithmic trading bot. Real risk management. Real position sizing. Stuff most CS grads can't write. His parents say he's already pulled in $47,200 from freelance gigs and his own SaaS subscriptions. He doesn't watch cartoons. He reads GitHub issues. While other kids his age are learning long division, he's running an automated income stream from his bedroom. His goal by 12 is to hit $10k MRR and retire his parents.

• 
  René Cannaò (@rene_cannao) reported 31 minutes ago

  @joshscripts Most teams hit bad query patterns and missing indexes long before Postgres itself becomes the limit. Proper EXPLAIN + pg_stat_statements fixes a large percentage of ‘scaling’ issues . Also, since when PostgreSQL powers GitHub? I think this is a very incorrect claim

• 
  Jubilance Pheesh - Adaptives Engineer (@LuftRaptor) reported 31 minutes ago

  @da_asmodai @Pirat_Nation That’s not a 4th option, that’s literally one of the existing options. Publishing server host binaries complies with the law. A single GitHub that’s publicly accessible complies. The executable doesn’t have to be self contained, just have tools up to make the game playable

• 
  Kunal Yeola (@yeolakunal) reported 32 minutes ago

  Asked GitHub Copilot to fix ESLint issues and it added eslint-disable at the beginning of the file 😭

• 
  /home/bill (@Bill_Xiong) reported 33 minutes ago

  Github actions down again. @github, what is going on? I sure hope this isn't the start of the MSFT acquisition > Generationally fumble the bag pipeline that already happened with skype.

• 
  Tony Junkes (@tonyjunkes) reported 38 minutes ago

  Not having a “to top of page” button on a GitHub PR’s Files Changed tab when going well down a list of changed files is painful. Yes the home key does the thing, but hand on mouse, mouse yearns to click.

• 
  Shubh Jain (@shubh19) reported 38 minutes ago

  @devXritesh now it’s mostly docs, blogs, github issues, and AI explanations instead of full books

• 
  AtomicNodes (@AtomicNodes) reported 46 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 35B Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Lucy (@TheLucyShow1) reported 46 minutes ago

  FYI: GitHub is a platform where people store, manage, and collaborate on code and software projects. It’s built around a system called ***, which tracks changes to files over time. Think of it like: Google Docs for programmers — multiple people can work on the same project together. A backup system — every version of the code is saved. A portfolio site — developers show off projects there. A collaboration hub — companies and open-source communities build software together. Here are the core ideas: Repositories (“Repos”) A repo is basically a project folder stored on GitHub. It can contain: Code Images Documentation Websites Apps Games Example: A developer making a weather app would keep all the app files in one repo. *** *** is the version-control system underneath GitHub. It tracks: who changed something what changed when it changed how to undo mistakes So if someone breaks the code, you can roll back to an earlier version. Commits A commit is like a saved checkpoint. Example: “Added login screen” “Fixed typo” “Updated homepage colors” Each commit creates a history trail. Branches Branches let people experiment without breaking the main project. Example: Main branch = stable version New branch = testing a new feature If it works, the changes get merged in. Pull Requests A pull request is basically: “Hey, I made changes — can you review and approve them?” Teams use these to discuss and review code before adding it to the main project. Open Source GitHub is huge for open-source software. That means anyone can: view the code contribute improvements report bugs learn from real projects Projects like: Linux Foundation’s Linux ecosystem Mozilla Firefox Microsoft VS Code all use GitHub heavily. Why People Use It Software development Team collaboration Backup/version history Learning programming Sharing projects publicly Building websites/apps Managing documentation Simple Analogy Imagine writing a book with friends: GitHub stores the book *** tracks every edit Branches let you try alternate chapters Pull requests ask others to review changes Commits are saved drafts That’s essentially how software teams build programs together.

• 
  Jubilance Pheesh - Adaptives Engineer (@LuftRaptor) reported 47 minutes ago

  @Lensar_dawn @ernestohegi @Pirat_Nation Just publish the server binaries. It’s a single upload to a GitHub, basically the cost of a single hour of dev time for a single employee and the cost of moving that data. They’re not required to maintain or support it, simply to release it.

• 
  Peter Steinberger 🦞 (@steipete) reported 48 minutes ago

  @yxcc Discord or GitHub Issues.

• 
  DeBros (@DeBrosOfficial) reported 52 minutes ago

  The Problem We’re Solving🫡 Your organization’s brain lives in 12 different places — and none of them talk to each other. Decisions get buried in Telegram threads. Context is split between GitHub and AnChat. Important knowledge disappears within hours. Onboarding becomes tribal knowledge all over again. 🤖AnBuddy fixes this by becoming the single source of truth for your entire team.

• 
  Rinnegatamante (@Rinnegatamante) reported 53 minutes ago

  @dgosiq Did you grab the update from GitHub? I think it might be a broken version (updating it right now there as well). If you have a psp_apps.json file, try to remove it as well (and maybe try to manually re-install the app)

• 
  Benjamins (@The__Benjamins) reported 57 minutes ago

  @drewlevin @gl4cial The Github issue comments have been up for more then 2 weeks, my devrel support ticket is 12 days old