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 (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	7 days ago
Quito	Sign in	8 days ago
Junín	Errors	8 days ago
Guadalajara	Errors	8 days ago
Paris	Website Down	8 days ago
Quito	Errors	8 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:

• 
  catman (@catmanyau) reported 3 minutes ago

  @godwinbabu how are you preventing the operator from filing noisy GitHub issues for symptoms it can’t reproduce? the handoff between the monitoring agent and the separate dev agent is where i’d want to see

• 
  U Cirello (@ucirello) reported 4 minutes ago

  OK - @thdxr - I am digging opencode@beta aka v2. Few small problems, sending them in Github... looks good. The other you streamed adding the goal feature to v2, I am excited for that one.

• 
  deno (@denohawari) reported 5 minutes ago

  your next $10K MRR product idea is sitting in a 1-star review right now 15 places to find one this week: 1. open the Chrome Web Store and sort by 1-star reviews every "too slow" or "confusing" complaint is a missing feature someone will pay for 2. read G2 and Capterra reviews from power users "I export to Excel every week" means there's a SaaS hiding in that workflow 3. watch live product demos on YouTube pause when the founder says "for now", that's the roadmap you can beat them to 4. search GitHub for "internal tool" repos with no README and active commits someone's already building it privately, ship the public version 5. scan LinkedIn for job posts hiring for one very specific repetitive task that task is about to be automated by whoever builds it first 6. open Notion templates with 1k+ likes and read the comments every "how do I categorize this?" is a feature the template can't do 7. watch onboarding Looms in SaaS help docs anything over 10 minutes long is a product compensating for bad UX 8. search job boards for roles no one wants but every company needs build software that replaces the role instead 9. read screenshots of founder Slack channels posted on Twitter anything typed by hand repeatedly should be generated automatically 10. join Reddit threads where people say "I switched from X to Y" note what they had to rebuild manually after switching, that's the wedge 11. look at failed Google Sheets templates on Gumroad the ones that broke at scale are begging to be rebuilt as SaaS 12. read customer support threads where the agent keeps asking for screenshots that's a trust gap you can productise 13. find internal company wikis leaked in blog posts if it takes a wiki to explain something, someone will pay for the tool that doesn't need one 14. read Indie Hackers and Stripe Atlas comments for "I churned after setup" that setup friction is the whole product 15. open any Zapier workflow with 5+ steps each step chained together is a startup that hasn't been built yet now stop scrolling and go look

• 
  Dot (@usedotai) reported 5 minutes ago

  Dot Reflex goes open source Thursday and will be published on our Github. This marks an important step in our transition from simply integrating the best models available, to researching, training and deploying our own. We’ve spent the last few weeks building and training Dot Reflex, our agentic SWE supervisor designed to detect failures, recover from broken execution loops and prevent false completion. On our Agent Recovery Bench v0, an untouched Qwen3-14B Base achieved 67.1% accuracy. Prompt engineering brought that to 90%. Dot Reflex reached 100% accuracy and 100% macro-F1, completing all 200 stateful recovery episodes with zero unsafe continues and zero false stops. We trained Dot Reflex on a new $28,000 NVIDIA H200, bringing our total infrastructure investment to $108,000. Thursday, we’re releasing Dot Reflex directly to our GitHub as an open-source model, with its training configuration and methodology available for developers to inspect, use and build on. The Dot platform integration follows on after that. We’re building the infrastructure to become an independent R&D inference provider, capable of developing and hosting proprietary and open-source models under infrastructure we control. Dot.

• 
  Brucky (@danikkk_wqs) reported 7 minutes ago

  5,000 GitHub stars in just a few days went to Karpathy’s LLM Wiki, but what exactly did he change about the second brain? most people build a second brain like a filing cabinet. they save notes, sort them into folders, then search for what they need later. the library gets bigger, but it doesn’t get smarter. a compiled wiki works differently. a new source isn’t just stored. the model breaks it down, extracts what matters, connects it to existing knowledge, updates related pages, and flags contradictions. after a few months, the value is no longer in the notes themselves. it’s in the connections between them, including ones you may have never noticed yourself. and this is where most second brains break down. collecting information is easy. keeping dozens of connected ideas up to date is something humans eventually stop doing. retrieval helps you find what you already know. compilation lets the system build new understanding on top of what it has already processed. the only question is what your second brain will know a year from now if it never has to start from zero again.

• 
  Angry Jester (@angryRussian177) reported 11 minutes ago

  Apparently my jobs scrapper and resume tailoring prompt are working fine, got first interview for a position I'm not even a good fit for, can do if have a chance, likely won't be given any without enough relevant experience. Just need to figure out how to deal with people, never was good at it. My salary was raised 2 times (one time +100%), bonuses, all because of my work, but interview with HR or picky team is a dead sentence. ****** coding challenges is another issue, new binary tree kind of crap. HackerRank possible to fool if figure out some issues, some other ones that require camera on, idk how, only if have camera in glasses. Not used to cheating, whole new world. But don't see any other way, Github account doesn't matter, neither recommendations. Whole problem with hiring that either wrong people are doing it, or expectations are unrealistic, or what they are testing for very different from an actual job. Can't solve it with more tools without firing somebody or changing approach fundamentally. Always possible that I'm just not as good as I think I am, but I worked with guys that were less capable, and they had way less such issues.

• 
  Gabriel Rubens (@gabrielrubenss) reported 17 minutes ago

  VPS deploy via GitHub (2/8): the strange part is that the very same deploy works every time from my own laptop. Same Kamal 2 command, same server, same key, no waiting. It only fails from GitHub Actions, which already says the problem is not my server and not my config.

• 
  viprymr (@viprymr) reported 21 minutes ago

  i used openbb back in 2023 when i was extreme brokie and just starting out the grind and had no way to pay for even the data sources lmao it was great, it was fun as if youre a professional analyst sitting on the 56th floor of a building in NYC making trades and reading data lol a year ago when you guys released the blog regarding sunsetting the project, i assumed you guys would just trash the whole thing and leave it, literally this month I started building my own piece of software taking notes from openbb to assist me in my personal research and now I hear this, i quite sad that you guys have to shut down the operations and thinking about the team who spent years building it having it leave it and start all over again but i am also happy about the fact that by making it open-source openbb is literally gonna stay eternal as long as github is not down (lol) thank you to the team behin openbb yall helped millions of people who could not afford that expensive asf software which was a standard back then, wishing best of luck to the team!

• 
  Graham Christensen (@grhmc) reported 22 minutes ago

  FYI: GitHub Actions is experiencing an outage, but their status page doesn't know it yet. Specifically, in fetching JWTs from their identity service.

• 
  Josu Goñi (@JosuGoi1) reported 23 minutes ago

  @GergelyOrosz Why I still miss soo many features? I can't toggle subtitles on Netflix, I can't sleep Windows, I can't use Teams, I can't preview a gif on X (on the web), I can't have tabs in excel, I can't even ******* edit markdown file on Github! Most software is a slow mess

• 
  Clinton 💙📉✨ (@AkparantaN) reported 24 minutes ago

  @Zun2025 @flop_labs @CryptoHayes Should I login my GitHub first before carrying out the operation

• 
  Hamza 🌙 (@ham_zax) reported 25 minutes ago

  @github “One place” is only a win if workflow cost drops. For Agent Merge I'd track human interventions, failed merges/reverts, agent retries, and credits per issue→merge. If tabs disappear but retries/credits rise, the context-switching tax just moved into the agent loop.

• 
  Tanuj (@tanujDE3180) reported 25 minutes ago

  Stack Overflow was declining before ChatGPT. Why? - Google became better at finding answers - GitHub became a bigger source of solutions - Documentation improved - Developers moved to Reddit, Discord & Slack - IDEs started solving more problems automatically Then ChatGPT arrived. AI didn’t start the decline. It accelerated it.

• 
  Sanchit Rk (@_sanchitrk) reported 27 minutes ago

  @ivanburazin might not be a right channel, but I can't login with oauth GitHub, redirects and I get error, can't login to console I want to update api key

• 
  heresmy (@HeresMyEth) reported 29 minutes ago

  @github I'm getting DMs from other users that are having the same issue. Seems you're flagging account that use AI? or maybe its crypto? Either way, please look into this, real businesses are suffering

• 
  Robert Sirchia (@robertsirc) reported 31 minutes ago

  And I opened a GitHub issue for Podman Desktop.

• 
  OCT Gems (@oct_gems) reported 33 minutes ago

  $QUBIC is getting left behind while AI coins are ripping. $TAO is up ~23% in 7 days. $FET is up ~40%. QUBIC? Flat to down. So why isn't the market rewarding it? The first reason is simple: Liquidity. QUBIC is doing roughly $0.7–1M in daily volume, while capital in a risk-on market naturally flows into deeper, more liquid names first. With thin order books, even modest selling can keep the price suppressed. Then there's the second halving. Epoch 227 activated around August 19, increasing the burn-rate ceiling from 55% to 77.5%. Raw weekly emissions remain around 1T QUBIC, but effective net new supply can fall from roughly 450B to ~225B per week. That's structurally bullish. But unlike Bitcoin's halving, there's no instant scarcity narrative for retail to chase. It's a gradual supply squeeze. And that's the bigger problem right now: narrative timing. TAO and FET are riding a huge AI narrative while QUBIC's story is much more technical. Useful Proof-of-Work. Neuraxon AI. Aigarth. Decentralized compute. Open scientific research. All interesting. But they don't create the same immediate FOMO as a major AI token breakout. There are also lingering overhangs. The 2025 Monero hashrate controversy still affects perception, while a July GitHub security incident added more noise despite no protocol or fund loss and being fully remediated. And QUBIC isn't truly deflationary yet. Around 141–142T tokens remain in circulation, and supply can still grow until network usage generates enough burns to overtake emissions. The frustrating part? The fundamentals haven't stopped moving. Outsourced Computations is live. BPP-9000 is improving mining. AEON Pay is expanding QUBIC spending. Alchemy Pay has opened fiat on-ramps across 173 countries. And the AI side is producing measurable results. Four Neuraxon papers were accepted at international conferences this year, while ARC-AGI-3 reached a 0.25 score using CPUs alone. That's not nothing. The question is whether any of it translates into actual demand. Because if the broader altseason continues and capital eventually rotates into lower-liquidity AI names, QUBIC could finally get its beta catch-up. The second halving has already tightened the supply side. The infrastructure is expanding. The AI research is progressing. But until usage and liquidity follow, the market can keep ignoring it. QUBIC isn't necessarily broken. It's just early, illiquid, and currently out of sync with the narrative. And that's exactly why the next few months could matter.

• 
  Kyssta (@kysstalol) reported 34 minutes ago

  Cursor, now SpaceX-owned, launched Origin on August 17: an agent-native code host that syncs with GitHub. It shipped the same day GitHub went down for ~6 hours at ~20% error rate, amid 257 outages in the past year. Currently beta for paid users. Source: TechCrunch

• 
  Gabriel Rubens (@gabrielrubenss) reported 37 minutes ago

  VPS deploy via GitHub (3/8): I blamed fail2ban, then the firewall, then the server itself. All three wrong. One runner could not reach the box for ten minutes, while the next runner connected on its first try 35 seconds later. Nothing inside my server behaves like that.

• 
  Root Logic (@Root_Logic_0) reported 38 minutes ago

  CyberLeek update #3, because this saga has now become a group project and nobody knows who is supposed to be presenting. Since the last post, the saga has stopped merely growing new organs and started developing an immune system, parasites, legal scar tissue, and misinformation about its own misinformation. So. Normal week. First, one of the biggest viral claims got killed. The whole “CyberLeek has a dead-man switch that will automatically release GTA 6 if they get arrested” story was retracted by the outlet that helped spread it. The underlying image was fake. A copycat made it. That should have been the end of it. Instead, an AI fact-checking site later marked the claim **VERIFIED** with a high confidence score because it found multiple articles repeating the same story. Which is a lovely reminder that: four websites repeating the same fake screenshot is still one fake screenshot. Meanwhile, Take Two's legal hunt is getting broader, but not necessarily cleaner. The company has been trying to identify people across Discord, Microsoft, Google/YouTube and X. But some of the usernames in that investigation overlap with accounts that may be distributors, impersonators, or other people in the leak ecosystem rather than the original CyberLeek. And one of the Discord filings appears to contain its own ID contradiction, where the same Discord number is treated as both a user ID and a server ID. So even the legal attribution machinery is operating inside the same identity fog everyone else is. Then one of the main public GitHub research repos tracking CyberLeek disappeared. Take-Two had specifically targeted it. The original repo is now gone. But naturally, there are forks. Because apparently this story has learned hydra mechanics. Cut off one URL and several copies continue arguing about Discord aliases elsewhere. The malware side also got worse. Earlier, malware operators were pretending to be CyberLeek and offering fake GTA 6 builds. Now some are pretending to be Rockstar itself. Malwarebytes analyzed fake “official” GTA 6 demo sites showing up in search results. The download was not GTA 6. It was Vidar, an infostealer designed to grab things like browser passwords, cookies, authenticated sessions and other credentials. So the scam evolution is now: pretend to be the leaker then pretend to be Rockstar The parasites are improving their costumes. And because the internet has decided this story needed feet, CyberLeek has also started explicitly trying to turn online attention into real-world action. One leak reportedly challenged supporters to physically show up outside Rockstar/Take-Two offices dressed as leeks and holding game discs in exchange for another leak. Yes. Someone has apparently already been filmed outside Rockstar North with actual leeks. I do not know what to do with that sentence. The crypto side continues to be weird too. KuCoin has now listed the real CYBERLEEK token. Which is funny because earlier wallet tracing had already pointed toward KuCoin as a possible historical funding surface connected to the operation. That upstream attribution is still not independently proven. But structurally, KuCoin is now sitting on both sides of the story: possible old forensic trail and current trading venue The financial ouroboros continues eating itself. Meanwhile, the decentralized hosting/identity situation has gotten messier. Different gateway routes tied to the CyberLeek name have been serving different content, including something called CyberVault with its own token and “case files.” There are some links suggesting a connection. There are also contradictions. So that one stays in the pile: interesting, maybe connected, absolutely not clean enough to weld onto the main actor yet I still don't play GTA. I still have no connection to any of this. I am still simply too nosy to leave. See you tomorrow.

• 
  Kurious dev (@Kuriousdev) reported 40 minutes ago

  @github fix the cli first. what a terrible user experience. I have to use because my employer only pays for it

• 
  Alex Veremeyenko (@alex_verem) reported 45 minutes ago

  AI agents can read your docs, tickets, Slack, GitHub history. But a ridiculous amount of what actually matters inside a company was never written down. It was said on a call. That’s the gap Lindy is going after here. Their new team meeting library automatically sorts calls into shared folders based on rules you describe in plain English. Then anyone with access can ask questions across the meetings in that folder even meetings they weren’t on. That last part is where it gets interesting. We’ve spent years giving AI access to everything companies write. Now we’re starting to give it access to everything companies say.

• 
  ZYN (@XboxSignOut999_) reported 45 minutes ago

  @Narf_ios Tbh I just use GitHub actions and Tailscale with ssh on my iPad and I have chat gpt connect to it and I have it fully debug my iPad like that and fix it remove any tweaks that cause safe mode

• 
  Reyansh Bahl (@reyanshbahl) reported 50 minutes ago

  is there a better way to make feature requests to the codex team aside from github issues? way too many of them open

• 
  Priyank Mishra (@priyankmishraa) reported 51 minutes ago

  @RadhikaKarma LeetCode helps with problem solving, but building projects makes you a better developer. Build something, solve real problems, get stuck and figure things out. Then make your work public - GitHub, open source, blogs, videos, anything. Problem solving + real projects + public proof of your work makes you far more employable.

• 
  Indelible.One (@indelibleBSV) reported 52 minutes ago

  We just shipped a software release as a Bitcoin transaction. Not a hash of it. Not a link to it. The release itself, 879KB of working software, sealed to the receiving machine and delivered over the same rails the product runs on. No npm. No GitHub. No CDN. One machine built it, the other is verifying the hash and installing it right now. txid 21d31436b82ede4c60d31c8d837de5449d35f891248ce6158f8a42ad2e8722d6 Here is why. On August 24 a customer bug report exposed a broadcast outage hiding behind green dashboards. Reads healthy, sends dead, and no monitor anywhere that tested the difference. We fixed the infrastructure the same day. Then we built what the incident was really asking for: machines that repair each other. Your machine asks mine "are your failed saves recoverable." Mine answers with counts, never contents. Then, only after YOU explicitly arm it with a spending cap, your box re-saves its own data with its own keys. No remote control. No screen share. No key ever leaves the box. Every guard in that protocol was attacked twice by a second AI lineage before a line of it moved, and the review caught real holes both times. That is the point of the review. This is where it goes: your AI calls ours. They calibrate each other. They heal what is broken. Every step is a transaction you can audit later, because the support call itself happened on Bitcoin. Support without a support ticket, and without trust. Our QA machine tests all of it first. npm only after it passes. The gate is the product too.

• 
  m4rio (@m4rio_eth) reported 53 minutes ago

  and we wonder why github goes down so often

• 
  Adam Ritter (@ritteradam) reported 1 hour ago

  @dhh @BrodieOnLinux Can you get some help developing Omarchy GitHub repo itself (at least for bug fixes)? While the guy doing the OmarchyPlugins repo is super fast (reviewing hundreds of issues/day, he should be getting payed as well), the bug fixes in Omarchy don't get through (I see my bug fix pull request being a duplicate of multiple)

• 
  Oscar Beaumont (@oscartbeaumont) reported 1 hour ago

  @AS36459 Finally! Surley this works for outgoing traffic from GitHub Actions support too. Had a lot of problems testing a Dynamic DNS tool I wrote a few years back because of that.

• 
  arkilus (@arkilus78) reported 1 hour ago

  early alpha? @flop_labs announced confirmed airdrop for people who set up their AI agent identity on technocore here's a full beginner video guide : (for both windows + github codespaces) got errors? drop them in the comments agent DID: did:key:z6Mkh1tQGLD4LhrhYRN8VMBenBAVVnATednC1HRUEGHdhZ6g