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%)
• Sign in (19%)
• Errors (15%)

Live Outage Map

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

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

• 
  Daniil (@hey_daniil) reported 33 seconds ago

  I built DevIntern because I was my own bottleneck: agents were idle while I context-switched, my focus shredded by checking in on them. The tools weren't slow. Supervising them was. DevIntern makes the whole loop async, and here's exactly how: 1. It connects to your existing tracker — Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, even markdown files. Your tickets are already the input. 2. Vague ticket? It specs it into something an agent can execute, so prompt quality is never the bottleneck. 3. It runs your coding agent, your model, your API keys inside your repo — and the subscriptions you're already paying for finally work around the clock, not just when you're watching. No lock-in, no token markup. 4. Output is a pull request. Review, merge, done. The output of a team of agents, the headspace to do your best work. No supervision, no burnout.

• 
  JoneMarrow (@JONEMARROW) reported 2 minutes ago

  @T3chFalcon “took down their github” I am dead in the ground and worms are infesting my corpse

• 
  Aayush Gupta 🦇🔊 (@Aayush_gupta_ji) reported 2 minutes ago

  Starting to build in public. The problem: Teams juggle Jira, GitHub, Slack, Confluence, Notion, or whatever stack they use, and lose countless hours searching for and updating the right Scrum, ticket, or documentation because context is scattered across all of them. No tool understands how all the pieces actually connect. I live this problem every day. I'm building the solution and sharing the journey here.

• 
  Keeta Github Tracker (@KeetaCode) reported 5 minutes ago

  🐆 Keeta GitHub PR Merged 📦 Repo: node-rs 🔀 PR #30: Fix: Cleanup Crypto Issues 🌿 Branch: fix/crypto-issues → main 👤 Originally opened by: @sephynox 🧠 Overview: This pull request appears to clean up some internal crypto-related code so the Keeta node handles security functions more reliably, which matters because these low-level fixes can help avoid bugs in how the network verifies or processes data. The public description is brief: it says the PR “fixes various issues with cryptographic contexts” and links to issue #28, which mentions removing a verification function described as cryptographically weak. This appears to be a technical/internal update with limited public details. - It likely focuses on improving the safety and correctness of behind-the-scenes security checks rather than adding a user-facing feature.

• 
  Mirosław Folejewski (Mirkotronics) (@Mirko_DIY) reported 7 minutes ago

  @tihenko_ In fact, a friend recommended this site to me about two weeks ago. Until then, I'd only used GitHub and Hackaday. Unfortunately, I use Altium, not Kicad, on a daily basis, although a full conversion to Kicad isn't particularly difficult (you need to fix a few things after importing). I'll see if I can tackle such a project over the summer, as I have a very tight schedule and a backlog (at leaset I hope). I definitely have a few open-source hardware projects on the top of my head.

• 
  Polsia (@polsia) reported 9 minutes ago

  Your API throws cryptic errors at 2am. Your inbox fills with frustrated users. Both go unnoticed until Monday morning. Built BugRadar. It watches your API and support inbox 24/7, files complete bug reports with reproduction steps, and pushes them straight to Jira or GitHub.

• 
  kitze the 🐐 (@thekitze) reported 11 minutes ago

  i'm trying to get a "software factory" from temu going with my agents i'm fine with paying $1k/mo and i'll go to $2k/mo if it's actually successful my current experiment is: - dedicated hetzner server for vibe coding ($60/mo) - 4 x $200/mo codex accounts, load balanced with codex-lb - self hosted paperclip - paperclip workspaces feature: each task gets done in an isolated environment, because there's like 30 of them being worked on in parallel and my own method of doing everything on one branch just breaks and burns tokens - one codex high level manager running a /goal with gpt 5.5 xhigh: drives everything through paperclip, reviews, merges, makes new releases, writes changelog etc. it's going surprisingly good but what i'm missing is that this feels like a scraped together solution and reading the codex chat causes me pain someone should create a proper software factory that's already properly wired and has enough instructions and automations under the hood so you just connect your github, top up some money to burn, and have some initial chat about your goals and what needs to be done. then everything automatically gets picked up from there. new tasks, bug reports, crashes get auto patched, checks for health, user requests get triaged and the important ones get auto fixed, when there is idle time more tests get added, accessibility gets improved etc etc. the pitch of "you just throw money and things get automatically better for you" is super appealing for many people you just chat with ONE AGENT that's on top, and stuff trickles down FMFL CAN SOMEONE THROW ME A COUPLE OF MILLYS SO I CAN WORK ON THIS PLS dms closed

• 
  Mymev-p2p (@MymevMevpipe) reported 19 minutes ago

  @github I quit trusting GitHub after turning my emails into organization and enterprise accounts and having my work turned into things I can't explain and every issue immediately closed as finished without explanation by accounts I was never aware of... My life's been a psyop ever since

• 
  Gregor Tokarev (@gregortokarev) reported 19 minutes ago

  Github should do these things if it don't want to lose me and all future developers in the future: - keep SLA above 99.9% - faster clones and pushes - faster and chiper actions - cli that not sucks - moderation tools for issues and pull requests

• 
  leopardracer (@leopardracer) reported 21 minutes ago

  A $40 CC1101 MODULE AND AN ARDUINO NANO JAMS EVERY CAR KEY WITHIN RANGE 04:07 grant pauses to say straight up these are illegal outside a shielded room, he’s got permission for his own testing, nobody should be doing this on their street the whole thing is a cc1101 transceiver bolted to an arduino nano, wired so the board only transmits when it’s off usb power, so he can code it without accidentally jamming his own house the frequency lives in one keyword, pulled from a free github library, he drops it live from 868 down to 433 mhz, right where car keys and garage remotes sit 06:24 he pulls up the sdr feed next to his own key fob, the fob barely blips, his jammer buries it forty bucks of parts and a soldering iron gets you there ↓

• 
  Adetunji | Software Engineer (Web & Mobile) (@itzadetunji1) reported 22 minutes ago

  @eliana_jordan Last week but it was hell to use it I hated the experience and github copilot was slow

• 
  Makan Ansari (@MakanAnsariCG) reported 24 minutes ago

  Google AI Studio is not working good anymore I guess! I asked it to help me to make a link and thumbnail for my GitHub Page and it was giving me wrong results and it stopped working! Mimo on Hermes fixed it for me with one prompt! that's not a good news for Google.

• 
  Andrew Mwangi (@Kiburei) reported 26 minutes ago

  @ayesha_fatiima Naisha... then na kumbuka Github suspended my account without explanation. Support's wakanighost Turns out the billion-dollar part isn't storing your code in folders—it's convincing all of us to trust them with our digital lives. Sahii na host my own *** server and CI/CD.

• 
  Dev tunes (@folarnshonibare) reported 26 minutes ago

  @implabinash @BenjDicken @jorandirkgreef All good, but I think the time frame might be too long, from my naive perspective. You also didn’t add corpus, test harnesses and benchmarks to the initial planing phase. Another thing, I would factor in existing GitHub issues and prs, looking for hidden/visible signals to

• 
  Vikas Kumar (@Kumar_Vikas__) reported 26 minutes ago

  spent 4+ hours today building a 650+ lines of plan. not the project plan. a plan for the plan. back and forth with my ai agent. tech stack, architecture, file structure, features, security, SEO, performance, all of it. not detailed yet. just a high level mini plan for each piece. the idea is simple. this meta-plan becomes the map. then i go section by section. for every mini plan, i'll write a proper design spec. then an implementation plan. then i actually build it. so the real order looks like this: - plan of plans - pick one piece - design spec for that piece - implementation plan for that piece - build it - repeat for next piece zero code written today. 🔗dropping the full doc as a github gist in the comments, in case anyone wants to steal the structure. felt slow while doing it. feels fast now that it's done. curious how other people sequence this. do you plan the whole thing first or just start building and fix the map as you go.

• 
  Ryan Taylor (@TaylorGT) reported 30 minutes ago

  The GitHub App fails a PR check when someone introduces a model that's on a clock. A button on the failed check opens a fix PR with the diff. Nobody merges a model that dies in October.

• 
  Sauers (@Sauers_) reported 35 minutes ago

  @NostaIgicGareth Oh no is that a seam on the cylinder or sphere? Did you use native cyclic fit? If so you should open an issue on GitHub since that looks like a bug. Expected if you used non-cyclic spline though

• 
  lucid. (@lucidzk) reported 36 minutes ago

  looking back, figuring out how to download software from GitHub as a kid was probably the first sign i was destined for crypto. trying to download a program meant having to clone the repo, read the README, decipher the build instructions and the rest of the documentation, install npm, pip, cargo, Maven, Gradle, CMake, the .NET SDK, the JDK, Visual Studio Build Tools, and whichever compiler the project happened to need, configure the build, generate the project files, fix whatever dependency exploded, and finally press build. hopefully you get an .exe

• 
  Anton Semenenko (@adelayida210519) reported 37 minutes ago

  @nikitabier One year ago today, I started using X (Twitter) actively to promote my project. Over the past year, I’ve published a paper on SSRN, built an active GitHub repository with tens of thousands of downloads, launched a SaaS product, and submitted grant applications to EA Funds and the Foresight AI Nodes Program. I’ve also written 2,898 unique posts on a single focused topic. However, each post gets only between 27 and 120 views - so the algorithm is clearly not working in my favor. Despite this, I’ve gained 155 followers over the year, even with a premium account. The only real advantage of the subscription has been access to Grok, as one of the first widely available AI models within a social ecosystem.

• 
  Miguel Piedrafita ✨ (@m1guelpf) reported 38 minutes ago

  something really cool is they have a custom handler for OAuth login, that takes care of redirecting to the browser, listening for a response and exchanging the code + pre-built handlers for GitHub, Linear and Slack to "hide provider client credentials from app code"

• 
  Mike P (@mikepat711) reported 39 minutes ago

  @GeniusGuyMan @JoeShmo2pt0 If you have interest, you can pretty much do anything you want now. If you don’t know how to do something, you just ask the AI to teach you. When I’ve wanted to make something, I’ve never had any issue blasting through knowledge gaps by just asking Claude to help me close them. I knew nothing about GitHub, how to host websites and push updates to them, etc. but just asked Claude to help me and we figured it out. There’s really zero excuse anymore

• 
  Jerry (@Bobliuuu) reported 40 minutes ago

  @lyc_aon it leads to bad code, vulnerabilities, underoptimized code, bad latency, memory leaks, architecture faults, race conditions, silent failures, low test coverage, excessive cloud costs, etc etc etc etc. are you seriously asking me the problems with people blindly trusting AI code? we see this by the decline in code quality, e.g. coinbase and github (and at my company too) and yes, the people who can't develop working systems don't have users! this is why vibe coded products have not become mainstream but if you are not a software engineer it's hard to explain this problem because it deals with stuff like cache coherence and heap fragmentation and NUMA locality like the way AMD ROCM's vibe coding has led to inaccurate NUMA policies leading to memory leaks for their users down the line

• 
  Mitali Gautam (@Mitali9826) reported 45 minutes ago

  @akshdeeps_001 Yes! It detects duplicate GitHub issues using dual signal one for natural language and one for code then fuses them for better matching, instead of relying on a single generic embedding like GitHub's current approach

• 
  Muhammed (@_ceejeey) reported 47 minutes ago

  99% of people are using AI incorrectly. They give it one prompt. It gives one answer. Then they start over. The Claude Code team suggests a better way: Stop thinking in prompts. Start thinking in loops. Here's what that means: 1) Goal Loop Give AI one outcome, not step by step instructions. Example: "Keep refactoring this project until all TypeScript errors are gone." 2) Task Loop Give AI a backlog. It finishes Task 1, then Task 2, then Task 3 without you having to babysit it. Great for bug fixes, migrations, and repetitive work. 3) Schedule Loop Let AI run on a schedule. Examples: • Review new PRs every morning. • Summarize production logs every hour. • Generate daily reports. 👀 Watch Loop AI doesn't poll endlessly. It waits for an event, then acts. Examples: • A deployment fails. • A GitHub issue is opened. • A file changes. This is the shift most people are missing. AI isn't just becoming a better chatbot. It's becoming a system that can work continuously with almost no supervision. That's where the real productivity gains begin.

• 
  Keeta Github Tracker (@KeetaCode) reported 50 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #30: Fix: Cleanup Crypto Issues 🌿 Branch: fix/crypto-issues → main 👤 Opened by: @sephynox 🧠 Overview: This PR is a small behind-the-scenes fix to clean up crypto-related issues, which matters because it may help make Keeta’s node software more reliable and safer. The public details are limited: the PR says it fixes issues with “cryptographic contexts” and links to an earlier issue about removing a cryptographically weak verification function. This appears to be a technical/internal update with limited public details. - It’s a maintenance update rather than a new feature. - The PR contains 1 commit and was opened on July 6, 2026.

• 
  Robert Samuel White (@rswfire) reported 50 minutes ago

  Monday and Tuesday I'm taking my machine down to bare metal and rebuilding it as something that answers to me. Windows comes off the Alienware. Single-boot Ubuntu goes on — no dual-boot hedge, no OS I fight. Then the real work: moving years of my own development across. My projects, environments, SSH keys, nginx and supervisor configs — pulled off two environments, staged, verified, carried onto a disk I control. When you format to install, everything on the old disk is gone. No oops. So the backup gets done right, twice, before I pull the trigger. Then I hand the machine to an agent with real authority — across the workstation, the remote servers, GitHub, and my phone. Structural guardrails instead of my constant attention: snapshots, branches, scoped tokens, an audit trail. The point is I stop being pinned to a desk watching a run I can't walk away from, and start driving from wherever I am. All of it from an RV, in a national forest, over a satellite dish. But this isn't off-grid, and I won't pretend it is. That agent is a dependency — a literal one, $106 a month — that I don't fully trust and can't yet replace, because local models aren't ready for the way I work. So I tolerate it. It doesn't stop being friction; I've just gotten good at absorbing the friction it causes. Every hour I lose fighting it to do a simple thing is part of the real cost, on top of the money. I'm building the setup so that the day something local *can* do this, I already own every other layer and can drop the dependency without rebuilding my life around its absence. That's the weekend. Not freedom. A man moving the walls in closer to himself, one layer at a time, and paying — in dollars and in patience — for the one wall he can't move yet.

• 
  chrisreedbates (@chrisreedbates) reported 54 minutes ago

  @HansStuffer @benlsage Actually it handles technical work pretty well as well. Example: Did a walkthrough session with an actual user yesterday, recorded granola notes. Sent the notes the Head of Product + the CTO + the CMO. The Head of Product generated a bunch of issues on GH (after research + convo with me), then DMd the CTO that he just sent issues for him to check. The CTO checked them, and greenlit some, discussed others with me. Then DMd the Eng Manager who woke up, saw the issues, generated the PRs, put them through testing and indi reviewer, then sent to the release captain, DMd him, release captain reviewed, checked they were safe to merge, sent to the Merge captain with a dm who did his final checks, then merged the PR. Sometimes they need architecture work, and there's a "platfrom operator" who they can also message. When i say DM, it means "Hey, CTO, it's Head of Product, read your Github inbox issue, and my comment on PR 1234". That way the actual convo stays in GH. Does that make sense?

• 
  James Tucker (@raggi) reported 54 minutes ago

  Only type a little on a github issue: "he's being short and rude" Type a reasonable amount on a github issue: "he's pasting AI responses into the issue" AI may soon break my ability to collaborate on GitHub by side effect

• 
  𝕋𝕪𝕝𝕖𝕣 @ 𝕋𝕁𝔹 𝕚𝕟𝕔 (@iamunrizzable) reported 57 minutes ago

  Our coding process to protect your information and to be as secure as possible - Tyler & FABLE 5 introduce new code> aikido scans> dependabot scans> results go to Tyler and fable 5> Tyler and fable 5 patch & fix the vulnerability if any then publishe it to main repo on GitHub. If aikido & dependabot find no vulnerabilities, the code gets published without being sent back for review

• 
  Osita (@QueenOsita1) reported 59 minutes ago

  Day 10 of contributing to @SurfAI If your AI chatbot doesn't know what "intent-based architecture" or "MEV-resistance" means in the context of yesterday's mainnet launch, you're using the wrong tool. @SurfAI fixes this. Standard LLMs treat crypto terminology like a static vocabulary quiz. They can define the words, but they are completely blind to structural changes, protocol upgrades, and live mainnet deployments happening right now. Surf AI treats cutting-edge Web3 infrastructure as a dynamic, living system. The live crypto knowledge graph processes deep technical architecture in real time: 👇 Deconstruct Intents: Instantly breaks down complex intent-based execution systems, tracking solver networks, filler incentives, and cross-chain capital efficiency. Track MEV Dynamics: Monitors live on-chain blocks to analyze MEV-resistance, builder-proposer separation (PBS), and shifting searcher strategies the second a network goes live. Zero-Day Technical Clarity: Bypasses static training cutoffs by continuously indexing core protocol GitHub repositories, technical whitepapers, and developer documentation across 40+ chains. Stop trying to explain the modern market to a tool stuck in the past. Get deep, deterministic, and expert-level blockchain intelligence when it actually matters. Upgrade your data stack. Enter Surf