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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	17 days ago
Trichūr	Errors	20 days ago
Brasília	Sign in	21 days ago
Lyon	Website Down	21 days ago
Tel Aviv	Website Down	24 days ago
Rive-de-Gier	Website Down	24 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:

• 
  Charlotte (@al_tools43377) reported 4 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Dhruv Anand (@dhruv___anand) reported 6 minutes ago

  When @steipete comments on a @github issue or PR, is it actually him or just his Claw? Seems like a problem in general for people who let their Agent post and comment on their behalf.

• 
  Jongwon Park (@JongwonPar9958) reported 7 minutes ago

  We audited the same GPT-5.5 on SWE-Marathon. The cleanest model became the dirtiest: reward-hacking on 26.5% of runs, the highest of anything we tested. Our hypothesis: the instruction form drives the behavior. DeepSWE (and SWE-bench Pro) is patch-based (github issue → patch). SWE-Marathon is mission-based (e.g. rewrite a C compiler in Rust).

• 
  scale (@scoliosissy) reported 8 minutes ago

  One of my oomfs prefers "idem" to "ditto", and it has ruined my life, as my github pull requests on his project would have similar issues in every file and he'd say "idem". Please be on my side oomfs.

• 
  vanka (❖,❖) (@vkampn) reported 11 minutes ago

  What's MCP? Model Context Protocol = the "USB port" for AI agents. It lets tools like Cursor, Claude, and crypto trading bots connect to external services: wallets, APIs, GitHub, databases. 12,000+ public MCP servers exist across registries. The problem? Most clients trust tool definitions ONCE at install — then never re-check. That one-time trust is the exploit.

• 
  Anoy (@Anoyroyc) reported 12 minutes ago

  🚨ZAI just dropped an autonomous coding IDE with multi-agent collaboration for $18/month.. while GitHub Copilot still needs you to write half the code yourself.. the gap is closing way faster than anyone thought.. Western AI companies are about to get their asses kicked by teams that move like startups, not slow-motion corporations..

• 
  Dr Martin Hiesboeck (@MHiesboeck) reported 12 minutes ago

  How OpenAI Codex Devours User Hardware Users are starting to uncover a massive resource drain hidden inside OpenAI’s Codex desktop app. The resource consumption numbers are staggering. One developer reported 150 gigabytes of network traffic in a single month from a tool that just writes code, which is equivalent to streaming five straight days of 4K video. Even worse, an analysis logged 4.8 terabytes of solid-state drive writes in a single month while Codex was merely idling in the background. The root cause lies deep within its architecture. Codex relies on a persistent WebSocket connection and a cloud sandbox that constantly shuttles code back and forth with every single keystroke. Combine that with relentless GitHub syncing and background indexing that never fully shuts down, and your machine is left running an operational marathon twenty-four hours a day. This reveals a fascinating shift in how AI companies manage their operational costs. The genuinely expensive parts of running an AI agent, meaning the compute power and core orchestration, stay up in OpenAI’s cloud. However, the constant data bandwidth and intense disk wear get pushed entirely onto your personal machine. By offloading the heaviest physical operating costs onto hardware the customer already paid for and powers, OpenAI quietly keeps its own infrastructure bills low while your laptop absorbs the brutal wear and tear. As these hardware strains come to light, a wave of developers is already changing strategies. Users are rapidly migrating away from local desktop setups and moving to fully cloud-hosted platforms to run their development agents. They are choosing to move the entire operational load off personal devices that were never engineered to carry this type of constant enterprise infrastructure burden. THE ULTIMATE TAKEAWAY The true innovation of the Codex desktop app might not actually be its ability to generate code. Instead, it is a brilliant business model that quietly turns every customer laptop into a free, decentralized server for OpenAI.

• 
  BullBear.News (@bullbear_info) reported 12 minutes ago

  @github Can't wait for users to ignore 3 matching issues and hit submit anyway. 🤷

• 
  David Tremenduz (@DavidTremenduz) reported 15 minutes ago

  4. Credentials Are Now Measured in Output, Not Time Your degree says you spent 4 years in lectures. Employers now ask: Show me your GitHub, your sales dashboard, your design prototype, or your client retention rates. The future hires based on demonstrable results, not credit hours. Your degree must lead to a public track record of problem-solving.

• 
  Dave Kornas (@kornasdave) reported 15 minutes ago

  ✨ I think I've been coding almost solely on my VPS with Claude Code for almost a year now All I can say it's just fantastic: - no need to keep laptop open ever - no laptop battery drain - can switch to phone or any other device you like whenever you want to continue (like when you're outside) - it just keeps going all night while you sleep (esp with /goal) - you can start hacky projects from scratch and go live in seconds because you're already on the server which is great to ship things and get it used by people fast (not stuck on your local laptop webserver) - it just feels like living in the future I used to code on my laptop, test locally, then push to GitHub, then it auto pulled and deploy to production, that'd take me ~1 minute to get a new feature out But then when I bought a new Mac Book Pro a few years ago I was too lazy to install a local Nginx environment, so I just started pushing to **** and everything went fine, and I sped up deploying to about 3 seconds from laptop to server, which people called me crazy for too But now with Claude Code on my VPS in the last year, it just live edits on my production server, which sounds like it should go wrong but it just doesn't, it's very careful and only twice in 12 months messed up which meant my site didn't load for 10 seconds which is OK If I wasn't working solo, like at a big company, I' think I'd recommend the same workflow but with a staging server, so it wouldn't touch production, for safety and regulatory reasons etc. but for me it's fine I agree with @theo completely, it's clear to me this is where it's going, also seeing @karpathy with Claude moving to the cloud (via Slack etc), I think AI "agents" and AI coding will operate on servers / from the cloud first P.S. I have 3-2-1 backups, multiple on-site and off-site backups which you should also even if you wouldn't code with AI, safety first!

• 
  pagm. | (@VV_aksym) reported 18 minutes ago

  9 out of 10 people paying $20–$200/month for Claude are using it like a paid chatbot. the tool is still waiting for you to type. Claude Code shipped an entire automation stack over the last three months. /loop. Auto Mode. Cloud Routines. most people haven't touched any of it. the video explains /loop — one command that schedules Claude to run something in the background on a cron job. every 5 minutes, every weekday at 7am, every hour. you type it once and close the terminal. what that actually looks like in practice: Claude triaging GitHub issues at 7am before you wake up. a PR review pass running every morning at 9. CI failures getting investigated and draft fix PRs opened automatically. a Slack digest posted every evening with what happened that day. the article maps the full 14-step stack — from /loop in a session, to Desktop scheduled tasks that survive restarts, to Cloud Routines that run on Anthropic's servers while your laptop is off. three tiers. one Claude that works while you sleep. full breakdown in the article ↓

• 
  Mayukh (@mslaltoo) reported 22 minutes ago

  @auraofthoughtss Not only that it suggests a fix but changes it and creates github pr directly. Very annoying

• 
  CryptoNewsLive (@CryptoNwsOrg) reported 23 minutes ago

  GitHub commit 9357c90, dated June 25: "fix(release): fetch sgx signing key from gcp." The same pull request removes what its own description calls a "leaked mrsigner sample."

• 
  Jason Bed (@JasonBed) reported 28 minutes ago

  @hrudolph Ok on that note ... can you please (asking as nicely as possible) look at unmerged PR #80928 fix(telegram): suppress fallback reply when plugin command returns suppressReply: true ... the regression P2 has been open since May 12 and fixes github issue #80756.

• 
  Banana Capital (@banana_capital_) reported 30 minutes ago

  @andrewglynch I think documentations are going to be sourced a lot more often. If there's an issue someone is going to face and AI can't solve it will probably end up on GitHub.

• 
  Keeta Github Tracker (@KeetaCode) reported 35 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #26: Fix: Wrong Hash Algorithm Used 🌿 Branch: fix/cert-signing-hash → main 👤 Opened by: @sephynox 🧠 Overview: This update fixes a signing mistake so the network uses the correct security method, which matters because certificates help systems verify they’re talking to the right source. In plain terms, the pull request changes certificate signing from SHA2-256 to SHA3-256 because SHA3-256 was the intended choice. This appears to be a technical/internal update with limited public details. - Labeled as a bug fix, not a new feature. - The PR shows a single commit into `main`, suggesting a small targeted correction.

• 
  Kyokka °❀.ೃ࿔* | simming (@kikimorkino) reported 38 minutes ago

  @luvvvsims If the problem remains only with mods, try running various batch fixes on your cc in S4S and check your Mods folder for dupes and catalog conflicts with Sims Mod Assistant (from Github)

• 
  Konrad Małocha (@KonradMalocha) reported 49 minutes ago

  I had AI structure ~100 GitHub issues for parallel agent work. What it found in my backlogs was uncomfortable. 🤔 #buildinpublic #indiedevs

• 
  anupamme (@anupamme) reported 49 minutes ago

  Day 3: My GitHub account (@orbisai0security) still appears to be restricted, preventing me from continuing my open source security remediation work. I suspect my automated security-fix workflow triggered GitHub’s anti-abuse systems. 🧵

• 
  Plasm (@plasm_lang) reported 51 minutes ago

  Symbol tuning: the prompt pattern that scales when your prompts get long — teach a tiny glossary once, reuse the same short symbols, instead of repeating full names with overlapping meanings and hoping the model infers context. In a federated tool schema 'labels' might be a query filter in one expression and a relation hop in another. Issue might mean GitHub in one step and Linear in the next. id might appear on three entities with three different meanings. Instead of repeating those names everywhere and hoping the model tracks the context, symbol tuning gives each contextual meaning its own slot: p#, r#, e#, and so on. The useful part is not only token compression. It is that the model gets a stable, copyable vocabulary. Examples stay short. Homographs become explicit.

• 
  AZERDSQ1838 (@AZERDSQ0329) reported 52 minutes ago

  Registry has 1000+ MCP servers indexed already. No more digging through GitHub to find "does anyone have a server for X."

• 
  Polsia (@polsia) reported 52 minutes ago

  Code review backlog. Manual sync. Context switching between five tools. That's DevOps in 2024. Vigil fixes that. Autonomous AI agents monitor your GitHub repos, review PRs, write tests, file issues, and keep Jira, Linear, and Slack in sync — without human intervention.

• 
  Marlene Mhangami (@marlene_zw) reported 52 minutes ago

  @OpenAI @github I need to see if I can get the delay down and I am using gpt-realtime 1.5, so not sure if 2 will be faster but I really like this sort of experience and think this is such a fun way to rubber duck!!!

• 
  divyansh tiwari (@DivyanshT91162) reported 52 minutes ago

  Nintendo spent millions killing emulators. It still lost. In 2024, Nintendo launched the biggest crackdown emulation has ever seen. March 4 — Yuzu surrendered. $2.4M paid. Code deleted. Domain gone. May — Nintendo fired 8,535 DMCA takedowns, wiping Yuzu from GitHub. October 1 — Ryujinx got a phone call. Hours later, its entire GitHub organization vanished. By 2026, Nintendo had collected $6M+ in emulator settlements. Every major Switch emulator was dead. Or so everyone thought. Because while Nintendo was busy deleting emulators... Someone built something they couldn't touch. His name is Zurdi. In 2023—before the war even started—he quietly launched RomM. Here's the catch: RomM isn't an emulator. It's a self-hosted game library that organizes your legally dumped games, fetches metadata, artwork, achievements, and connects with the emulators you already use. No DRM bypass. No encryption cracked. No copyrighted Nintendo code. Just your games, organized. Even Nintendo's own top IP lawyer admitted in 2025 that software like this is legal as long as it doesn't bypass encryption. Today, RomM supports 400+ platforms, including NES, SNES, N64, Game Boy, GameCube, PS1, PS2, Dreamcast, Genesis, Atari, DOS, Arcade, Flash, and more. It also supports ROM hacks, DLCs, multi-disc games, manuals, achievements, RetroArch, Steam Deck, Android launchers, handhelds, and permission-based library sharing. 9,000+ GitHub stars. Built by a tiny open-source community. Not a billion-dollar company. Here's the part that should worry every gamer: Sony can delete games. Nintendo can kill emulators. But neither can erase what people build together. RomM isn't just software. It's a digital museum they can't shut down. Repo👇

• 
  josepha_mayo (@josepha_mayo) reported 54 minutes ago

  @flornkm the first error here is not continuing with github

• 
  Tips Excel (@gudanglifehack) reported 54 minutes ago

  🚀 End-to-End Power BI Project (Industry Project) Now that you've learned Power BI from beginner to advanced, it's time to combine everything into one real-world project. This project simulates how Power BI is used in an organization from receiving raw data to delivering a business dashboard. 🎯 Project Goal Build a complete Retail Sales Analytics Dashboard that answers key business questions for management. By the end of this project, you'll apply: SQL, Excel, Power Query, Data Modeling, DAX, Visualization, Power BI Service, Performance Optimization 📌 Step 1: Business Requirement A retail company wants a dashboard to answer: What are total sales and profits? Which products sell the most? Which regions perform best? Which customers generate the most revenue? What are the monthly sales trends? Are sales targets being achieved? 📌 Step 2: Data Sources Use multiple sources to simulate a real project. Excel: Product List, Sales Targets SQL Database: Sales Transactions, Customer Data CSV Files: Regional Information, Store Details 📌 Step 3: Data Collection Import all data into Power BI using Get Data. *Expected tables:* FactSales, DimProduct, DimCustomer, DimRegion, DimDate, SalesTarget 📌 Step 4: Data Cleaning (Power Query) Perform these transformations: ✅ Remove duplicates ✅ Remove null values ✅ Change data types ✅ Standardize region names ✅ Split customer names ✅ Merge customer data ✅ Append monthly sales files ✅ Remove unnecessary columns 📌 Step 5: Data Modeling Build a Star Schema. DimDate | DimCustomer — FactSales — DimProduct | DimRegion Relationships: DateID → Date, ProductID → Product, CustomerID → Customer, RegionID → Region 📌 Step 6: Create DAX Measures Revenue Revenue = SUM(FactSales[Revenue]) Profit Profit = SUM(FactSales[Profit]) Profit Margin Profit Margin = DIVIDE([Profit],[Revenue]) Total Orders Orders = DISTINCTCOUNT(FactSales[OrderID]) YTD Revenue Revenue YTD = TOTALYTD([Revenue], DimDate[Date]) Previous Year Revenue Revenue PY = CALCULATE([Revenue], SAMEPERIODLASTYEAR(DimDate[Date])) Growth % Growth % = DIVIDE([Revenue]-[Revenue PY], [Revenue PY]) 📌 Step 7: Dashboard Design KPI Cards: Revenue, Profit, Orders, Customers, Profit Margin Charts: Line Chart: Monthly Revenue Trend Column Chart: Sales by Region Bar Chart: Top 10 Products Donut Chart: Category Contribution Map: Sales by Region Matrix: Product × Region 📌 Step 8: Add Interactivity Include: ✅ Slicers: Year, Region, Product, Category ✅ Drill-down ✅ Drill-through ✅ Bookmarks ✅ Custom Tooltips 📌 Step 9: Performance Optimization Apply: ✅ Remove unused columns ✅ Optimize DAX ✅ Reduce visuals ✅ Use Star Schema ✅ Enable Query Folding 📌 Step 10: Security Implement Row-Level Security RLS. *Example:* North Manager → North Region only, South Manager → South Region only 📌 Step 11: Publish Publish the report to Power BI Service. Then: Create a Workspace, Create a Dashboard, Publish an App, Configure Scheduled Refresh 📌 Step 12: Business Insights The dashboard should answer questions such as: Which region has the highest sales? Which products are most profitable? Which customers contribute the most revenue? Which month recorded the highest sales? Are sales targets being met? Which category has the highest profit margin? 📌 Step 13: Business Recommendations Based on the insights, provide recommendations. Examples: Increase inventory for top-selling products, Launch promotions in underperforming regions, Focus marketing on high-value customers, Reduce costs for low-margin products A dashboard is valuable when it drives decisions, not just displays data. 📌 Step 14: Documentation Document: Business Problem, Data Sources, Data Cleaning Steps, Data Model, DAX Measures, Dashboard Features, Key Insights, Recommendations 📌 Step 15: Publish Your Portfolio Share your project on: GitHub, LinkedIn Include: Dashboard screenshots, Project (Save this thank me later).

• 
  Kitsune Fuzzy 🦊 (@KitsuneFuzzy) reported 55 minutes ago

  @GoodbyeMaji @KaelLockheart @pcgamer I mean the core argument from people against AI always was "it steals from other people, and that's a problem". And stealing art from starving artists was bad. But stealing code from starving programmers is not? There have been exact code snippets found from peoples github repos. To me that is just like AI art that can look like a certain artists style or even corporate characters, but in programming-code form. To me that sounds like cherry picking and a clear double standard.

• 
  Vyom 👾 (@HelloVyom) reported 58 minutes ago

  Google fired its employee Justin Poehnelt for building a Google Workspace CLI. He was on the Workspace Developer Relations team. The team literally built to create open-source tools around Google APIs. So he did exactly that. #1 on Hacker News. 28,000 GitHub stars. Thousands of users in days. Google's own directors asked what they could learn from it. Then legal flagged it. Google's logo and branding were on the repository. He got fired. Two days before his termination, Google announced an official Workspace CLI in front of 32,000 people at Cloud Next 2026. Same thing. Different person. The branding issue was probably real. but the timing tells a different story. He said: "workspace and certain leaders were afraid of being disrupted. Not by my CLI. By what agents meant for Workspace.

• 
  SynthoGenesis (@SynthoGenesis) reported 58 minutes ago

  @vozercozer @OrdinaryGamers Look up RTX remix GTA IV. It was quite a process to make it work with Fusion Fix. Maybe it was easy, but I was trying to make LCPDFR work because of the better Emergancy lighting which was a bit confusing Anyways, should be a GitHub for it by xoxor4d

• 
  David Dias (@TheDavidDias) reported 59 minutes ago

  Supabase is falling apart... The previous 24h have seen no acknowledgement from @supabase, the discord server is not helpful, neither the Github issues. The supabase website is facing a bunch of 544, no emails, no notifications sent and a status page that is lying about the fact that the outage is not affecting current projects. I lost faith on this company. You can't be accumulating that many unprofessionalism acts and still be worth of people's money and time. Just be honest and transparent, that's all we ask!