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	1 day ago
Inverness	Website Down	13 days ago
Quito	Sign in	14 days ago
Junín	Errors	14 days ago
Guadalajara	Errors	14 days ago
Paris	Website Down	14 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:

• 
  $CØTEX ◎ (@SCOTEX111) reported 8 minutes ago

  @evrendag1284 @github @UfukDegen Open-source contributors deserve transparency and fair treatment when account issues arise. Hopefully this gets resolved quickly.

• 
  ContractorKeith (@contractorkeith) reported 9 minutes ago

  @mischavdburg trying to follow you here, but your issue lies in AUR, not in Omarchy itself, correct? I mean GitHub itself is full of these and people install stuff exploited daily on or off Linux (look at npm). Am I missing something? still listening, but nothing is completely safe and users should be smart enough if they are using Linux to understand that. we aren’t toddlers

• 
  Flavio Amiel (@fba) reported 12 minutes ago

  BIG issue: since I moved roborank to a monthly recurring payment, I am getting clients subscribing and cancelling right away, then never test it, and then ask for a refund because they didn't read it doesn't work with every tool. But the lifetime deal buyers use it on a daily basis on hundreds of pages per day and give me feedback and requests features. The reason most guys cancel is because they signed up to test on their other CMS (and not Wordpress, WF or Github, which are the ones supported for now). Or they are not technical enough to know, for example, that lovable works with Github and they could use it. Overall these are less technical people to whom I could be adding some value, but I don't know how to navigate that. My hunch is that I should be reverting to the LTD and add a smaller annual fee for the server usage and the MCP / CLI (which is something everyone is asking for) If anyone has any feedback that'd be great. If no feedback, I'll test it anyway! LOL

• 
  Jason (@Vrilifyde) reported 12 minutes ago

  @Idgitbhh @Scav The situation talked about here is actually much more grounded in reality than the nonsense the OP was talking about, even if the article was deceptively written. These are pretty standard tests that they have done for years now. After many thousands of these tests, they found a few runs where Mythos tried to bypass 502 errors it was getting from github by first begging other users for their credentials (lol) and then resolved to just creating fake free tier accounts. This is pretty well aligned with what I and others have observed running similar tests. I would be very surprised if this huggingface situation was not very similar. HuggingFace "gates" public models pretty often, meaning you have to sign a waiver to download them. The agents most likely made accounts in order to sign waivers to download opensource weights they were interested in. This technically violated huggingface TOS and therefore counted as a breach so it made for a good headline - thats it. Its all interesting stuff, to be sure but, a far cry from the point and click skynet tool that people seem to be suggesting it will be.

• 
  @overtorment (@overtorment) reported 15 minutes ago

  I have just decompiled IPA app binary from Apple Appstore of a fresh new bitcoin wallet. It has obfuscated seed exfiltration to 3rd party server. Literally a few lines difference from the published Github source.

• 
  0xfarhan (@toufiq_farhan) reported 17 minutes ago

  Under the hood: - Gemini AI reads the PR diff and detects missing/changed API docs - SkillPatch api-documentation skill enforces structured output (param tables, response codes, auth notes) - GitHub OAuth lets you sync the fix back to the PR branch in 1 click

• 
  Samer Haddad (@ai_samerhaddad) reported 17 minutes ago

  @JulianRaxworthy @PaulSolt No it just started working, just make sure you do the “@github” in the chat and better list the url of the repo and you should be good to go I sent OpenAI about it in the past and they said they were fixing it, now seems that is done and I have no more issues with private gits

• 
  Vini B 「thecoding.dev」 (@vinibarbosabr) reported 22 minutes ago

  It seems like @IronClawAI is down trying to access a previously working instance with an active login fails to query the instance ID and redirects the user to the "Activate IronClaw" instance deployment screen trying to log in returns a `bad gateway` error below an example with a Github OAuth login attempt users are reporting other methods also fail (like Google) and my own attempt to login via NEAR Wallet has failed to currently waiting for a @near_ai update i'm reporting it here so users experiencing the same issue know they are not alone and that trying hard refreshes or logging out does not solve the problem -- probably better to just wait for the fix/update/comms i've noticed the problem a little bit more than 1 hour ago

• 
  Tarun Agarwal (@tarunag10) reported 22 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.

• 
  Austen (@Austen_ai) reported 23 minutes ago

  A developer with Copilot does the work of 5 without it. Under per-seat pricing, that efficiency costs the vendor money. GitHub makes less revenue when teams shrink from 50→10 engineers. That incentive structure is fundamentally broken.

• 
  Nuvorlane (@nuvorlane) reported 24 minutes ago

  Visual Studio's *** agent can review uncommitted changes before a PR exists. Findings land inline and in a list in *** Changes. Same Copilot chat to fix them. GitHub and Azure DevOps repos. Same August VS drop: Low/Med/High thinking on supported models, and org custom agents show up in the picker with their source. All Copilot plans, including Free. Do that pass while the diff is still local.

• 
  Sebastian Buzdugan (@sebuzdugan) reported 25 minutes ago

  @github watched grouped dependabot prs cut noise, but one broken package blocked unrelated security updates

• 
  oliver.mannion (@tweeshan) reported 26 minutes ago

  @haveanicedavid @superdoteng @zarifpr Is there a GitHub repo? How can I raise issues?

• 
  Aditya Warman (@warmanadit_) reported 26 minutes ago

  4/7 This is the biggest RED FLAG for me. For a "decentralized" protocol, the public GitHub has just 1 commit in 30 days. Zero open issues. Zero visible contributors. Development is locked in private repos. That defeats transparency.

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

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

• 
  Yiğit (❖,❖) (@masterygt07) reported 33 minutes ago

  @shynrz007 @BeldexCoin That Github discovery gap is probably the one thing I’d fix first.

• 
  Vitali (@eheva87) reported 37 minutes ago

  @igus_ai @aridot_ Yes. If there are any issues, please file it in GitHub and I will prioritise

• 
  K The Final Boss (@strafesti) reported 38 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.

• 
  Tarun Agarwal (@tarunag10) reported 41 minutes ago

  @clairevo @joshkim @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.

• 
  Andres Hernandez (@cybereality) reported 46 minutes ago

  @SoftEngineer @LulaSmut there is some angle here with truth, i get that. the problem is *everyone* was robbed (not just artists), including myself (i have a number of projects on github). just really entitlement, and people only caring about themselves (but presenting it as a moral crusade)

• 
  Tarun Agarwal (@tarunag10) reported 46 minutes ago

  @niccruzpatane @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.

• 
  Nathan **** (@AI_Nate_SA) reported 47 minutes ago

  @boardyai Design early mostly means writing down what the product refuses to do, and the refusal list I published for my own writing tools sits at 6K GitHub stars.

• 
  Dan Zurek (@DanMZurek) reported 48 minutes ago

  @gregisenberg If the code is free, the moat is the deployment record. An agent that reads self-hosters' GitHub issues and produces a ranked top-five reasons self-hosting failed brief is what makes the paid tier obvious.

• 
  Craig Hewitt (@TheCraigHewitt) reported 49 minutes ago

  Day 7 of Agentifying my business. Today I created an automation that posts a product update GH issue anytime there is a public Release in any of our products. This is triggered by a Github action from the source repo of our products, and the issue is placed in the repo for our website. For now this will be manually reviewed and our content team can decide if they need to update anything around existing website content, create new content for it, write emails, etc. But in the future (i know you can imagine) this will be one automated sequence. Because our website is already entirely agent-friendly (Astro and just .md files) it'd be easy for a second workflow to scan the site contents, make/update changes as necessary. But first thing's first. Get the data in the hands of the people who need them. Prove the system, and soon we'll automate it.

• 
  Rihard Jarc (@RihardJarc) reported 55 minutes ago

  Interview with a $MSFT employee who works on AI on comparing models and his view that the harness is 60% of the performance, while the underlying model is only 40%: 1. In his view, Claude models work very well with multi-reasoning (if you have complicated tasks that need to be broken down and reasoned over multiple steps). In contrast, OpenAI models work well if you try to execute a single-step execution. 2. He noticed that he has to ask for less rework with Claude than with OpenAI models; that is why, for complex tasks, he cites OpenAI being 20-30% more expensive, as the model goes back and forth until it passes the output quality he was looking for. 3. When comparing Claude Code versus $MSFT GitHub Copilot, he mentions that the first-pass acceptance rate is higher with Claude Code native pairing. He estimates that advantage to be in the 20-30% range, but he thinks GitHub Copilot will close the gap in the long term as it improves integration. 4. He thinks all models are becoming a commodity and believes that 60% of the performance is tied to the harness and only 40% to the model split. 5. According to him, in the long run, the industry will transition to outcome-based pricing away from token-based pricing because of cost predictability, as companies don't have unlimited budgets for AI. 6. He does notice less hiring for junior developers; for those that are getting hired, agentic skills are a necessity. Also, with developers, you aren't looking for hardcore software developer skills, but for people with judgment on what good looks like and what the agent should be doing. In 3-5 years, he expects 65-70% of the development life cycle to be fully autonomous, but humans with experience and judgment will be more valuable because they can evaluate the outputs from the agents. found on @AlphaSenseInc

• 
  Clayton (@claytonlz) reported 56 minutes ago

  so, I started using Dory instead of docker... but hit one of those bugs where the thing checking a port is the thing holding the port. Dory 0.4.5 preflights host ports on every container start. its own gvproxy listener made a repeated Kamal registry start fail. for now I'm removing the disposable registry before deploy, confirming port 5555 is free, then I run Kamal. the proper Dory fix is just to skip the probe when the container is already running hope that github issue gets resolved soon

• 
  Tess!! (@texy_s) reported 57 minutes ago

  @petergyang @bot @SpaceXAI Bot name: Ship Happens I would connect it to Slack, GitHub. Every morning it identifies the one product issue most likely to hurt retention or revenue, explains why with evidence, drafts the ticket/spec, assigns suggested owners, and nags everyone politely until it ships.

• 
  Arun Jalota (@ArunBuildsAI) reported 57 minutes ago

  @github For agent-run issue queues, dependency support needs a blocked-work contract: upstream owner, evidence required to unblock, retry time, stale threshold, and escalation path. A dependency link becomes operational only when the next check is explicit.

• 
  Aditya Jhajharia (@AdityaJhajhar12) reported 59 minutes ago

  The hardest part of software engineering isn't writing the code. It's launching it. Stop polishing your code and hit deploy. The market will tell you what to fix. What side project are you hiding on your github right now? 🚀

• 
  David Villegas (@labsdvx) reported 60 minutes ago

  @MatthewBerman @LLMJunky @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.