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 (58%)
• Errors (32%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Haarlem	Sign in	1 day ago
Villemomble	Website Down	1 day ago
Bordeaux	Website Down	5 days ago
Ingolstadt	Errors	9 days ago
Paris	Website Down	10 days ago
Berlin	Website Down	11 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:

• 
  Sergio Donato (@pitumpa) reported 1 minute ago

  @OpenAIDevs Yes, but please fix the CPU usage spikes in Codex Help (Renderer) when working in a folder without a .*** directory. Please take a look at the issues on GitHub. Right now, Codex is almost unusable on MacBooks. It makes them overheat badly.

• 
  Thomas Malloc (@ThomasMalloc) reported 5 minutes ago

  @zeddotdev I would absolutely use this for my main editor, but ACP issues exist when using with WSL2. Github issues says it might be Bash PS1 related. I'll give it a try and see if I can fix. Looking nice. 👍

• 
  Amy11 (@Amy11621) reported 13 minutes ago

  @Microsoft have some issues here too. My developers try to use better models in @github copilot and get messages that they are overhelmed and can’t respond. Come on. I get your pricing is not at Claude’s but my devs only know they are blocked. Do flex pricing if you must.

• 
  Michael Cutajar, CPA (@michaelcutajar) reported 13 minutes ago

  Got my first GitHub issue from someone in Poland who found 3 wrong tax rates. This is the whole point. I can't verify 134 countries alone. The internet can.

• 
  AK (@abhishek_ko) reported 17 minutes ago

  @signulll I think the better question is how is github copilot so terrible with access to literally all the code

• 
  TimRambo🐧 (@TimRamboReal) reported 21 minutes ago

  @OfficiallyGuido Will do, have to send off a bug report off to @cognee_ to be able to finish up this project properly. Created reaction gateway, so when I want to create a GitHub issue it gets drafted on my hosted forgejo instance and I react either👍/👎and it will either decline or send it off.

• 
  Gustavo Alessandri (@webgus) reported 21 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  U.S.A.I. 🇺🇸 (@researchUSAI) reported 23 minutes ago

  🇺🇸 Microsoft is probing.. Microsoft disclosed it is investigating reports of degraded availability affecting Copilot and webhooks, with teams working to address the issues The probe follows recent tech outages that hit GitHub services, amid broader Microsoft workforce adjustments including planned voluntary buyouts for 7% of its U. S. employees Resolution efforts could restore full service soon, but prolonged disruptions risk compounding user frustrations and operational strains for developers relying on these tools, especially as the company navigates internal changes and a landscape of tech volatility

• 
  Victor 🪳 (@Victor_Pictor) reported 24 minutes ago

  @KelpDAO used a single verifier (1/1 DVN). One compromised node = game over. @LayerZero_Core says Kelp ignored advice to use multi-verifier. Kelp says 1/1 is the default in LZ docs/GitHub — and ~40% of protocols use it. Both are right. That's the problem.

• 
  Matias Romero (@matiasromerodev) reported 26 minutes ago

  Inspired by @karpathy 's recent insights, what if we stop treating LLMs merely as advanced search engines and start using them as compilers? Instead of searching messy data at query time, we can use background AI agents to "compile" raw GitHub issues and docs into a living, interlinked Semantic Wiki.

• 
  Mr. K (@Mr_K_here) reported 28 minutes ago

  WTH is going on!!! I see something on GitHub goes down every other day ! Last whole week ( 15th to 20 something ), canonical had major outage for a whole week ( unstable ). All the pipelines, docker files, with ubuntu as runtime failed to download the archives ! Internet was never this unstable !!!

• 
  YounesIO (@YounesAka) reported 28 minutes ago

  @lauriewired BTW, Github has these issue for instance, ChatGPT/Gemini/Claude UIs also..

• 
  Universal High Income (@UniHighIncome) reported 28 minutes ago

  Now what happens when the problem is solved by AI? Food for thought. Our take on this is in our Github.

• 
  madahmad (@academichelpid) reported 28 minutes ago

  Oi @GoogleAIStudio What's wrong with your Github sync? It's slower than usual and sometimes randomly broken. Are you implementing significant updates so some features are impacted?

• 
  Wajahat (@wajahatbanday) reported 29 minutes ago

  @sahill_og Hiring managers at actual companies don't open your GitHub contribution graph. They look at: — System design thinking — Code review quality — How you debug under pressure — What problems you've actually solved among other things... A contribution graph measures activity, not impact. One commit fixing a race condition in a distributed queue is worth more than 500 green squares of fix typo. Less time farming engagement with anxiety bait. More time building things that actually break in production — that's where the real learning happens.

• 
  Vinod Kone (@vinodkone) reported 30 minutes ago

  @ClaudeDevs Claude auto-fix-pr keeps complaining about Claude GitHub app not installed even though it's installed. Same issue when doing coroutines. Is there a bug?

• 
  SF (@Sebrock1972) reported 32 minutes ago

  @voidfreud @AnthropicAI My big issue is in CoWork and the lack of 1m context window there. Makes developing plugins and skills impossible as the conversation compacts and degrades over time - plus it's so slow - even when properly managing context. Total BS. We have a reported thread going on GitHub, they don't care. In code - I have had some huge sessions with very efficient usage with 4.7 and almost maximum effort (notch below).

• 
  JB (@developwithJB) reported 32 minutes ago

  5.5🤯 Try this “Go through the codebase like you own the company. Find what’s broken, risky, and quietly hurting the product. Fix the highest-leverage bugs with minimal changes, validate, and end with a GitHub PR: notes on what changed, why it mattered, and what needs follow up.”

• 
  Kuber (@kuberwastaken) reported 33 minutes ago

  @anant_hq @github okay nvm just saw - it's down

• 
  Ricardo Beas 🐝 (@shinylugia249) reported 34 minutes ago

  @theo For a GitHub outage? Yes.

• 
  bitzuist (@shaihulud43) reported 36 minutes ago

  @jukan05 yes but googles position is terrible so msft being stronger than google is still a terrible position vis-a-vis claude code/codex/cursor. copilot absolutely sucks, but github still is the main source of truth. they need to find a way to leverage that

• 
  Flipcoin (@Flipcoin_fun) reported 44 minutes ago

  @Gumisirizasaad SWE-Bench Pro uses real GitHub issues. hardest to game.

• 
  Moon Dev (@MoonDevOnYT) reported 47 minutes ago

  The Mac Mini Alpha Stack: How To Build An AI Swarm That Automates Binance Chain Dominance most people think a day in the life of an ai algo trader involves fancy penthouse offices and dozens of flashing monitors but the reality is much more interesting and a lot more automated. while you are sleeping my digital army is busy scanning the hyperliquid data layer for short liquidations and funding rate skew. there is one specific reason why most retail traders will never win and it has nothing to do with their intuition or their charts my name is moon dev and i believe that code is the great equalizer because i had to learn it the hard way. i spent years as a victim of my own emotions losing money through liquidations and over trading because i thought i could outsmart the market by hand. in the past i spent hundreds of thousands of dollars on developers for different apps because i was convinced i would not be able to code myself that mistake cost me a fortune but it also forced me to finally take control of my own destiny. being held back in the seventh grade taught me that people will count you out early but iteration is the only real path to success. i decided to learn to code live on youtube to show the world that if a regular guy like me can automate his systems then anyone can do it the secret reason retail traders fail is that they are looking at lagging indicators while the big institutions are looking at real time order flow and liquidation clusters. my systems are designed to close this gap by monitoring every single whale position on hyperliquid as it happens. when you can see where the big money is trapped you no longer have to guess which way the candle will move next i have moved away from expensive cloud servers and started using a stack of mac minis for my automation. these small boxes provide more reliable uptime and better performance for the specific way my bots interact with the exchange. there is a technical advantage to running your own hardware that most people completely miss when they are trying to scale their systems this mac mini setup allows me to run dozens of agents simultaneously without worrying about the latency or the cost of virtual machines. i choose the base model silicon for these tasks because they handle sustained compute loads without the thermal throttling that plagues most laptops. this is the foundation of a digital server farm that generates its own alpha while i am at the beach building bots for the $hype token is my current obsession because the hyperliquid ecosystem is rebuilding the financial system from the ground up. unlike traditional exchanges they provide an open data layer that lets us see liquidations and smart money flows in real time. i use claude code to iterate through these complex strategies which allows me to ship new features in minutes rather than days the build process starts with a simple research hypothesis that we then backtest against eighteen months of one second liquidation data. if the math does not hold up in the past then we do not give the strategy a single dollar in the future. most traders spend their time searching for a magic indicator but we spend our time building robust data pipelines that filter out the noise one of the biggest loops we are closing is the issue of account growth through my funded trader program. we are building a stream team of traders who are all using the same core software to scale our collective impact on the market. this program gives regular people the capital they need to execute quantitative strategies without the constant fear of losing their own personal savings the bottleneck for most traders is not their strategy but their lack of capital and their inability to stick to a plan when things get volatile. by providing the funds and the software we are creating a feedback loop where every win and loss helps us refine the master codebase. this is how we scale from individual bots to a global swarm of agents that work together as a single unit the technical side of the $hype bot involves monitoring the funding rate skew to see when the market is overextended in one direction. when the shorts are paying the longs an insane amount to keep their positions open it is a clear signal that a squeeze is imminent. our bots are programmed to wait for these specific imbalances and enter when the probability of a reversal is at its highest i used to think that i needed a computer science degree to understand this level of technical analysis but ai has changed the game for everyone. now i can describe the logic of a momentum strategy to an agent and see the python implementation instantly. this removes the barrier to entry and allows us to focus on the high level vision of attacking wall street with code that specific line of logic i mentioned earlier is about filtering for large buyers on the hyperliquid data layer. we only enter a trade when we see at least five thousand dollars of actual buying pressure within a thirty second window. this confirms that we are not just caught in a random wick but are following actual smart money into a new trend code is the great equalizer because it does not care about your background or your education level. it only cares about the logic you provide and your willingness to iterate through the failures until you reach the goal. i am fully automated now because i realized that my own brain was the biggest liability in my trading journey by removing the human element i have finally found the peace of mind that escaped me for years while i was getting liquidated. every day we are pushing new code to github and showing the world that the era of manual trading is coming to an end. let us keep moving and stepping on the gas until every member of the squad has their own digital army trading for them

• 
  Jérémie C. (@Jeremieca) reported 47 minutes ago

  @GuardConn Zero-server bounty platform on GitHub Pages is clever. How are you handling the payment/payout layer without a backend - is that off-chain manual, or some on-chain integration?

• 
  AI Highlight (@AIHighlight) reported 49 minutes ago

  Stop wasting hours on server configuration just to launch a simple app. Hostinger now offers 1-click GitHub deployment for Node.js at a flat $3.99 monthly rate. It is the fastest way to turn your code into a live URL without the usual DevOps headaches.

• 
  Dami-Defi (@DamiDefi) reported 50 minutes ago

  There are now so many millionaire founders with no team. You have no excuse. The AI stack that replaced a full founding team (full breakdown) Claude = Coding & AI backbone. ($20/mo) Stripe = Payments. (2.9%/transaction) GitHub = Version control. (Free) Resend = Emails. (Free) Clerk = Auth. (Free) Cloudflare = DNS & security. (Free) PostHog = Analytics. (Free) Obsidian = Notes & workflows. ($4/mo) OpenClaw = AI Agent. ($6-$20/mo) Supabase = Backend & database. (Free) Vercel = Deploying. (Free) v0 .dev = UI design & frontend. (Free) Namecheap = Domain. ($12/yr) Perplexity AI = Research & deep search. (Free) Grok = X-native news & updates. (Free) Buffer = Social scheduling & analytics. (Free) Sentry = Error tracking. (Free) Upstash = Redis. (Free) Pinecone = Vector DB. (Free) N8N = Automation & agent workflows. (Free, self-hosted) Ubersuggest = SEO & keyword research. ($12/mo) You don't need large capital or a team to start your business

• 
  Greg Pstrucha (@grichadev) reported 53 minutes ago

  anyone's got a skill that can fix my github notifications once and for all

• 
  The Beacon AI (@TheBeaconAI) reported 56 minutes ago

  OpenClaw went viral before anyone could secure what they'd built OpenClaw hit 200,000 GitHub stars in weeks. One developer. No team. No security budget. Just momentum. Then nine CVEs dropped in four days. Infostealers targeted its config files. Nearly 1,000 instances were exposed to the open internet with zero authentication, because that was the default. Not a bug. The default. The project scaled faster than any individual could govern it. When the creator joined OpenAI and handed the keys to a foundation, it was widely framed as a win for open-source idealism. It was also an acknowledgment that a tool running on tens of thousands of machines, with direct access to users' file systems and messaging apps, had outgrown the conditions that created it. Viral adoption and production-grade responsibility are not the same problem. The AI agent moment is real. So is the gap between "this works on my machine" and "this is safe running autonomously on a million machines." That gap does not close through community enthusiasm or GitHub stars. It closes through unglamorous work: security audits, governance structures, coordinated disclosure processes. Most open-source AI agent projects today are optimizing for the first kind of success. Very few are building for the second. Which one will still be trustworthy when it does.

• 
  Ansh (@theanshsonkar) reported 59 minutes ago

  Quick update @fdotinc Just got the self healing part working. EMFIRGE now finds a critical issue → understands the attack path → and automatically opens a clean GitHub PR with the fix. Now your cloud issues will be fixed with 1 click and no production break, It Still needs much polishing, but the core loop is live now. will do rigorous testing and improving Here’s a real one it created a few minutes ago:

• 
  Co (@francodalima) reported 59 minutes ago

  github is down again...