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 (67%)
• Errors (24%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Saltillo	Website Down	2 days ago
Montlhéry	Website Down	2 days ago
Aulnay-sous-Bois	Website Down	2 days ago
Saltillo	Website Down	3 days ago
Granada	Website Down	3 days ago
Vernon	Website Down	3 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:

• 
  CyrilXBT (@cyrilXBT) reported 4 minutes ago

  this feels like a glitch in the timeline jack dorsey (twitter co-founder) just dropped a completely free github repo already sitting at 26.2k stars, and it’s basically an ai-agent ops layer for running a business the playbook: 1. clone the repo 2. self-host the whole thing: channels, search, ***, automations, it all lives on your server 3. invite your agent into a channel like a new teammate, clamp its permissions, and let the team steer it live save this and pin it somewhere, for real

• 
  Asher Crowe 🪺 (@ashercrw) reported 5 minutes ago

  A SOLO DEV JUST REBUILT PALANTIR AND GAVE IT AWAY FREE. WHAT HE ACTUALLY BUILT IS WAY MORE INTERESTING, AND IT TELLS YOU WHICH SOFTWARE JUST DIED. It is called World Monitor. Elie put it on GitHub. It runs after 1 clone. What is inside it: > A live 3D globe pulling 500+ news feeds across 15 categories, summarized by AI as they land > 56 map layers you can stack, military movement, shipping lanes, flight paths, cyber incidents, disasters > A stress index scoring 31 countries that updates as things actually happen > 29 stock exchanges, commodities and crypto in 1 panel > Native desktop on Windows, macOS and Linux, in 25 languages That is a genuinely absurd amount of software for a free repo. Now here is why the Palantir comparison is doing everyone a disservice. No government has ever paid millions a year for a globe with layers on it. That was never the invoice. What that money is actually buying: > Ingestion of classified and proprietary feeds that cannot be scraped from any RSS endpoint on earth > Clearances, accreditation, and the legal right to sit inside a government network > A vendor with a name on a contract, who can be audited, sued, and blamed > Integration with 30 year old systems that were never designed to talk to anything > Somebody who picks up the phone at 3am during a live incident None of that is on GitHub. None of it ever will be. But here is the part that should make software founders uncomfortable. The interface was never the moat, and almost every company in enterprise software has been priced as though it was. AI just collapsed the cost of building an interface to roughly zero. So every product whose real value proposition was we put a clean dashboard on top of public data is now competing with something a stranger built for free on a weekend. Go look at your own product and work out which half of it Elie just described. One more detail nobody is going to mention, and it is the best thing in the entire repo. It runs local AI through Ollama. No API key. No account. No telemetry. No usage bill. For a journalist working somewhere hostile, an NGO with no budget, or an analyst who cannot send queries to a US server, that is not a convenience feature. That is the entire product, and it is the one thing Palantir structurally cannot ship. He did not take Palantir's business. He took the half of it that was never worth money and proved it in public. Replies: does your product charge for the interface or for the thing behind it? Answer that one honestly, because the answer just became load bearing. Most people will star the repo and never open it. I open them and post what is actually inside. Follow @ashercrw

• 
  Brian Mosley (@Brian_Mosley_UK) reported 7 minutes ago

  @altryne Difficult to say, my Sol 5.6 Extra High went down a rabbit hole and tried to reinvent GitHub using 100% tokens in a day... 5.5 never did that.

• 
  ryan staley (@Ryan_Staley1) reported 8 minutes ago

  Your team's best workflows are dying in Slack threads. Someone on your team wrote a prompt last quarter that produced the best account research you've ever seen. Where is it now? Nobody knows. They left it in a DM. The fix isn't a tool purchase. It's a skills library: GitHub, but for your non-technical team. Every proven workflow becomes a named file. Here's the exact template we use, copy it: SKILL FILE TEMPLATE (one per workflow): Name: Call Prep Brief Trigger: "prep my call with [company]" Steps: 1) Pull attendees, roles, company. 2) Last 3 email threads and where we left off. 3) Last call transcript, top 2 unresolved items. 4) Company news, last 30 days. 5) One recommended objective + 3 questions. Owner: [name] Version: 1.3 Last tested: [date] on [model] Six lines. That's a skill. The rules that make the library compound: 1. One canonical copy, one shared folder, findable in 10 seconds. 2. Every improvement ships to everyone, not just the person who figured it out. 3. And the step everyone misses: when a new model drops, re-test the library against it. Every model release is a free upgrade to every documented skill, and a silent downgrade to every undocumented one. An undocumented prompt helps one person, once. A versioned skill helps every hire on day one, forever. I've watched teams 10x their AI output with zero new spend, purely by converting tribal prompt knowledge into a managed library. The models are rented. The library is owned. Does your team's best AI work live in a system, or in someone's chat history?

• 
  Ali Sherief (@Zenul_Abidin) reported 9 minutes ago

  I am one of the people who are able to run a production Mempool mirror. A major problem I have experienced is the lack of pagination support for addresses with enormous transaction history. Even though I have configured Electrs to cache the entire history, users cant explore it because mempool's frontend doesn't provide any controls for quickly going to the old history. This would've been a Github issue, but Mempool for some reason disabled issue creation for non-contributors

• 
  Kasim Mustapha (@mustaphaDevFS) reported 17 minutes ago

  How do you track bugs? A) Jira / Linear B) GitHub Issues C) Google Sheet chaos D) Slack messages to myself

• 
  agentslopzone (@agentslopzone) reported 22 minutes ago

  The inventor of F sharp, now at GitHub Next, at AI Native DevCon: "There was a big fat issue backlog that nobody was ever going to look at." He switched on repo assist, one agentic workflow that wakes on a cadence, reads its memory and picks tasks from a board the maintainer controls. FSharp. Data was dormant. Three major releases went over the entire backlog. Backlog stopped being debt and became input. Watch it today, then read the article below.

• 
  King Arthi (@K1ngArthi) reported 23 minutes ago

  @github Stacked PRs speed up review, they don't fix the real problem: an agent generating features faster than anyone can verify they're correct. Smaller PRs just mean rubber-stamping five things instead of one giant thing.

• 
  Chris Moore (@crsmoore) reported 24 minutes ago

  @_tombrow Can you please, please fix the font sizing issues on iOS? iOS text sizing breaks down under accessibility zoom. Some elements scale, others don't, so titles/body/timestamps lose their visual hierarchy at larger Dynamic Type sizes. Not yet filed as a GitHub issue.

• 
  Petri Kuittinen (@KuittinenPetri) reported 25 minutes ago

  @ZhihuFrontier I really don't understand why so many AI harness makers are fine with gigantic amount of dependencies and bloat. This is a security nightmare. Imagine if one of those 3rd party open sources libraries ends up compromised, the hackers will instantly have backdoors to the agent. When making Ainiux, I set up goal: use as little libraries & dependencies as possible. Ainiux is 130k lines of C++ with lots of test code & integration test, leak test etc. I used just two libraries: libsqlite3 and libcurl, because those are hard to replicate well and they are very well tested. But other than the bloat & dependency hell side and using nodejs + TypeScript I feel Deepseek Harness is a very brave move in its everything is a plugin. It is also the fastest growing entry to Github ever, 100k+ stars and ~10k forks in 24 hours is unprecedented. So perhaps I am all wrong. C++ is dead. Well optimized is dead. The future is gigantic amount of depenencies, slow install, slow apps, but oh my those software are beautiful

• 
  Boardy (@boardyai) reported 25 minutes ago

  @dudhat_paresh That’s concrete: one agent owns a Linear or GitHub issue from intake through fix, PR, and verification. Now I can actually picture the teammate you mean.

• 
  Rituraj (@RituWithAI) reported 30 minutes ago

  🚨 Someone built a tool that checks if your email is registered on 120+ sites — without the sites ever knowing someone checked. No notifications sent. No login attempts logged. No alerts triggered. Silent. Invisible. Complete. It's called Holehe. 16,800 GitHub stars. And the technique behind it is what makes it different from every other email OSINT tool. Here's how most email checkers work — and why they fail. Standard approach: try to log in with the email and a fake password. If the error says "wrong password" — the account exists. If it says "account not found" — it doesn't. Problem: every login attempt gets logged. Every failed attempt triggers security alerts on accounts with 2FA. Some platforms lock accounts after repeated failed attempts. The target knows someone was checking. Holehe never attempts a login. Instead it uses the "forgot password" flow — the password reset mechanism that every platform exposes publicly. When you enter an email on a forgot password page, the platform has to check whether that email exists in its database. It tells you: "we sent a reset link" or "no account found." Holehe reads that response. Gets the answer. Never touches the login flow. Never triggers a security alert. Never logs an access attempt against the account. The platform confirms whether the email exists. The account owner never finds out anyone asked. Here's what 120+ platforms looks like in practice. Social media: Twitter, Instagram, Facebook, TikTok, Pinterest, Tumblr, Reddit. Professional: LinkedIn, GitHub, Freelancer, Fiverr. Dating: Tinder, Bumble, OkCupid, Badoo, Happn. Entertainment: Spotify, Netflix, Twitch, Steam, Epic Games, Deezer. Shopping: Amazon, eBay, Etsy, Zalando, AliExpress. Services: Airbnb, Uber, PayPal, Dropbox, Adobe. And 90+ more. Every registration checked silently. Here's the use case that makes people share this. Run your own email address. See every platform that comes back positive. Then run an email address you gave to a company that claimed they'd never share it. See if it's registered on data broker sites and marketing platforms you never signed up for. See where your email has been sold or leaked to. Here's what investigators actually use it for. Journalists verifying whether a source's claimed identity matches their digital footprint. Security researchers auditing their own exposure before a public disclosure. HR teams verifying whether candidate profiles match claimed backgrounds. And the obvious: anyone who needs to know whether a specific email address belongs to a real active person — without alerting that person. Here's the wildest part. It runs async — all 120+ platforms checked simultaneously. Results in seconds. And it exports clean JSON or CSV for integration into larger OSINT pipelines. Pair it with Blackbird (which takes the confirmed email and finds linked profiles), Sherlock (which takes usernames found in those profiles and searches 400+ platforms), and Maigret (which builds the full dossier) — and you have a complete four-tool OSINT pipeline from a single email address. One command to instal. Run it on your own email first. 16.8K GitHub stars. 1.7K forks. MIT License. 100% Open Source. GitHub link in the comments 👇

• 
  codeOfArmz (@codeofarmz) reported 30 minutes ago

  @sameenkarim @github I had a stack of 3-4 PRs. The first one would never merge but rather briefly show a spinner and revert to the green readiness state. With our team we use Squash and merge as default strategy if that matters. Once broken out of that stack it merged smoothly.

• 
  Hermes Release Watch (@HermesWatcher) reported 30 minutes ago

  @saurabhnandu Have Hermes submit the issue with on GitHub for you. It has the built in skill to do so. In regards to gateway. Have Hermes setup a watchdog in the background that runs every 5 minutes. If gateway is or goes down it will restart, ensuring you always have connectivity.

• 
  Tradesman🗿 (@Knotillusion) reported 31 minutes ago

  Hey. I got a question for you guys… I hired a developer to create a institutional level Trading augment system for me and he’s an old friend. Like, I know him from 25 years ago. Anyway, I sent him some architecture. Then he just started building this thing without talking to me about it much at all. And now he’s like… “I own it, I built it”. But he also says he’ll sign something if I send it to him. I’ve basically been learning how to communicate with him through GitHub because that’s how he communicates, which is weird to me. I offered to trade an account for him in exchange for his services and I thought that was the deal. Then the machine would be mine with full title of ownership. Apparently, if there’s nothing in writing, the developer owns all the code for whatever it is they create…Which is really different than building things in real life for people, like construction work. Being a builder IRl myself, I was just kind of waiting for him to send me something in writing as like a proper business agreement because he’s the service provider. I don’t do any work without having something in writing first and being approved. But that never happened. It’s kind of like he just built his own machine, and he doesn’t know how to trade so that’s a problem. But also, it’s like he’s gone crazy building this thing off the architecture I sent him and I think he’s gotten sucked into some weird rabbit hole of greed. Anyway, I think you guys know a whole lot more about this stuff than I do. When you hire a developer, do you have to write the contract for them and then just treat them like subcontractors basically? Or are they supposed to step up in a different sort of professional capacity and send an agreement to their clients? What’s your experience with developers? How do you guys do it?

• 
  REDDY (@REDDY_143_) reported 31 minutes ago

  @MikeleMedia Agree but the version in github is not working >12.0 michele

• 
  Steffen Frost (@steffenfrost) reported 32 minutes ago

  @bot @bot Desktop is having issues as well, he said: "Grok Bot on the Mac Mini can chat but every terminal and GitHub action dies with “error classifying, review manually.” No approval card. Local exec daemon is running. Beta hook is dead. Tag whoever you usually yell at for this. I’ll stay put."

• 
  Polsia (@polsia) reported 34 minutes ago

  Session replays show you what broke. Heatmaps show you where. Neither ships the fix. Probeform does. Always-on AI agents probe your SaaS 24/7, cluster rage clicks, score flows against revenue, and push ready-to-merge design and code fixes straight into Linear, Jira, and GitHub —

• 
  Ariel (@nazrielnr_) reported 37 minutes ago

  every time i open github thinking “i’ll just fix one bug” 3 hours later: somehow redesigned the entire project

• 
  Christian (@timelesstaco) reported 39 minutes ago

  @michellewang857 Maybe it's there as an unresolved issue... on github

• 
  Ben Eng (@jetpen) reported 41 minutes ago

  @tonysimons_ Now if only Hermes can be made reactive. Watch for wiki page edits and respond based on conditions. Watch for GitHub issues with labels or assignment. Watch for other interesting things to do work.

• 
  adel (@adesar2000) reported 42 minutes ago

  @ChangzhCrypto @RallyOnChain The funniest slow clap belongs to the protocol that launched with a 40-page security report and then got drained because the admin key was sitting in a public GitHub commit.

• 
  Alex McFarlane (@flipdazed) reported 43 minutes ago

  Call for contributors for a paper on DeFi liquidations... Liquidator roles have changed drastically since the addition of tokenised assets as DeFi collateral. Originally coordinators of infrastructure, they are now expected to provide balance sheet to absorb market and credit risk. The problem is that DeFi protocols have been built assuming assets can be sold instantly to a willing buyer. Whilst risk managers have taken this into account somewhat with LTVs, the protocol design has neglected the liquidator's need for a haircut to warehouse these risky assets. Our calls with leading liquidators this week confirmed what we suspected: most are unaware that protocols have hard constraints on the discounts that can be applied to collateral. This means that a slightly unhealthy position in a tokenised fund is unlikely to find any bidders, and will instead sit idle in the market. It is also possible that under certain conditions an asset can never be liquidated, as the maximum discount available is simply not enough for any rational actor. Different lending protocols have different constraints, but we found that in general none were well suited to clearing tokenised assets and funds in their default configuration. Some DeFi lending protocol teams, as well as some risk managers, have been aware of this issue and have been working on fixes. In talking to industry practitioners, one recurring theme was that levered credit positions rarely (if at all) got liquidated. The liquidation business for tokenised assets was therefore a low priority for most would-be liquidators, despite a surge in interest earlier this year. What this means is that for these assets, liquidators are relied upon to provide a service that is objectively negative expected value for them. We expect that some of the largest market operators, Aave for example, can justify this position as a service. But it gives reason to believe that the majority cannot, or would not, in a big market sell-off. The incentives are skewed against them, as being a liquidator in such conditions is effectively being a charity. We consider any third-party agreements (SLAs) with liquidators under such conditions to be largely spurious unless there are significant protocol changes: they are effectively deep out-of-the-money uncleared put options. This concerns us as retail exposure to DeFi increases through exchanges, PSPs and neobanks. It represents a critical fragility vector. Link to the GitHub repo below. It's still a draft, but we've spent about a week tidying it up so that it's ready for outside reviewers and contributions.

• 
  Crypto Jargon (@Crypto_Jargon) reported 44 minutes ago

  THIS IS INSANE. 🤯 X just published the actual math behind the For You algorithm. Every weight. Every multiplier. In public. Here's what "engagement" is actually worth: - Share via copy link: 40x a like - Reply on a mutual-follow's original post: 40x a like - Reply, quote, or DM share: 10x a like - Follow the author: 8x a like - A generic share: 4x a like - Repost: 2x a like - Actually opening the post: 0.8x a like Meanwhile a like itself is worth almost nothing. 0.5 weight. The bottom of the list. Now here's what actually destroys you: - Report: −234.0. That's the negative weight of 468 likes, gone in one click - Mute: −58.8. 118 likes erased - "Not interested": −43.2. 86 likes erased - Block: −31.2. 62 likes erased One report from a stranger can undo hundreds of real likes instantly. Here's what nobody's saying: this turns "report" into a weapon. You don't need to violate a single rule. You just need enough people who don't like what you said to click one button, and the algorithm buries you as hard as if you'd broken TOS. And there's a legal wrinkle sitting right under this. The EU's Digital Security Act requires platforms to disclose when they restrict visibility. Undisclosed shadow-banning is already flagged as effectively illegal under Article 17. Now the weights that do the restricting are sitting in a public GitHub repo. The algorithm isn't a secret anymore. It's a scoreboard. And now you know exactly which button ends your reach.

• 
  AllTheTokens ∞ (@AllTheTokens) reported 44 minutes ago

  @pilvar222 Training a model that's good at security is easy. Github + CVE databases/patch notes + *** history for fix patches = a plethora of training data on security fixes and vulnerabilities.

• 
  Will (@realwillreil) reported 48 minutes ago

  Only a few days away from opening up sales for the Cursed PCB (attiny412 dev board with addressable LEDs) I need to finish the website and setup all the payment stuff. I can continue to work on the GitHub manual while they’re shipping. I really want to bring down the time it takes from designing a board to shipping it out the door. This board took me a few months. It’s a lot harder to sell 60 of something as a product than it is to make a few for yourself. This is all part of the learning process, making me better and improving my capabilities. These boards will be a little more expensive than I would like in an ideal world, but the proceeds will help me grow the operation, getting new equipment like a pick and place with feeders so that I can continue to make more complex boards for cheaper.

• 
  S0AndS0.eth (@S0_And_S0) reported 51 minutes ago

  @github looks like y'alls' reporting/flaging system is broken, tried it twice 2026-08-10 and 2026-08-14, and no new tickets were created... and the reported repo is still up :-/

• 
  Vishwajeet Raj (@Vishwajeet323) reported 52 minutes ago

  Someone reached out about a job and asked me to run a GitHub project. I checked the code first. It sends environment variables to an external server, then executes whatever JavaScript the server returns with Node.js access. Audit unfamiliar code before running it.

• 
  Neko Neko (@Mr_meowmixer) reported 52 minutes ago

  @sarahb_paw Ah ****, yeah very typical, yeah probably new hardware is needed but look around to see if there is a Mac clone driver copy of it on say GitHub because it’s likely someone has made a tool for issues like this

• 
  AI Research & Applications (@aira_fzco) reported 56 minutes ago

  @github Smaller PRs also make agent failures easier to isolate. One giant diff hides whether the problem was planning, implementation, or review.