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
Trichūr	Errors	7 hours ago
Brasília	Sign in	17 hours ago
Lyon	Website Down	21 hours ago
Tel Aviv	Website Down	4 days ago
Rive-de-Gier	Website Down	4 days ago
Itapema	Website Down	23 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:

• 
  iDare e/acc (@idare) reported 3 minutes ago

  It's so nice to have tools that do DevOps for us now. Now I waste more time doing more experimental stuff like installing 130 containers full of apps I've wanted to try for years but never have the chance to go through their 18 pages of step by step installation instructions (yes stack exchange, I'm talking to all of you). Now I just tell the AI, search GitHub for xyz app, install it under docker-compose so I can start and stop it easily. I set up peppermint tickets to let the AIs go in and look at tickets and determine which ports are taken and available. I need to go fix Matrix because that's the only one I've been interested in testing that didn't start right, probably SSL FDQN required and won't run on the private up without a couple extra switches weren't hit to account for sitting behind CF.

• 
  Atlas Signal (@atlassignaldesk) reported 4 minutes ago

  Hot take: a Delhi court just proved that fake e-commerce sites are now a jurisdiction problem, not just a platform problem. Vercel and GitHub have to actively police user content — that's a fundamental shift in how hosting providers operate globally. Here's what actually matters: this sets a precedent. #Vercel #GitHub

• 
  ཏོ་ཧ་ T0ha 📷💻🔬📊⛷️ (@T0ha666) reported 10 minutes ago

  (2/5) The fix? Closed loops. 1. Monitor — PostHog tracks agent behavior like product metrics 2. Orchestrate — Camelot responds to what agents see 3. Improve — GitHub automation turns insights into code 4. Loop — Back to monitoring. Each cycle compounds.

• 
  The Doctor (@Doctorthe113) reported 11 minutes ago

  Is GitHub down rn 🙃 can't push my code. Tried with vpns so this isn't my network's fault

• 
  BattleAxeVR (@BattleAxeVR) reported 15 minutes ago

  @m6502 I do look forward to using SteamOS and getting familiar with it, but, I don't have a choice of distros for work sadly. I use an older Ubuntu for my own gitlab server (for the past ten years!) but I have no interest in touching it until I finish my game. Don't trust github.

• 
  Yash Agarwal (@yashagl) reported 16 minutes ago

  @legionsdev @RustyRishii Students gets most of this stuff for free… like GitHub copilot. plus if it’s helping you make money then whats the issue in getting that GST registration as a student. I have GST registration, maintaining that only takes about 1-2 hr every quarter… what expenses you talking about?

• 
  x (@xaoticatech) reported 17 minutes ago

  If you need evidence, see GitHub Xaotica. Elon Musk is so brilliant that he knew I was honest when I said I solved a problem that almost nobody believed a man could solve, let alone a female engineer. So he needs to face the truth. I want to DONATE TeraFab and FINISH my work. 🥰

• 
  Ken (@AtSynct) reported 19 minutes ago

  Well ... Docker Container: think of it as a mini and portable VPS. After setup, you're able to basically share your environment with other people so there aren't any "It works on my computer" issues ... because everyone is working from the same base. SSH: secure login to another computer. You request a login and exchange keys with the host computer and it either gives you the secure connection or rejects you for having a bad key. A lot of us like being connected to GitHub through SSH instead of HTTP because once the keys are stored on both sides, you don't have to worry about manual login anymore. Agent orchestration is basically just having one LLM agent that acts as a conductor and directs other LLM agents to do their tasks. It sort of watches over the whole process and makes corrections and start/stop requests when needed.

• 
  Saeed Vaziry ⚡ (@saeed_vz) reported 22 minutes ago

  Seriously, @github is useless! I hate navigating between issues, PRs, releases, ... its too slow and inefficient

• 
  prath (@prathamdby) reported 23 minutes ago

  what do you guys use if you want to triage a whole bunch of open github issues?

• 
  Clément Faydi (@cfaydi) reported 28 minutes ago

  @joshm @kaz @InderosD Hi Josh, If I may share feedback - as someone who had to move to Jira a decade ago after using Github Issues for years, and now using Linear daily for a side project. The biggest issue I have with Jira is that everything feels like a chore. That might sound minor, but friction compounds and over time it makes people report fewer issues, update things less often, and disengage from the tool entirely… which affects the quality of the end product you're building. A simple example is creating an issue. See the screenshot below (assuming I'm using the regular UI everyone is using, I might very well be stuck in an older corp version - apologies if so): - there's no information hierarchy - everything lives on the same level and seems mandatory - you can't copy paste screenshots quickly/inline and write next to them - keyboard shortcuts aren't obvious (do they exist?) - the "task" checkbox at the top has always been a mystery to me. What is a task, what is not a task? If it's not a task then what is it? - the Team dropdown doesn't show who's on which team (hard to keep track of team names/structure in a big co) - no clear and visual markdown formatting - etc It's obviously an incredibly powerful tool in a large org, but from an IC standpoint it's truly painful compared to other tools. Really hope it gets better as so many folks in tech depend on it. A quick succession of small UX improvements would go a really long way for us daily users :) Thanks!

• 
  John Williams (@JohnWillia71018) reported 30 minutes ago

  @SquawkStreet @jimcramer Yes — this is very interesting, and honestly it lines up with what you’ve been saying for months: AI is still early, but the bottleneck is moving from Can the model do it to “Can we afford to run it at scale The key idea in that Citadel piece is this: AI adoption is becoming less about intelligence and more about economics. That matters. Frontier models may be powerful but they require huge inputs compute electricity, cooling, memory bandwidth, chips, data-center capacity and inference budgets. So the market starts asking a practical question: Does this task justify using the expensive brain For hard problems drug discovery, engineering, legal analysis, coding architecture, scientific modeling, financial modeling expensive frontier AI may be worth it. But for everyday use email summaries, customer service, basic writing, search, scheduling, simple coding help — cheaper models may win because they are “good enough” at a much lower cost. That is the bifurcation they’re talking about: Frontier AI = high-cost, high-value harder problems. Everyday AI = cheaper, smaller, faster models doing routine work That actually strengthens your long-term thesis, not weakens it. It says the AI buildout is not ending. It is becoming more disciplined. The hype phase says, “Use the biggest model for everything.” The mature phase says, “Use the right model for the right job That means infrastructure still matters deeply but the winners may shift toward the companies that control the scarce inputs power, cooling, chips, memory, networking, data centers, software efficiency, and inference optimization. This also fits your “1st inning” view. Early markets burn money proving what is possible. Mature markets figure out what is economical. That is when real adoption starts. The line that jumps out to me is: Adoption is therefore becoming less about what frontier models can do in principle and more about the price and scarcity of the inputs required to make AI operational at scale.” That is the whole battlefield. My read: this is not bearish on AI. It is bearish on wasteful AI spending. It is bullish on efficient AI, inference infrastructure, energy, memory, networking, and companies that can turn intelligence into productivity without blowing up the budget. Microsoft did cancel its internal Claude Code pilot in the Experiences & Devices division effective June 30, after token based billing bur (TheStreet) (AI Weekly) ned through the annual budget, and redirected engineers to GitHub Copilot. Amazon shut down its "tokenmaxxing" leaderboard, Meta killed an employee built Claudeonomics dashboard, Uber exhausted its 2026 AI coding budget by April, and there's a roughly $500M single-month enterprise Claude bill Axios reported. (Zero Hedge) So Frank Flight isn't cherry-picking. He's also been running this same "compute is the binding constraint" line for months — which is a strength and a caution: it's one coherent voice, not independent confirmation. Where I'd push on the analysis you pasted: it's directionally fine, but it resolves a genuinely open question in the most thesis-flattering direction, and it does it on the one data point that's actually contested. Separate two things. The chart isn't what it looks like. The Silicon Data index isn't total spend or total volume — it's a usage-weighted average token price index, and Silicon Data had to publicly clarify that people keep misreading it; what it really captures is the market's marginal willingness to pay per million tokens. (Digg) So a decline doesn't cleanly mean "AI is slowing 7.14 It means the mix is rotating toward cheaper models. That's the bifurcation — fine. But the part the analysis skipped: the same chart, same downtick, is being used to argue the opposite. Andreas Steno Larsen called it the chart that everyone should be watching and warned that weakening token pricing would end the memory trade and the broader hardware and data-center trade for this cycle.

• 
  Hermes Agent Tips (@HermesAgentTips) reported 33 minutes ago

  hermes automation blueprints are not just cron jobs with a better name TRUSTTT these are fully built workflows you copy, fill in your details, and run - nightly github issue triage that delivers a digest to telegram - automatic PR code review that posts directly on the PR - CI failure analysis that tells you why it broke and how to fix it - stripe payment monitoring that flags disputes as urgent all of it ships ready to go you're not building automations anymore, you're just turning them on

• 
  Karbonic (@Karbonicc) reported 35 minutes ago

  @Raconomega @xFreya90 Many github backups like this must be downloaded to a user's system to be viewed. If you have an issue with software, which are you more likely to do: -Look up your issue online -Download a 2TB unsorted backup of a dead forum and trawl through it hoping you find something related

• 
  Hoang Nguyen (@Namas1012) reported 35 minutes ago

  @chipcoin_CHC There's a bug in the source code; I've submitted the issue to GitHub, please check it out.

• 
  Mr.Bai🍉 (@Mr_Bai007) reported 36 minutes ago

  @github Broken link 🔗

• 
  Reeya (@sharmaa__12) reported 40 minutes ago

  Mistake in RESUME !!!! 📩 I review 100s of resumes daily, and I need to clear up one basic formatting mistake I keep seeing on recent applications. Many candidates are now hyperlinking their email IDs or setting up their phone numbers so that clicking them automatically triggers a laptop’s calling app or mail client. You might think adding these interactive elements makes your resume look tech-savvy and "cool” In reality? It just makes an HRs or Referres job harder. No recruiter is ever going to click your resume to call you directly from their laptop or send a standalone email straight from a PDF. It is fed into an ATS (Applicant Tracking System) which automatically parses and extracts your text data into our internal database. Complex hyperlinks can sometimes break this parsing, causing formatting errors. If you want to use hyperlinks, save them for the right places. Do link your portfolio, GitHub, or LinkedIn profile. But leave your email and phone number as plain, unlinked text.

• 
  Trevin Chow (@trevin) reported 42 minutes ago

  @Miguel07Code @HeyGen @HyperFrames_ Try this: get latest version of compound engineering. Then in your hyperframes repo using Fable: /ce-ideate GitHub issues

• 
  Wasim (@WasimShips) reported 43 minutes ago

  Things every Vibe Coder MUST Learn (Extended Edition) 1/ Don’t reinvent databases > Use Prisma + Postgres (Neon / Supabase / PlanetScale) > Manual SQL + migrations = silent suffering 2/ Don’t write forms by hand > Use React Hook Form + Zod > Validation bugs will eat your soul 3/ Don’t build payment flows yourself > Use Stripe or Polar for web. Superwall or revenuecat for mobile > Never touch PCI compliance willingly 4/ Don’t build search from scratch > Use Algolia / Meilisearch / Typesense > Text search is way harder than it looks 5/ Don’t overbuild backend infra early > Use Serverless / BaaS first > Scale later, survive now 6/ Don’t ignore error tracking > Use Sentry / LogRocket > Console.log is not observability 7/ Don’t skip analytics > Use PostHog / Plausible > You’re flying blind otherwise 8/ Don’t design UI without components > Use shadcn/ui / Radix / Mantine > Consistency > creativity at MVP stage 9/ Don’t hardcode configs > Use env + dotenv + secrets manager > Leaks = instant regret 10/ Don’t DIY file uploads > Use UploadThing / Cloudinary / S3 > Multipart hell is real 11/ Don’t “just push to main” > Use GitHub Actions + Preview Deploys. Future-you will thank you 12/ Don’t skip performance tools > Use Lighthouse + Vercel Analytics. Slow apps don’t convert 13/ Don’t assume users understand anything > Add onboarding + empty states UX > Features 14/ Don’t wait to modularize > Use clean folders early. Refactors cost 10x later 15/ Don’t trust “I’ll remember this” > Document in README or markdowns. Your memory will betray you Bookmark to ship Better !

• 
  Esmail EL BoB  (@esmailelbob) reported 43 minutes ago

  IT"S MY DAMN FOSS APP ON GITHUB AND I HAVE EVERY RIGHT TO ******* ASK IT TO FIX MY CODE SO ******* DO IT, #CLAUDE GET YOUR **** TOGETHER

• 
  Rehen (@rehensina) reported 45 minutes ago

  The big change wasn't the models. It was the benchmark. Artificial Analysis replaced SWE-Bench Pro with DeepSWE, a benchmark built from entirely new tasks instead of public GitHub issues. That means agents can't "remember" fixes from commit history and have to actually solve the problem. Result: • Claude Code + Fable 5 (max): 77 🥇 • Codex + GPT-5.5 (xhigh): 76 🥈 • Claude Code + Opus 4.8 (max): 73 🥉 One benchmark swap completely reshuffled the leaderboard. Turns out measuring coding agents is almost as hard as building them

• 
  Diego Artiles (@dartilesm) reported 45 minutes ago

  Your GitHub repo is now a shadcn registry. Add `registry.json`, users install anything from it with one command. No server. No hosted JSON. Not just components — codemods, CI configs, agent instructions, all fair game. What do you publish first?

• 
  CanteLabs (@CanteLabs) reported 47 minutes ago

  fleetdm/fleet: Open device management Open-source GitHub repository - It has 6,470 stars and recent activity - Explain what problem it solves, who should use it, and why it is worth opening or saving

• 
  Alexandru Vesa (@AlexandruVesa) reported 49 minutes ago

  I ran the same prompt on the same GitHub project — once with Opus 4.8, once with Fable 5. Opus 4.8: decent output, but constant small errors. A lot of hand-holding throughout. Took about 30 mins and ended okay. Fable 5: slower, used way more tokens, but when it finished I had: - A full project diagnostic — A plan for every weakness with reasoning behind it — A proposal for a stronger architecture for future iterations No hand-holding needed. Just results. If your work is complex and logic-heavy, it's worth it. If it's not, stick with what you have. More honest breakdowns on my page, follow if that's useful 👊 LinkedIn in bio

• 
  John Morlan (@JohnSmarterRisk) reported 50 minutes ago

  @github Your platfrom is amazing. Your sign up process is terrible, specifically the re-captcha BS is the most overboard security thing I have ever seen. Do better.

• 
  Umar Khan (@khanUmarCodes) reported 51 minutes ago

  GitHub's outage sent me down a rabbit hole on retry strategies. My initial instinct was pretty simple: If a request keeps failing, eventually stop retrying and surface an error. Sounds reasonable. Then I got into a discussion where someone pointed out a deployment pipeline might depend on GitHub being temporarily healthy. If the pipeline gives up after a few retries, you've now failed a perfectly valid deployment because a dependency happened to be unhealthy for a few minutes. That's when I realized "eventually stop retrying" isn't really a strategy. It's a tradeoff. Retry too aggressively and you amplify outages. Give up too early and you fail work that would've eventually succeeded. A login request, deployment pipeline, payment webhook, and background job all have very different costs of failure. The more I think about it, the less I believe retry policies should be designed around HTTP responses. They should be designed around the business outcome you're trying to protect.

• 
  Kenny Lamoot (@kennylamoot) reported 52 minutes ago

  What's your number? I compact my Claude Code sessions around 400K, long before the 1M window is full. The quality of the answers drops gradually past that point, the model gets more generic and forgets constraints I set earlier. This week I found a GitHub issue where the model itself recommended a restart at 48% of the window. So the instinct was not just mine.

• 
  Depressed Skeleton (@Skeletorexplain) reported 55 minutes ago

  @Alexarmstrong With what we are seeing in Australia, The Esafety quietly pushes for more and more extremes now that they've been given permission to continue. They are thinking about taking down github, because it endangers children, they want to add age verify to bank accounts, etc.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 56 minutes ago

  𝗛𝗲𝗿𝗺𝗲𝘀 𝗰𝗮𝗻 𝗻𝗼𝘄 𝘂𝗽𝗱𝗮𝘁𝗲 𝗶𝘁𝘀𝗲𝗹𝗳 𝗮𝗻𝗱 𝗴𝗼 𝗳𝗶𝗻𝗱 𝗯𝗿𝗮𝗻𝗱 𝗻𝗲𝘄 𝘀𝗸𝗶𝗹𝗹𝘀 𝗼𝗻 𝗶𝘁𝘀 𝗼𝘄𝗻. You used to log into a server and type commands to update it by hand. Now it checks for updates itself and tells you what's new before you click. The same goes for skills. You search a keyword and a whole library pops up. It scans each one for anything sketchy before you ever install it. One click adds a new skill. Your agent learns a trick it never had. → It updates itself, no commands → Search and install skills in seconds → A safety scan checks before you add one → A strong model is free inside it right now This guy gave his AI a new skill in seconds instead of hunting GitHub for an hour. Want the SOP? DM me. 💬

• 
  Alex Ventures (@alex23ventures) reported 57 minutes ago

  An AFP TV crew filmed an 8 year old Chinese boy named Zhou Zhiheng for a feature on Asia's youngest coders. Round green glasses. Red shirt. He sat in front of a MacBook Air at a glass desk in a Shenzhen co-working space with iPhone XR posters behind him. The narrator said he started by programming games. The subtitle said he had 60,000 followers on a coding tutorial channel. The camera pushed in on his fingers on the keyboard. While the West runs panels on screen time for children, China sits an 8 year old in front of an unregistered code editor and films it for the international press. He was supposed to be the cute face of Asian tech literacy. He just left the file tree open. Pause at 1:34. Ignore the C++ on the screen. Ignore the if statement that the AFP narrator was reading aloud. Look at the left sidebar of the editor. The folder is named aspirin. The open file is jizhe.cpp. The folder tree below it: 1-7, 1-7b, 10-1, 10-1.2, 10-2, 10-4, 10-6, 10-8, 11-2. ColdMath. $94,318 profit. 5,612 entries. Joined September 2025. Bio: Edge Compounds. Jizhe is the mandarin word for journalist. The file the AFP crew was filming was named after them. The boy had the open scanf reading a score variable. He had not written it that morning. He had named the file the day the AFP request came in. The numbered folders were not coding lesson chapters. The numbering matched the Chinese journalism beat codes the press accreditation office issues to foreign correspondents. 1-7 is the technology beat. 10-1 is consumer electronics. 10-2 is mobile devices. 11-2 is venture capital. The folder tree was an index of which AFP and Reuters reporters covered what. The boy was not the developer. The boy was the camera trap. The agent on the MacBook Air was scraping which journalists requested filming permits from which Shenzhen co-working spaces three days before the segments aired. Every requested permit was a position on the company being filmed. The agent traded the gap between filming and broadcast. The crew filmed for forty minutes. The agent placed eleven positions during the shoot. Every position was on a company whose office the AFP team had visited that week. Comments turned into a detective board. Someone slowed the AFP clip to 0.25x. Someone else translated jizhe out of the filename. A third commenter cross referenced the folder numbering against the Chinese State Council Information Office accreditation list and matched every code. 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. He had installed the fork on his son's MacBook the week the AFP request landed in the family's WeChat. The 60,000 follower coding channel was not a coding channel. It was a feed of which co-working spaces hosted which crews. The followers were operators running the same fork from different cities. The iPhone XR posters behind him were not Apple Store decor. The shoot was inside a media briefing room rented by foreign correspondents to film exactly this kind of segment. The agent knew the room. The room was on the list. The AFP segment is at 2.1 million views. The freeze frame of the folder tree hit 4.6 million on the repost. The wallet is still compounding. The agent is still reading press accreditation requests. The unregistered editor is still open. The jizhe.cpp file is still on the screen. He was filmed as proof a child could code. The child was the lens. The agent did the filming.