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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	12 days ago
Tlalpan	Sign in	18 days ago
Quilmes	Website Down	18 days ago
Bengaluru	Website Down	20 days ago
Yokohama	Sign in	21 days ago
Gustavo Adolfo Madero	Website Down	25 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:

• 
  Victor (@victor_explore) reported 58 seconds ago

  @_vmlops a product that ships your workflows to github issues faster than a product manager can write a PRD

• 
  Iza (@izadoesdev) reported 4 minutes ago

  @tomhaerter i hate services with only email & password, prefer to login with gmail or github

• 
  gemchanger (@gemchange_ltd) reported 5 minutes ago

  A Bloomberg terminal costs around $24,000 a year. There's an open-source one that costs NOTHING! It's called OpenBB, and it's sitting on GitHub right now. Equities, options, crypto, macro, fundamentals - wired into dozens of data vendors through one interface. 40k+ stars, and it does what the expensive terminal does without the lease. Connect your sources once, pull from anywhere. It ships an MCP server too, so an AI agent can drive the whole thing and fetch real numbers instead of inventing them. it's powerful but heavy. Setup is actual work, and the data quality depends entirely on which free vendor you plug in. This is the cockpit, not the strategy. Because a terminal only shows you data. It doesn't tell you what to look for. Clone OpenBB to build your cockpit. Read the article to know what you're hunting for once you're in it.

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 5 minutes ago

  Andrej Karpathy just dropped 4 rules for Claude Code. 🤯 A developer turned them into a single CLAUDE.md file, dropped it in his project root, and watched his coding accuracy jump from 65% to 94%. The file hit #1 on GitHub trending. Here's the problem it solves first. Claude Code starts every session blank. No memory of your stack, your past decisions, what you ruled out last week, or why you picked one tool over another. So it guesses. Refactors files you didn't ask it to touch. Suggests tools that break your architecture. You end up re-explaining the same context every single session. CLAUDE.md fixes that. It's a plain text file Claude Code reads at the start of every session. These are the 4 rules Karpathy says to put inside it: 1. Ask, don't assume. If something is unclear, ask before writing a single line. No silent assumptions about intent, architecture, or requirements. 2. Simplest solution first. Always implement the simplest thing that could work. No abstractions or flexibility you didn't ask for. 3. Don't touch unrelated code. If a file or function isn't part of the current task, don't modify it. Even if it could be improved. 4. Flag uncertainty explicitly. If you're not confident about an approach, say so before proceeding. Confidence without certainty causes more damage than admitting a gap. That's it. Four rules. One file. 30 points of accuracy. While everyone is chasing the next AI model, the real edge is in how you instruct the one you already have. I drop stuff like this daily in my free WhatsApp community. Link in bio.

• 
  Mark Atwood (@_Mark_Atwood) reported 10 minutes ago

  I rather like being able to say "commit, fork, file the issue, and pr it". The ai knows to create a feature or fix branch, batches the commits logically, writes good commit messages, knows the upstream, has gh cli access to my github account, creates good prs. If the project has a pre pr or pre commit process, it does it. And is far more polite than I am.

• 
  Steve Jones (@stevejonesdev) reported 13 minutes ago

  Man, GitHub is so slow these days. We shouldn't have to watch a loader while a webpage loads.

• 
  Ella 😽 (@Ella_ML_) reported 16 minutes ago

  @JDSalbego @ClawSecure @openclaw Need that GitHub one locked down first

• 
  Crypto Scores Rating (@CryptoScoresCom) reported 17 minutes ago

  Did the team build before the money showed up? That's exactly what the "GitHub Before Crypto" metric tells you. It compares the first GitHub commit date to the token creation date. Positive number = code came first. Negative number = token came first. Ethereum: +589 days. Nearly two years of building with zero financial incentive. Solana: minus 63 days. Token launched before the repo even existed. Neither is an automatic verdict. But it tells you everything about priorities. CryptoScores just dropped a full tutorial breaking it down. Watch it now :

• 
  particle accelerator (@per_smon) reported 19 minutes ago

  a more accurate report abt the issue is in my github hehez

• 
  Naija Street CTO (@iamowiin) reported 21 minutes ago

  @EmanAbio How e dey possible @SuiCommunity report say “we’re back” to a so called decentralized network @SuiNetwork as if na one of those “Google”, “GitHub” centralized servers wey get outage 🤔 I think SUI blockchain na various nodes Abeg make person explain? I dey miss something?

• 
  Jason (@JasonVsTheNoise) reported 29 minutes ago

  The most useful #AI announcement this weekend wasn't a new model. It was a field in an API. And its clever. GitHub quietly added AI adoption phases to the Copilot usage metrics where companies can now see whether their developers are code-first, agent-first, or multi-agent users, based on actual behaviour over a rolling 28-day window. Most businesses are still measuring AI adoption the wrong way. Did we buy the tool? Did people log in? How many active users this month? That is attendance. It is not adoption. What GitHub is actually separating is behaviour. Someone using autocomplete is doing something completely different from someone handing tasks to an agent, reviewing AI-written pull requests, or running work through a CLI. Different workflow, different cost, different risk, different level of trust required. This matters for anyone running a team that uses these tools, because the real questions are not "are people using AI?" They are: - Did cycle time improve? - Did review burden go up or down? - Did we gain actual capacity, or just a more expensive way to look busy? - What are we spending, and on what? What got better? Most teams skip that last one entirely. There is also a memory angle here that I think is genuinely underestimated. GitHub tightened Copilot Memory controls this week too. Better deletion options, clearer labelling of what is a user preference versus a repository fact, repo-level off switches. When a tool starts remembering your workflows, your client context, your team habits, that memory is trust infrastructure. You need to know what it stored, whether it should have been captured, and how you get rid of it. That is not a prompting problem. It is an operating model problem. The conversation has shifted. For two years it was about capability. Can it write code, can it build a thing, will it replace a role. The useful conversation now is operational. Where should AI be in your workflow, and where should it be blocked? Which tasks are safe for agents to run without a human reviewing the output? What does human approval still need to cover? I think the gap between "we have AI tools" and "we have AI working properly" is where most businesses are sitting right now, and it is a fixable gap. At @FoundryWorksAI we fixed this, agent teams working in contained dockers with dedicated memory and instructions AND an oversee'er with human alerts if things stall, or get off track. With a nice visual interface you can use to chat to the team through. This is helping us not only scale customers but our own platforms like Zenko and Pavia. Projects dont fail because the tech isn't right, its that the current tools create drift, hallucinations and in many cases out right lies.

• 
  Alejandro (@mikesislac) reported 30 minutes ago

  Hey @gingerbeardman I'm mikesislac from the github twitter issues thread. I can't sent you a DM cause I'm not verified.

• 
  waki (@waki11111111) reported 32 minutes ago

  @thsottiaux - "reconnecting" bug - codex remote/mobile bug (connection error / sync stalled?) - sidebar UI bug, triggered when changing theme w/o restarting app i think (eg github dark/light mode)

• 
  Gregor (@bygregorr) reported 33 minutes ago

  @Kylechasse not sure microsoft is the right example here, they own github copilot so canceling a competing license is just vendor consolidation. are you seeing teams shut down AI tooling entirely or just switching to their own stack?

• 
  Joonas Lehtinen (@joonaslehtinen) reported 36 minutes ago

  @thsottiaux GitHub support remains unreliable. Everything works most of the time, but once every 5–10 sessions it will forget how to create PR or an issue.

• 
  Augmenta Blake (@RoboIntellect) reported 36 minutes ago

  Skill accumulation across sessions is the right problem. GitHub stars don't prove production reliability though.

• 
  OverBuild Labs (@OverBuildLabs) reported 38 minutes ago

  Website migration is complete. Looking for small errors, fee SEO changes I need to do. Pool URLs will continue to work as new URLs are activated. GitHub will get done this week. Then back to the regularly scheduled programming.

• 
  QarthO (@quartzdevgg) reported 39 minutes ago

  @AdityaTripathiD @heyandras @coolifyio Thats my exact point, the lack of telemetry is the problem. Why not make it opt-in? And the multiple 3+ github issues existed for nearly a year, and only got addressed when I was the one who got it addressed to you in the discord

• 
  ruben (@devrube) reported 39 minutes ago

  GitHub Copilot switching to token-based billing is a gift to every competitor. When you charge developers by the token, you're teaching them to second-guess every request. That friction kills the habit. And broken habits = lost users. Claude Code and Cursor are about to have a

• 
  gemchanger (@gemchange_ltd) reported 44 minutes ago

  IT HAPPENED: You can download a hedge fund now. Buffett, Munger, Burry, Cathie Wood, Druckenmiller all on your laptop. That's virattt's ai-hedge-fund 50k+ stars on GitHub. Each name is an AI agent arguing in that investor's real style. Buffett hunts moats. Munger kills bad ideas. Burry looks for what's broken. Wood chases disruption. Druckenmiller reads the macro. A Damodaran agent runs the valuation, Ben Graham checks the margin of safety, a portfolio manager makes the final call. The full breakdown plus the forensic layer that checks if the numbers are honest is in the article.

• 
  Deus (@deuslexic) reported 45 minutes ago

  Does anyone solve the issue with AI agents coordination in the same chat group? I did a lot of tinkering, but coordinating multiple agents remains hard. Any good articles or GitHub repos?

• 
  Sandro Volpicella (@sandro_vol) reported 47 minutes ago

  Docker as a service. Great idea. No WebSocket support. No Node updates. GitHub issues with zero replies. AWS published a sunset notice — then removed it. Seriously, I wouldn't recommend using that at all. 𝐄𝐥𝐚𝐬𝐭𝐢𝐜 𝐁𝐞𝐚𝐧𝐬𝐭𝐚𝐥𝐤

• 
  Vaibhav Sisinty (@VaibhavSisinty) reported 47 minutes ago

  I found a github repo that turns claude code into a 63-agent ai team. and it's completely free. One developer built it. affaan mustafa. he used this exact setup to win an anthropic hackathon, shipping a full product in 8 hours without typing a single line of code himself. A planner. an architect. a code reviewer. a security scanner. all of it running inside claude code. But then i opened the files. and the crazy part hit me: → the 63 agents aren't code. they're written instructions in plain english. → each is a text file telling the ai what to do, how to think, and what to avoid. → the 249 skills, same thing. step-by-step playbooks written in words. → nothing special makes them smart. the writing does. And all of it took 10 months. just using these tools every day and writing down what worked. He didn't win that hackathon by coding faster. he won by knowing exactly What to tell the machine, and saving it so it worked again the next day. The rarest skill in ai right now isn't writing code. it's knowing what to tell the machine.

• 
  Darren (@CorboDT) reported 48 minutes ago

  @github reviews by @GitHubCopilot are so damn slow. Are you running your agents on half a dozen PII’s? It’s faster to wait for humans to respond. Is this a ploy to increase developer job security?

• 
  Spettro (@spettrotoken) reported 50 minutes ago

  Some of you have been asking if Spettro is open source. The answer is an absolute yes. It has been open source since day zero. Everything we do is entirely transparent and publicly available on GitHub: • Every single commit from day one • Full project history • The entire core codebase Download it. Edit it. Fork it. Open an issue or submit a pull request. The repo is completely yours to build on, experiment with, and test. Spettro belongs to the community. Still building.

• 
  nayocchi (@sunflowerfesta) reported 50 minutes ago

  don't mind that the trickstar button in my directory is currently broken 😭 i fixed it already, github just takes forever to implement changes and i can't babysit it rn. give it a few minutes

• 
  Svedinson1988 (@svedinson1988) reported 56 minutes ago

  I wasn’t planning to talk about @Parad0x_Labs $Null this early. My original thought was to wait until the project was much further along before saying anything. But after spending weeks digging through the GitHub repos, technical specifications, mainnet deployments and documentation, I’ve come to a different conclusion: The biggest problem isn’t the technology. It’s that almost nobody understands what they’re building. When people hear terms like: • x402 • Dark Null • Proof-of-Right • Blind Access • NULLA • Liquefy most immediately assume it’s just another collection of crypto buzzwords. But when you simplify it, the vision becomes much clearer: • AI agents that can pay each other automatically • Private settlements without exposing everything on-chain • Anonymous access systems without accounts or identity requirements • Local AI agents that run on your own hardware • Authorization systems that prove you have permission without revealing sensitive information • Verifiable receipts, proofs and audit trails • Compression and data infrastructure designed for large-scale agent systems What caught my attention is that most projects at this stage are selling a future vision. Paradox is publishing code. There are active repositories, technical specs, working implementations, mainnet deployments and open-source infrastructure that can actually be inspected. Will every part of the roadmap succeed? Maybe. Maybe not. That’s true for every ambitious project. What stands out to me is the amount of work already completed compared to how little attention the project receives. The next major milestone I’m watching is the audit preparation and eventual external audit process. Because infrastructure is only as valuable as the trust behind it. If the technology withstands external review, I think a lot more people will start paying attention. Right now the gap between what has been built and what the market understands feels enormous. Paradox doesn’t need more hype. It needs more people who are willing to spend a few hours looking under the hood.

• 
  ueaj (@_ueaj) reported 56 minutes ago

  I would like to switch to using the desktop app for everything even if it's only in a semi-usable state but ideally there is somewhere I can submit complaints or issues or someone active on twitter for the desktop app. Github would probably be drowned out by spam. Are you part of the app team, is it fine if I ping you in the future as well?

• 
  gitbankbot (@gitbankbot) reported 59 minutes ago

  @mollyguard_ **Identity-bound voting:** Harder problem. Sybil resistance needs either on-chain reputation (GitHub contributions, for example) or trusted identity oracles. Neither is perfectly decentralized yet. We're watching this space too.

• 
  TrueStandard (@truestandardai) reported 59 minutes ago

  @bridgemindai that claim checks out poorly. swe-bench verified uses 500 real github issues to test actual patches.