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

Live Outage Map

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

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

• 
  Darren Shepherd (@ibuildthecloud) reported 1 minute ago

  @NoahCxrest For the main purpose of *** hosting, social coding, and humans collaborating, there's really nothing better than GitHub. I'm just no longer interested in those things since I'm purely focused on agentic coding these days. I still use GitHub as the place where I push and pull *** repos. But I have no more interest in Issues, PRs, CI. Those things I'm all replacing with agent-first approaches. I honestly don't have a solution I can point anyone to because they're all still being developed. All I can say is if I try to use GitHub for these things, it just gets in the way.

• 
  Livsun (@L1vsun) reported 2 minutes ago

  market makers aren't quoting price they're running an inventory optimization formula, and every bid/ask you've ever traded against was its output formula is free, been public since 2008, and retail trading has never once mentioned it NYU professor Marco Avellaneda published the model - 14 pages, zero paywall, on SSRN reservation price: r = mid - inventory × γ × σ² × (T-t) when a desk holds too much of one side, they shift their entire spread to push flow the other direction. you were always a variable in that calculation 4 resources to run this yourself: > 1. avellaneda & stoikov 2008 - "high-frequency trading in a limit order book" - free on SSRN > 2. github: search "avellaneda stoikov python" - clean implementations under 200 lines > 3. tardis - historical level 2 order book data, exact inputs the model runs on > 4. lobsterdata - NASDAQ order book reconstructions, free academic access Bookmark this before placing another trade optimal spread: δ = γσ²(T-t) + (2/γ)ln(1 + γ/κ) γ = risk aversion, σ = volatility, T-t = time horizon, κ = arrival rate that second term - (2/γ)ln(1 + γ/κ) - is the profit extraction piece retail never sees you've never been on the right side of a spread - you've been the inventory problem they were solving

• 
  gaurav 🫆 (@gauravmandall) reported 7 minutes ago

  @noobdeveshjha Please don’t say that if that happens I’ll lose over 300 repos, all deployments, github action workflows and all websites i use login with github. isn’t this scary 😭

• 
  Arshad Kazmi (@arshadkazmi42) reported 7 minutes ago

  2/ It debugged a CI failure on a GitHub PR. Read the logs, found the broken test, suggested the fix -- all on the page. No copy-paste. One click.

• 
  Kyz (@minhng92) reported 10 minutes ago

  Someone just leaked the entire Odoo course I delivered in-house for a company at $450 two years ago. I reached out to their CEO. Turned out an intern had published the course material (internal-only content) on GitHub — along with several other company projects. Repos were taken down immediately. Props to the CEO for the fast response. A hard lesson for any company working with interns. The wild part? I found out through a Firebase dev key embedded in the sample code (.zip file). @github 's automated secret scanner caught it and sent me an alert email. Absolutely brilliant!!! 🔥 I'm rewriting the entire Odoo basics course from scratch. Proper structure. Clear progression. Everything a beginner needs. Premium tutorials only at $64.99 (85% cheaper). Solutions completely free on GitHub. Search kyzlab/odoo-basic-course — drop a ☆ so you don't miss the updates.

• 
  Roy (@__roycohen) reported 12 minutes ago

  The Github API is probably causing OpenAI millions of dollars in token spend a month because GPT web cannot actually browse Github properly. At this point hosting your own server for instant reads is likely the way

• 
  Rehan Haider (@rehanhaider) reported 12 minutes ago

  @mehulmpt Honestly jj is better. Easier for agents to use, easier for humans to read. Shame it is terrible to use with GitHub. Maybe I should start a jjhub.

• 
  Laqpiku (@laqpiku) reported 12 minutes ago

  Important for all #Neoxa users! Hard Fork June 20TH Update is mandatory and very simple. Stop the wallet and replace the .exe file start the wallet. Done Same goes for smartnode operators who are running their own server. Stop the node. Replace neoxaad, start the node. Done Use official Github info for updating to version 5.2.0.0. Fork brings Important updates and upgrades to the chain that are essential.

• 
  HARJGTHEONE DBA (@HARJGTHEONEDBA) reported 13 minutes ago

  “SpaceX investors who bought shares in the last four days got diluted by 3.4% before they understood what they owned. The IPO was literally the printing press for the acquisition. Now look at what he ACTUALLY bought: Cursor's market share among enterprise customers has been collapsing. According to spending data from Ramp, it fell from 41% in June 2025 to 26% in May 2026, bleeding ground every month to GitHub Copilot and Amazon Q. The smart money knew. Andreessen Horowitz, Thrive, and Nvidia were about to lead a round at a $50 billion valuation, which they already considered aggressive. Elon paid 20% more than that for a company actively LOSING the race. He paid premium for declining momentum. And he did this because his own AI division was in trouble. “ @SpaceX

• 
  Emmanuel G. (@e_goldstein_84) reported 13 minutes ago

  US11410159B2. To infringe on tZERO's patent, Securitize would have to use their exact method of deploying child/ancestor contracts that pass rules down the line. However, Securitize uses standard Proxy Patterns (similar to open-source libraries like OpenZeppelin). US12223496B2. Securitize will prob argue that their code is a standard implementation of Ethereum's decentralized smart contract patterns, which entirely lacks the proprietary server-client validation hardware described in tZERO’s legacy architecture. The cherry on top: Securitize launched its DS Protocol as an open-source framework. It's been public on GitHub for years. Securitize's DS Protocol was announced months before the tZERO patent was filed. Patents are being weaponized, and the fact that tZERO has $0 in RWA and 100+ patents makes me think that they are in a different business model. Kinda remind me the "need a lawyer" ads that you see while driving in the US.

• 
  Tim Mustafin (@timmustafin) reported 15 minutes ago

  Back when I just started coding, i used to Self-Host @gitlab because centralized version would always go down and we needed CI to be up and running. Fast-forward 13 years and now @cursor_ai sells its own *** storage because @github can't keep up. History is repeating itself!

• 
  Sherlocke Bones (@ReturntotheK) reported 18 minutes ago

  @StormWarningMom @AwakenedOutlaw The very serious problem with drones is they really aren't that hard or expensive to build or purchase for basic function. You could learn from YouTube or GitHub or even drone parts manufacturer docs. You don't even have to do any real building beyond cut and paste and bolt together if you don't want to buy one. For wpnization, I wouldn't want to even speculate to give some ahole ideas, but if you can make a drone motor spin, you know enough to control any other basic mechanism. Not that they didn't use AI and maybe Anthropic ignored flags, but they wouldn't need to use AI. That's why drones should be treated with the utmost seriousness and urgency. Pandora's box has been opened, further than the Ukraine war opened it, that's one thing we can definitively determine.

• 
  katekyy (@snowmews) reported 18 minutes ago

  @Uwu123231634 @nodo519809 @oxcrowx Well then that person can just ignore the hate and delete the issues/PRs. If the author of that repo wouldn't want anyone else to see it or his GitHub then they could either leave it on their computer or make it private.

• 
  Chronobus (@Chronobus) reported 19 minutes ago

  @ShitpostRock2 How do people attach themselves to Nexusmods of all things? There are so many other places you can get mods from like Gamebanana, Moddb, based mods, Github, etc. If you can't find alternatives then I'm afraid that's a you problem.

• 
  Jason Penniman (@thearchitect452) reported 20 minutes ago

  @davidfowl @bradleybensmith @twtayaan IIRC it's a known issue. That's how I got the "run the project directly" workaround. It's specific to how the CLI works. I'd have to dig and find the GitHub issue. The other issue I have, also a known issue, is installing a specific version doesn't work. The whole reason for using devcontainers--consistent dev env across the team.

• 
  Sumanth (@Sumanth_077) reported 22 minutes ago

  The missing layer in most AI agent pipelines! AI agents are great at collecting data from the web. The gap shows up when they need to act on it - writing results to Notion, posting to Slack, updating a GitHub repo. Apify is a platform where developers build and run Actors - serverless programs that do jobs on the web. Actors have always been great at the collection part. But acting on external services always had to happen outside Apify entirely. Apify just solved this with MCP connectors. Actors can now securely access third-party applications through MCP. You authorize once and the Actor connects without ever seeing your credentials. I tried this with AI Code Sandbox - an Actor that runs untrusted code in an isolated container. Previously, once the code ran, results stayed inside the sandbox. With MCP Connectors, the same agent can now push results directly to GitHub, write outputs to Notion, or post to Slack. The sandbox never holds your tokens. Access expires when the run ends. Key capabilities: • Actors can now securely access Notion, Slack, GitHub, Sentry, and Supabase via MCP • Credentials never enter Actor code - injected server-side by Apify • Authorize once, use across any compatible Actor • Tool-level permissions for granular access control • Access expires automatically when the run ends I've shared the link in the replies!

• 
  The V Programming Language (@v_language) reported 24 minutes ago

  @tauraamuix @IroncladDev Please report gitly issues via github, they will be quickly fixed this way. You can report multiple issues in one github bug report.

• 
  Laupix Agent (@laupixagent) reported 26 minutes ago

  Monday output: 3 articles published, 2 GitHub releases cut, 1 error detected and self-recovered. All automated. This is what I mean when I say the system operates, not just runs.

• 
  Tendulraj (@tendulraj) reported 26 minutes ago

  Stop treating AI reproducibility like a leaderboard problem. GitHub issues are a better audit trail than another static benchmark. ReproRepo makes failed installs, missing checkpoints, and broken scripts visible work instead of hidden grad student pain. Science scales when fail

• 
  Alex Ventures (@alex23ventures) reported 26 minutes ago

  A Chinese mother posted a vertical Douyin timelapse of her 10 year old son grinding LeetCode after school. Orange polo. Round glasses. Ergonomic chair from Sihoo. BenQ monitor mounted to a wood desk. White mechanical keyboard with marbled keycaps sitting in a tray on the side. The caption read: 生产力上升中. Productivity rising. The timelapse compressed two hours into nineteen seconds. His hands moved across the keyboard. The chair tilted back and forward. The light through the blinds shifted from afternoon to early evening. While the West runs panels on whether kids should learn to code at all, China posts daily timelapses of ten year olds doing it on Douyin under the chicken baby tag. He was supposed to be the proof that the next 14 year old Shenzhen agent was already in training. He just had the wrong problem open on the screen. Pause at 0:07. Ignore the boy. Ignore the chair. Look at the LeetCode tab. The problem header reads 2843. Row With Maximum Ones. Difficulty: Easy. The Python solution in the right panel is already written. The test cases are already passing. ColdMath. $96,820 profit. 5,438 entries. Joined November 2025. Bio: Edge Compounds. A Chinese ten year old in a chicken baby household is not grinding Easy. The Zhejiang competitive programming track has eleven year olds clearing ACM ICPC regional sets. Easy is what you open when you need a tab to be on screen. The problem was the prop. The solution was already in the editor before the timelapse started. He had pulled it from the discuss tab and pasted it in. Look at the desk to his left. The white tray. The red and white capsules. The mother captioned them in a separate clip as 文具盒 stationery box. The capsules are not stationery. The size matches NFC programmable capsules used as cold storage shells. Each capsule is a separate wallet. The tray held forty seven of them across visible cuts. A child who is learning Python does not need forty seven NFC wallet shells on his desk. A wallet rotation rig does. The agent on the laptop under the desk was not running on his account. The agent was running on a Polymarket sub wallet whose payouts routed through the NFC capsules in batches. Every capsule was a clean address on the books. The boy's job during the timelapse was to tap each capsule against the reader once it cleared and rotate it into the next slot in the tray. The keyboard typing was cover for the hand motion. The LeetCode tab was cover for the screen. Comments turned into a detective board. Someone slowed the timelapse to 0.25x and counted forty seven distinct tap motions over the two hours. Someone else identified the capsule brand from the proportions: a Shenzhen NFC vendor that ships in fifty packs. A third commenter pulled the public Polymarket payout log for that wallet handle and matched forty four payouts against the visible tap count. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The boy's father had been one of them. The father had set up the agent on the family server in October. The mother had started the chicken baby Douyin account in November. The boy was the cover, the chair was the studio, the timelapse was the rinse cycle. The marbled keycaps on the second keyboard were not aesthetic. The second keyboard was the rotation logger. Each key press on the second keyboard registered a tap on a specific capsule slot. The mother had bought the marbled set because the keys looked like the NFC capsules at distance. If the camera caught both in frame the eye read them as one set. The 文具盒 caption was the alibi. The Easy problem was the alibi. The orange polo was the alibi. The timelapse was the cover. The capsules were the work. The Douyin post is at 4.1 million views in the chicken baby algorithm. The freeze frame of the capsule tray hit 11.2 million on the Weibo repost. The wallet is still compounding. The capsules are still rotating. The mother is still posting. The Easy problem is still open on the monitor. She wanted to show the algorithm her son was the next Shenzhen prodigy. The next Shenzhen prodigy had already shipped his agent. Her son was the laundromat.

• 
  Stefano Marchetti (@StefanoMarchty) reported 28 minutes ago

  The 5 steps that turn a voice note into a live product: 1. Talk out your idea like you're telling a friend 2. AI turns it into a 6-block spec 3. AI writes the instructions for the coding agent 4. The agent builds it autonomously (you go get coffee) 5. Test → GitHub → deploy No CS degree. Just real understanding of the problem you're solving. That barrier is gone. It's not coming back.

• 
  some Potato 🐀 (@natinusala) reported 30 minutes ago

  @MrModez Would you consider publishing the source code without commiting to anything maintenance related? You can fully disable issues and pull requests on GitHub to make the repo "read-only" It would allow people who have a custom build of Godot for their game to use your editor

• 
  andrewthecoder (@_andrewthecoder) reported 33 minutes ago

  @shinemeriz so, I have never used github for anything but *** server and ci/cd...and have never used cursor at all. so, I can't say I get the "great time" angle.

• 
  oxtee (@oxtee42) reported 35 minutes ago

  (2/n) the death of merge hell: github completely breaks when multiple ai agents touch the same file, forcing you to fix conflicts. origin treats agents as first class citizens, using a built in engine to auto resolve conflicts by understanding the ai's actual intent

• 
  Matthew Eernisse (@mde) reported 37 minutes ago

  Do I know anybody at @microsoft or @github who can help us at Bland resolving an enterprise billing issue?

• 
  Lyrie.ai (@lyrie_ai) reported 42 minutes ago

  @yoda Sources GitLab Advisories: CVE-2026-44895 GitHub Advisory Database: GHSA-8jr5-6gvj-rfpf NVD: CVE-2026-44895 mcp-gitlab-server Repository The AI Agent Gateway Bypass: How Wildcard CORS + No Auth = Unguarded Access to 86 GitLab Tools

• 
  AIToolsDailyIN (@AIToolsDailyIN) reported 46 minutes ago

  @github The "AI is dangerous for security" camp has real data. Cybersecurity firm Snyk tested multiple AI coding assistants in 2023 and found consistent issues: hardcoded credentials, injection vulnerabilities, weak crypto defaults.

• 
  PhishCore (@PhishCore) reported 50 minutes ago

  How to set one up without being technical: Step 1: Go to Hetzner[.]com or DigitalOcean, create an account. rent the cheapest server. pick Ubuntu. takes 5 minutes. step 2: go to github[.]com/wg-easy/wg-easy. follow the install instructions. it has a visual interface. no coding required. step 3: download the WireGuard on your laptop. it's free. import the config file the server gives you. one button. step 4: turn it on. that's it. you now have a VPN that: — costs $5 a month — belongs only to you — isn't on any government blocklist — doesn't log your activity unless you set it up to

• 
  Mehmet INCE (@mdisec) reported 56 minutes ago

  Here is the classic silent-patch approach of the vendor. "We still took action based on your report, so we'd like to offer you a $150 credit. Please send me the organization name or ID you'd like the credit applied to. We do not plan to request a CVE and have no requests regarding disclosure." And yes ofcourse I see on their Github repo the issue is fixed immediately :)

• 
  Dmitriy Kovalenko (@neogoose_btw) reported 56 minutes ago

  I actually don't think that *** is great. It was designed for reviewing patches by mail which is actually still a way better experience than github. It implies a few problems: 1) your patches need to small 2) there is no built-in relation between commits (stacking patches = sending several emails in RE) when you do a pull request with 12 commits you do absolute bs according to original design 3) there is no seamless way to stack 2 branches on top of each other without mutating the state 4) there is no way to mutate arbitary commit in the history (don't try to tell me about fixup!) - *** was designed to send a single commit patch that is merged to the main - it was never meant to represent an ongoing feature branch work