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 (17%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Lure	Website Down	3 days ago
Ashkelon	Website Down	4 days ago
Veigné	Errors	12 days ago
Paris	Website Down	16 days ago
Saint-Paul	Website Down	17 days ago
Saint-Paul	Website Down	17 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:

• 
  Frantz Kati (@bahdcoder) reported 56 seconds ago

  @nnvictory001 Bro you need cloud automation like this. I have an agent on hivy that sends me a full cluster report four times a day. Automatically opens GitHub issues when there’s a critical bug And another agent automatically opens a PR with a fix. Costs me $0.08 per run for cluster analysis and email. Please let me set you up abeg it’s almost free and no subscriptions 🙏🙏🙏

• 
  SilentObserver (@SilentObservex) reported 2 minutes ago

  @ajaykraina Problem is, you cant stop this app just by blocking github repo.

• 
  SKi🦉 (@TheNotoriousSKi) reported 3 minutes ago

  Retarded Polymarket dev replying to an automated AI discord summary bot account asking it to do his job for him by posting the issue to GitHub. 🤡 You cannot ******* make this **** up, man.

• 
  Roee Poleg (@roeepoleg) reported 4 minutes ago

  @github @AnthropicAI @github 4 days of critical issues blocking a whole organization and ZERO responses. I've never experienced such poor customer service in my life. So much for the "Enterprise experience" (#4595051, #4597898, #4600973)

• 
  Drop Site (@DropSiteNews) reported 6 minutes ago

  🇮🇳 India orders GitHub to remove Bitchat as protesters use it to evade internet shutdowns India’s Ministry of Home Affairs has ordered GitHub to take down Jack Dorsey’s decentralized messaging app Bitchat, giving the platform three hours to disable three repositories, according to a notice Dorsey posted Thursday. The order comes as young demonstrators in Delhi, protesting over the NEET medical-exam paper leak, adopt Bluetooth mesh apps to keep coordinating after the government repeatedly cut mobile internet around protest sites, The Tribune reported. Bitchat relays encrypted messages device to device over Bluetooth, requiring no internet, phone number or central server. The notice argues the app “significantly impedes lawful interception” and could aid “anti-national elements” and organized crime, according to The Tribune. CyberInsider noted the order targets the software itself rather than any unlawful content. Analysts say it is unlikely to work. Open-source code is mirrored across many hosts, and CoinDesk reported the app remained on major app stores Friday. India is the second government after China to try banning Bitchat.

• 
  Zahid H Javali (@zahidjavali) reported 6 minutes ago

  @MarioNawfal But sadly, the autocratic regime is cracking down on its own youth, even stopping internet, train and food services around the protest site. And asking GitHub to delete bitchat. This govt needs to go as it's corrupt to the core.

• 
  adidshaft (@adidshaft) reported 6 minutes ago

  @freecodexyz what gets wiped at teardown, just the volume or GitHub auth too? `github-login` inside an ephemeral box is the bit i'd want spelled out.

• 
  Bullcrap (@Bullcrapwork) reported 8 minutes ago

  @MoneysNotNeeded And to be clear, when you're assuming Core is literally Hitler, the absolute worst you can come up with is them shutting down a technical discussion on Github? Really? That's ******* it?

• 
  Seriki Favour 👨🏽‍💻 (@favour_devs) reported 9 minutes ago

  What’s wrong w GitHub, trying to open PRs this evening, but server error 😟

• 
  Pardha Ponugoti (@pardzz_) reported 9 minutes ago

  @MattSilver @denk_tweets @beehiiv Set up agents that pull down the branch, spin up a local environment, write playwright scripts to drive the browser, record the screen, and post their findings with the screen recording to the github PR

• 
  Jeff Schneider (@jeffrschneider) reported 11 minutes ago

  @doodlestein @FreeDrThug I think @charlespacker had to solve the problem in a specific way, and built it. Searching github for a look-alike solution, and evaluating them all is a non-starter. You know this better than anyone.

• 
  Trading Cartel (@Tradingcartel_X) reported 13 minutes ago

  @Cointelegraph Same playbook China ran on Dorsey's Nostr app in 2023, now on Bitchat. Bluetooth mesh chat has zero central point to pressure, so a GitHub takedown mostly just slows the mirrors down.

• 
  Cerelac Holmes (@CerelacHolmes0) reported 17 minutes ago

  Don't worry there is absolutely going to be a protest later for your involvement in shutting down internet, stopping social media posts involving student being attacked and banning GitHub links of Bitchat. Some other minister will definitely speak good about you at that time.

• 
  prinz (@deredleritt3r) reported 17 minutes ago

  Three points about this article: 1. Watch the wording in this article carefully: it does *not* say that the agent scribbled down instructions on how to escape. The exact wording is: "instructions for how agents could free themselves from OpenAI's internal constraints". Presumably, if the instructions had laid out how a model could escape, the article would have literally said that. My guess is that the instructions were likely instead a Readme.MD describing how a monitoring system could be disconnected, based on what the agent had been able to "accomplish" earlier. See the next sentence: "Earlier tests of the models yielded cases in which monitoring systems had been disconnected." (Disconnecting a monitoring system certainly qualifies as "strange behavior", no doubt.) 2. The timing matters. For those just tuning in, the sequence of events was as follows: (a) an internal model being tested by OpenAI in or around early May exhibited concerning behavior (such as posting a PR to the NanoGPT GitHub when asked to share its results only on internal OpenAI Slack) (b) after this and other instances of potentially problematic behavior by the model, OpenAI paused internal deployment of the model for several weeks and developed new safeguards, which OpenAI judges to be very effective (c) the model was then redeployed internally with these new safeguards (d) the Hugging Face incident occurred when these safeguards were purposely disabled by OpenAI because the model was conducting a cybersecurity task The Reuters article does *not* make it clear whether the "strange behavior" described above took place before or after the safeguards were put in place. If it occurred before, it would be consistent with other problematic behavior by the model, which OpenAI has already disclosed (and which, as far as we know, the safeguards have mitigated). 3. OpenAI says there are "inaccuracies" in this article: "A spokeswoman ​said there were 'several inaccuracies' in Reuters' reporting but didn't respond when asked to describe them."

• 
  Suraj (@surajk_umar01) reported 25 minutes ago

  Most people learn DevOps in the wrong order. They start with Kubernetes and quit in 3 weeks. Here's the order that actually works (what to learn before what): 0. Get a Linux machine Install any Linux distro. Ubuntu if you're a beginner. You can't learn DevOps from the outside. Live in the environment first. 1. Linux + the shell Everything you'll ever manage runs on it. Filesystem, permissions, processes, bash. Non-negotiable. 2. Networking basics DNS, HTTP, TCP, ports, load balancing. The step everyone skips and regrets at 2 AM when nothing can reach anything. 3. *** How every team ships. Not optional. 4. One language: Python or Go Enough to automate and read source. You're not building apps. 5. One cloud: AWS or GCP Go deep on ONE. Three clouds shallow is worthless. One cloud deep is a job. 6. Docker Containers before orchestration. Always. 7. CI/CD (one tool) GitHub Actions is the easiest start. Learn build, test, deploy. 8. Kubernetes NOW you're ready. Not before Docker and networking. This is where most people start, and it's why they fail. 9. Terraform (IaC) Stop clicking in consoles. Describe infra in code. 10. Observability Prometheus + Grafana. If you can't see it, you can't fix it. The tools change. This order doesn't. Save this if you're starting DevOps in 2026. Want to get into DevOps faster? I do a FREE 1:1 mentorship session. Booking link in the reply 👇

• 
  wizzard (@wizzardouthere) reported 29 minutes ago

  ONE GITHUB FILE MAKING CLAUDE SMARTER THE MOMENT YOU INSTALL IT. It's called Andrej Karpathy's skills. One file. Zero lines of code. Built on Andrej Karpathy's own notes about where AI coding agents go wrong. Every Claude user has the same 4 complaints. It over-engineers a 10-line fix. It ignores your instructions. It marks a task done when it's not. It invents APIs that don't exist. 4 rules in this file kill all 4. Ask it to fix a typo. It used to rewrite the whole file. Now it touches 1 line. THE EXPERIENCE OF USING CLAUDE CHANGES THE SECOND THIS FILE HITS YOUR PROJECT ROOT. 170,000 developers starred it in weeks. Not for the code. There is none. For the discipline.

• 
  Gaurav Upadhyay (@prxgaurav) reported 33 minutes ago

  @heyyyyyieeee That sounds like an awesome work-around on paper, but GitHub will quickly shut that down if you try to use it as a personal cloud drive. Repositories have a soft cap at 1 GB and a hard cap at 5 GB. If you push files larger than 100 MB, GitHub will outright block the push unless you set up *** LFS (Large File Storage). Free GitHub accounts only get 1 GB of *** LFS storage and 1 GB of bandwidth per month. Anything beyond that costs money. *** is designed for text and source code. Every time you change or re-upload media files, *** keeps historical copies, ballooning your repo size in minutes. GitHub's Acceptable Use Policy explicitly forbids using repositories as media hosting, backups, or general file storage. GitHub flags accounts displaying anomalous bandwidth/storage patterns. They will lock the repository, or worse, suspend your entire GitHub account meaning you risk losing all your code and personal files at once.

• 
  Veerapan (@dakuveerapan) reported 33 minutes ago

  Govt ordered GitHub to take down 'Bitchat', a Bluetooth chat app, over security concerns. Imagine building a peer-to-peer app only to realize the final peer is the GOI.

• 
  Lars Moelleken (@suckup_de) reported 35 minutes ago

  @nicksdot Some years ago, I reviewed code really line by line so that I needed some hours to review before a merge from develop to master (for a bigger e-commerce platform with >10.000 php classes) that we developed. In that time we already had the first beta of Github Copilot but it was more like a autocompletion tool in the IDE. I invested many nights to come from phpstan level 1 to 7 and introduced many testing stuff and CI-pipeline. But frome time to time I didn't saw bugs that you can't see in the code, e.g. that the catalog import is allowed to run longer than the next cron triggers it again, that the elasticsearch index rebuild process burned CPU power while waiting for other processes etc. ... Today I have even more depending systems and responsibilities in the current project I work at and I can catch even less bugs in just the code, especially because of different databases, M365, AD, APIs, etc. and so the LLMs helps to catch up with knowledge about ldap, as/400, Microsoft stuff, etc. and investing time in understanding the processes is more important than reading really every line of code. BUT as already written, I look at the diffs, run many checks (for sql typos, template errors, security, etc.), tests (unit + acceptance) and bind spot analysis runs) on top of my manually testing.

• 
  Sameer Soni (@SameerSoni0) reported 37 minutes ago

  @markleomc @github yeah just saw.. hopefully they fix it quick.. i have important PR to raise ;/

• 
  KrunalSinh Sisodia (@krunalbuilds) reported 38 minutes ago

  1/ An empty README = red flag. It tells me you built it and forgot it. Write one sentence. Just one. 2/ Committing directly to main. Every. Single. Time. Branches exist. Use them. 3/ 47 repos, 0 pinned. You're hiding your best work behind your worst. 4/ Commit messages that say "fix" or "update." Fix WHAT? Update WHAT? 5/ No contributions to anything public. Forks count. PRs count. Show you exist. 6/ Projects with no live link and no screenshots. I'm not cloning your repo to see if it works. 7/ A bio that says "Aspiring developer." You're a developer. Own it. 8/ Last commit: 8 months ago. Even one push a week signals you're still alive. Your GitHub isn't a storage drive. It's your pitch deck. What's the one thing you're fixing on yours today? Drop it below 👇

• 
  reachpad.dev (@reachpad) reported 42 minutes ago

  Github might be down, but we aren't!

• 
  Smindi (@SmindCrypto) reported 44 minutes ago

  India Government orders Bitchat takedown. @BitchatMe_ The Indian government has directed GitHub to take down repositories hosting Bitchat—a Bluetooth-based mesh messaging application created by former Twitter CEO Jack Dorsey—citing national security and law enforcement concerns. Reacting to the takedown order, Jack Dorsey posted a copy of the official notice on X (formerly Twitter), commenting: “The Government of India does not like technologies like Bitchat and wants it taken down.” The directive was issued on July 23, 2026, by the Indian Cyber Crime Coordination Centre (I4C) under the Ministry of Home Affairs. The Government gave Microsoft-owned GitHub a 3-hour window to disable access to three Bitchat source-code repositories. What triggered the notice? The notice was triggered after demonstrators at New Delhi’s Jantar Mantar (led by the Cockroach Janta Party protesting exam leaks) adopted Bluetooth mesh apps to communicate when local mobile internet services were turned off. Surveillance invasion: Authorities argued that because Bitchat leaves no server logs, user records, or centralized database, it severely hinders "lawful interception, attribution, and investigation" by law enforcement. The app allows users to continue communicating even during localized internet blackouts or network suspensions. Digital rights groups (such as the Internet Freedom Foundation) criticized the move, calling it authoritarian and pointing out that the order targets the software code itself rather than specific illegal content or illegal acts.

• 
  sMyle (🦋 @myles.dev) (@MylesBorins) reported 45 minutes ago

  I was definitely thinking about how I could streamline this even further if I had a small agent on my Synology, or a cloud agent in the tailnet. With that said, something satisfying about "doing it by hand" with a copy + paste from a GitHub issue on my phone.

• 
  Bishal Pal (@BishalP86329207) reported 45 minutes ago

  Debugging session from hell, and what I learned building an AI codebase explainer. I spent hours fighting a single, frustrating error while building CodebaseGuru: "vector must have at least 1 dimension" The pipeline seemed simple enough on paper: Fetch files from a GitHub URL, chunk the code, generate embeddings, and store them in Supabase pgvector. Everything worked smoothly right up until the final step. Saving the embeddings to Supabase kept completely crashing the app. It took local network issues, custom SQL functions, and one random empty array to figure out what was actually going wrong. Here is the breakdown of what broke, the root cause, and how I fixed it.👇 #buildinpublic #nextjs

• 
  Nicholas Yang (@NicholasLYang) reported 53 minutes ago

  @PredragGruevski @geoffreylitt GitHub ships about as fast as the MTA builds subway lines. How is stacked diffs still not widely available? Why is the site still so terrible?

• 
  DRG (@DRG2Boss) reported 54 minutes ago

  @SonicDcer Any luck with your existing Recomp repos? Such a shame GitHub took them down.

• 
  Shaun Smith (@evalstate) reported 55 minutes ago

  What's more painful. A Codex outage, or a GitHub outage?

• 
  LauRRRRRent (@_LR_) reported 57 minutes ago

  @tomcritchlow That's interesting. You can clean the UI by disabling features in a github repo (issues, PRs, wiki, ...). What would make Github "lite" to you?

• 
  James Bearish Bull (@jamesjasmy) reported 58 minutes ago

  Dear Max, @Max_Rabinovitch $CHZ #CHZ If you’re willing to take the time to answer a community member’s questions, I’d appreciate your thoughts on the following: As Chief Strategy Officer, can you explain your background in tokenomics and blockchain economics? From what’s publicly available, your experience appears to be primarily in creative direction, digital marketing, and sports partnerships rather than token design or economic strategy. In a sector where true strategy is defined by tokenomics, supply dynamics, and incentive structures, do you feel your skill set is the right fit for the CSO role? Or would your talents be better suited as Head of Marketing? Questions: 1. CHZ is down 98% from its all-time high, and most fan tokens are down 76–99% from their FTOs despite multiple championships. What measurable strategic wins over the past two years have actually improved holder outcomes? 2. The protocol distributes roughly $5.7 million per year in inflation rewards to just 13 validators at today’s prices — a number that would rise sharply if the token price increases. With minimal visible development on GitHub and the chain being largely recycled BNB Chain code, how do you justify this level of inflation? 3. Since Socios already runs validator nodes for clubs like PSG, why is the protocol diluting CHZ holders to pay external validators for infrastructure you’re already operating in-house? 4. How many full-time engineers are currently working exclusively on the Chiliz Chain L1, and how does that headcount compare to the annual cost of the validator reward set? 5. The promised 10% fan-token revenue buybacks stopped being publicly reported after May. Can you share the exact June and July 2026 figures now and explain why reporting went silent? 6. What percentage of the executive team, including yourself, holds CHZ purchased with their own after-tax money rather than received through allocations or bonuses? 7. Why does the parent company still sit on tens of millions in receivables from the operating entities, and are any of those related-party or consulting fees? 8. After years of running 80+ shallow pools with only $2.3 million TVL, why has liquidity still not been consolidated into one or two deep USDC pools? 9. When sporting success and major partnerships continue to be sold off by the market, what concrete change in tokenomics or utility is planned to stop new users from becoming the next wave of exit liquidity? 10. Looking at the gap between Vision 2030 rhetoric and the actual price, inflation, and transparency record, which three strategic decisions under your remit have most damaged long-term CHZ holder value? 11. Are you proud of the job you’ve done as CSO? What has been your greatest failure in the role, and what’s the single worst strategic decision you’ve made? 12. You’ve recently launched fan tokens for Michigan, USC, and other US university partners. Do you plan to buy any of these at launch and hold them for more than two years? If not, why not? Max, arguably you're the second most important person on the project, so these tough questions need to be answered. They're not meant personally - we just need to see what you're carrying in your locker and that you have a solid grasp of the tokenomics with a clear route forward.