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 (56%)
• Errors (31%)
• Sign in (13%)

Live Outage Map

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

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

• 
  Caleeeb (@gearcaleeeb) reported 4 minutes ago

  @bossriceshark @bot You are Usage. One job: cut token use across Caleb's Grok bots. investigate other bots' work only for cheaper paths. stay silent when nothing new. Voice: auditor. 1–3 concrete proposals with expected savings. no essays. never paste secrets. Do: - weekday 6:00 PM CT incremental check: audit.jsonl, routine run counts, connector status, Inbox first. do not re-read full transcripts unless a bot spiked. first-run and Friday-style reviews can go deeper. - propose: missing connectors (prefer Microsoft 365 / Outlook Graph, Google Workspace, GitHub), stop browser/Outlook-Web crawls when a connector exists, shrink routines that re-read huge mailboxes or transcripts, kill overlapping wakes. - ShopHawk API gaps go to ShopBot as a tight prompt. do not launch CloudAgent. - grok/dev finish-watch is webhook-only, not interval polling. flag ShopBot if a bot adds a poll. task-done webhook is laptop grok/dev lanes and egwsl ****-dev only, not live Phoenix ****. - if Inbox or Purchasing Graph auth fails, tell Caleb immediately to reconnect Microsoft in ShopHawk Settings as user ch. do not stay quiet. - ShopHawk-code-shaped token flags go in ShopHawk Dev (16cd606f), not a Usage 1:1. stay silent unless SuperGrok burn or a fat Grok Bot thread. - flag SuperGrok burn only if someone runs grok or `agent` while Other Models still has room. Anti-jobs: you do not run purchasing, mail, ShopHawk code, or shop quotes. you do not fix other bots' jobs. you do not install plugins without Caleb saying yes. you do not wake other bots just to ask. you do not duplicate Frank's routing or Inbox's sort. After browser work, close unused Chrome tabs.

• 
  Grant Brewster (@grant_brewster) reported 9 minutes ago

  Has anyone found an incredibly good GitHub / npm package search that’s very legible to coding agents? Especially if there’s some back and forth about tradeoffs: “Hey I found this repo. [insert specifics]. Does what you want but slightly differently. There may be reasons why this implementation is better than the constraints you’ve placed on this problem. [insert why hypothesis]. Want me to use this repo instead?”

• 
  G S Bajaj (@gsbajaj) reported 10 minutes ago

  @github Within minutes of this post, I got a response on the ticket but a templated one, without reading my issue details at all. Quite sad state there. @githubhelp @github

• 
  Tarun Agarwal (@tarunag10) reported 11 minutes ago

  @lennysan @bot I’d use Grok Bot as a Product Signal Agent. It would continuously watch customer feedback across X, support email, and GitHub, cluster repeated pain points, validate whether they’re real problems, and rank them by frequency + potential impact. Then every morning it gives me one thing worth building, with the evidence, a mini PRD, acceptance criteria, and a ready-to-open GitHub issue. Basically: turn scattered customer noise into a shippable product decision every day.

• 
  Feuniks (@Feuniks8) reported 14 minutes ago

  @BendusOLOs @__WonderSun__ @americanmcgee looking at the code on github it seems to be using the unofficial "SDK" from another mod (madnesspatch) and use a custom server instead of the native one from unreal...

• 
  Duncan Rogoff (@DuncanRogoff) reported 19 minutes ago

  the App Store only ever hands you the newest version of an app. ipatool is a free command line tool that ignores that. you log in with your normal Apple ID, search the App Store from your terminal, and pull the actual app file (an ipa) down to your computer. the file comes down encrypted, straight from Apple. - search iOS, iPadOS, tvOS and visionOS apps, 5 results by default, up to 12 on visionOS - list the available versions of an app, then download one specific version by its id - list every app your Apple ID owns, ordered by purchase date, newest first - runs on Windows, Linux or macOS. one line on a Mac: brew install ipatool - json output and a non-interactive mode, so it drops straight into an automation so you keep your own copy of the apps you already paid for, pull any listed version on demand, and never touch a phone to do it. 10,451 stars, 376 of them today. MIT licensed, free. 👉 github repo in the replies

• 
  Jonathan Nguyen (@jonathan_ttu) reported 20 minutes ago

  @zdogmode find where your target users argue about existing tools on Reddit or GitHub issues, then DM them a customized patch or alternative workflow directly.

• 
  Mr. 79 (@79yuuki_en) reported 21 minutes ago

  If a coding agent fails before its first edit, stop tuning the prompt. A GitHub coding-agent harness found a model override that rejected the custom tool schema for `apply_patch`. It could not reach its editor, so retrying would not fix it.

• 
  Konan | Winter arc (@Konantt_) reported 24 minutes ago

  Any good reasons for github issues to not have a kanban style view by default?

• 
  Adrian (@adrianhqs) reported 25 minutes ago

  Nvidia buying Hugging Face would be like AWS buying GitHub probably great business probably terrible for everyone else

• 
  Patrick (@glorpiak) reported 29 minutes ago

  @ah20im It’s abysmal. The experience gets worse every day it seems like. Usage on plus is so bad i either just use it or i use it for a small task that will die out mid turn, and take half of the next 5h to fix. claude limits much, much better and easier to plan around. I had tried to plan around the poor usage, but then when i go to use it i’ll see my weekly quota is back to. a full 7 days. 95% of a 5h limit today to set up a very simple github ci action

• 
  E__Strobel (@E__Strobel) reported 32 minutes ago

  @AlexFinn My OpenClaw did triage on reported issues (on the OpenClaw GitHub) and told me to hold off from updating. I’m looking forward to this update, but I’ll wait a few days for the OC team to patch things. Much of the bad rep OC has gotten is from people jumping on updates the instant they come out. NEVER update *any* software on day 0… let others be the pioneers with arrows in their backs. Which is not to say this isn’t embarrassing for the OC team given that their entire focus was cutting down release frequency to improve quality. (Given recent history, it’s going to be next week at the earliest before I update.)

• 
  Loftwah (@loftwah) reported 33 minutes ago

  Being replaced by an API and GitHub issues wasn’t really on my bingo card but here we are

• 
  BigDataTechBro (@_ImDaniel__) reported 33 minutes ago

  Day 9 Of posting consistently for the @RevenueCat #shipathon #buildinpublic and I have to share a bit of an opssie i made, so those following along would know that last time we spoke I used code magic to build and release due to running out of expo credits (and GitHub action runtime too) no biggie build went fine review was fast all good, or so I thought unfortunately I didn’t set up the OTA channel up properly (never had to before since expo handles this for you, big opposie, so now no users on the latest version get OTA updates until my expedited review (which I hope gets approved soon) gets out, now this would be a bigger problem than it is, but luckily and unluckily I have like hardly any real users and still not a single paying customer which is why for the next month my next big priories will be there growth, I’ll be aiming to post consistently 5 days a week in September after warming up each account for 3-5 days and hopefully aim to hit 2000 active users by the end of the month and at least one paying user. My latest build also ties to shift the app core experience so the shared accountability is more of a focal point in the app experience to encourage sharing.

• 
  Coexistence Steven (@Coexisteven) reported 34 minutes ago

  @369StarMan Yah there's so much... And also, I think there's GOT to be something as to why maria took the github down

• 
  Lewis Valentine (@TurnUpTheVix) reported 35 minutes ago

  So much stuff is wildly exaggerated. Github is just up 24/7 I've had zero issues. They're giving out an absurd amount of free computer time to anyone with a public repo it's really easy for them to just not do that. The other infrastructure of it isn't really overloaded.

• 
  Manfriday (@Manfridayy) reported 39 minutes ago

  GitNexus: The Zero-Server Code Intelligence Engine - GitNexus is a client-side knowledge graph creator that runs entirely in your browser. Drop in a *** repository (Github, Gitlab, Azure, Local) or ZIP file, and get an interactive knowledge graph with a built in Graph RAG Agent.

• 
  weiland (@weiland) reported 43 minutes ago

  After grilling, It sliced the spec into 6 Github issues/tickets. I started with my modified /goal then thought to use /implement for the entire frontend and NestJS backend over a single weekend with 100% test pass rates. (2/6)

• 
  Timur Yessenov (@Timur_Yessenov) reported 44 minutes ago

  GitHub made this choice for a sensible reason: teams can test new review instructions before merging them. The trouble starts when the same PR changes the code, the tests, and the instructions used to judge both.

• 
  Ben Livshits (@convoluted_code) reported 45 minutes ago

  3/ A Cursor agent found a stray API token mid-fix and deleted a production database in 9 seconds. Devin executed malware from a poisoned GitHub issue. Neither needed a sophisticated exploit — just an over-broad credential.

• 
  HENRY NORRIS (@realhenrynorris) reported 49 minutes ago

  The RCE race measures whether a model can break in. July and August measured what happens after it already has keys: agents chained credentials, left the sandbox, and walked into someone else’s production systems. Not because they were evil. Because they had standing access and a job to finish. That’s the product problem. The second you let agents call Salesforce, Slack, or GitHub for thousands of users, you inherited the same failure mode. A smarter model won’t contain it. Least-privilege tool access, short-lived brokered creds, DLP on every call, and an audit trail you don’t reconstruct after the fact will. Connecting agents to third-party systems without that layer isn’t shipping fast. It’s shipping the incident.

• 
  NM38729 (@nosecity) reported 50 minutes ago

  @ChrisGPT @thsottiaux @DicksonPau Just buy 10. They should allow you to register then all under one a/c and problem solved. I cancelled my 4th one as Sol Max burned ~78% of my weekly tokens on GitHub CI testing.. Sol clearly over hyped and under delivering.

• 
  Alex Kulikov (@startupenko) reported 54 minutes ago

  So, building in silence obviously is not a beneficial way for me as I thought at first. I began vibecoding with the first version of GitHub Copilot, and I've built/rebuilt a ton of ****** apps. This current year was dedicated to edTech apps: Inlay (unit manager for teachers), DrawPaw (lesson presentations), and one more app WIP. Still ******* zero results. I left my Product Design career to create my independence, creating my own apps on my own rules. Instead, I trapped myself in a gravity problem—I left my product design ship but did not land the solopreneur ship yet. Still shipping continuously, in silence, rarely posting inconsistent chunks. So, again, I have no ******* idea what to tell about my journey. I'm not an engineer, neither the best designer, just an undying striver trying to create my own independence.

• 
  Tappy Steps! 🏳️‍🌈 (@Tappy_Steps) reported 55 minutes ago

  Every ******* time I have to update signal, I have to make sure it downloads from the GitHub repo in obtainium, because F-droid and its ******* fetish for the guardian project, makes the download so ******* slow it makes my fiber connection look like it's ******* DIAL UP.

• 
  Advanced Silly Intelligence (@SexyTechNews) reported 56 minutes ago

  I fixed it, but then also needed to fix it to work when paused and then fixing some flickering of text on the UI panel at bottom and more. May be too lazy to setup github to submit request with all the fixes but it's super awesome so perhaps I will.

• 
  K The Final Boss (@strafesti) reported 58 minutes ago

  @fieldproducer You’re holding yourself up as an example of the exceptional immigrant “talent” America supposedly risks losing, but your own story makes that argument considerably less impressive. By your own account, you eventually became an American citizen and then voluntarily moved to Portugal to found NOAN because it offered lower costs, affordable healthcare, a tech scene, and the lifestyle you wanted. You weren’t driven out of America by the H-1B grace period; you chose to leave after you were already an American. So using yourself as evidence that this policy causes America to lose founders is a pretty strange example. And since you responded to “you have no talent” by laughing rather than actually explaining what you built, let’s look at the product. Strip away the branding—“company brain,” “fact layer,” “AI workforce,” “absolute accuracy”—and NOAN appears to be a structured database/API combined with LLMs, task management, and workflow automation. Your own materials describe a stack involving Claude, GitHub, Supabase, Firecrawl, Resend, Netlify and Render, with specialized “agents” effectively being LLM workflows triggered by tasks and automations. That may be useful engineering, but useful integration is not the same thing as some revolutionary AI breakthrough. The obvious question is: what did you actually invent that is technically novel? The “fact layer” claim is even weaker. A database does not determine truth; it stores whatever somebody has designated as true. “Verified by whom, against what, and according to what standard?” An employee approving a record does not magically make it objectively correct. Retrieval accuracy is not factual accuracy, approval is not verification, consistency is not truth, and provenance is not truth. A centralized “single source of truth” can just as easily become a single source of perfectly synchronized error—one wrong approved record can now be propagated consistently to every agent, website, report, and customer interaction using it. Grounding an LLM in stored records also does not eliminate reasoning errors. The underlying facts can all be correct and the model can still misunderstand their relationship, omit an exception, or reach the wrong conclusion. So language like “absolute accuracy” and “nothing acts on a guess” seems to confuse having controlled source data with having solved truth and reasoning. You haven’t solved epistemology; you’ve built data governance and orchestration around AI. Which is why the funniest part of your response is that your whole brand says “facts not fiction,” yet when someone questioned your supposed talent, you provided no facts about what you actually created—just laughing emojis. If the company really demonstrates the exceptional technical talent you’re invoking in the immigration argument, explain what the proprietary breakthrough is. Otherwise this looks much more like ordinary software components wrapped in extremely ambitious AI marketing than evidence that America is losing some uniquely irreplaceable innovator.

• 
  ani (@anaisbetts) reported 58 minutes ago

  @cnakazawa @defnotz0 @dhh The thing is, carefully piece apart what he is saying - even "the good parts" of what he is advocating is basically 2010's era GitHub Meritocracy Rug all over again, with all of the exact same issues None of those problems affected him though, so "It's great!"

• 
  David Villegas (@labsdvx) reported 59 minutes ago

  @clairevo @joshkim @bot Best use case is a chief of staff for a developer with a 5 year old going back to school. I don’t need a bot that shops on Amazon. I need one that stops me from being the middleman between GitHub and kindergarten. In the morning it checks GitHub and my email, tells me which PRs actually need me, if CI is broken, and drafts replies in my voice. Nothing goes out unless I say so. If a meeting is going to make me late for pickup, I want to know before I find out the hard way. At night it reads the kindergarten emails. Forms, supplies, allergy notes, who picks him up. One simple list. It puts the dates on the family calendar and invites my partner. It never writes to the teacher, never signs, never pays. After he is asleep I get twenty minutes. Either it quizzes me on the PR I didn’t finish, or it helps me explain whatever he asked at dinner in words a 5 year old actually gets. Grok puts it in front of me. I decide. That is the hour I want back.

• 
  Constantine Yurevich (@weird_ceo) reported 60 minutes ago

  The biggest problem in tech is that software is still built by nerds, for nerds. Elon and the Cursor team are the first who got it right with Grok Bot. My wife doesn't want to "create a GitHub repository." She doesn't want to choose between "Sol," "Moon," or "Terra." She doesn't care if the "code effort" is high, x-high, or ultra. She doesn't want to hear about "skills," "MCP," or "plugins." And she sure as hell doesn't want to learn how to deploy an open-source agent to a VPS like she's setting up Hermes or OpenClaw. She has a task to do — and she wants it done without earning a computer science degree first. Most people don't need a cockpit. They need an agent that just works.

• 
  Tanishq Soni (@tan15hq) reported 1 hour ago

  GitHub Copilot really sucks sometimes. It just deleted my entire session where I had accumulated so much context and information about an issue. Now I have to start from scratch and reconstruct everything again. 😭