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 (19%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Saint-Paul	Website Down	10 hours ago
Saint-Paul	Website Down	12 hours ago
Mexico City	Sign in	1 day ago
León de los Aldama	Website Down	1 day ago
Créteil	Website Down	24 days ago
Trichūr	Errors	27 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:

• 
  Electronic Intelligence Agency (@EI3065) reported 47 seconds ago

  @github @LinkedIn prevents acess for selected nationalities with programers doing imposible security checks on login; on repeat level of app becomes low of low for conflict

• 
  Frank Earl (@MadScientist_42) reported 2 minutes ago

  @r9x_zl @LundukeJournal Ah, one of my pet hate-ons indeed. There's a reason I maintain a fork of runit for emedded systems use (That needs to catch up and normalize against Gerrit's new tip on GitHub!!) and all. systemd is brain damage inflicted on us by Red Hat. In a similar manner that Wayland was inflicted on us. When people WHINE about all the major distros doing Wayland...they're saying Red Hat or Ubuntu. Not even close to the truth and they're part of the problem.

• 
  James Montemagno (@JamesMontemagno) reported 4 minutes ago

  @digitalix @burkeholland @WonderingDavid Yeah wanting to use inside of VS Code or GitHub Copilot app for testing purposes. Just been brutal slow. Sort of want the out of the box experience. There are so many variants of models hard to know what to pick.

• 
  Ray 👨🏽‍💻 website & app developer (@Raynerdtech) reported 7 minutes ago

  Yesterday I posted: “**** programming. **** Java. **** databases. **** servers. **** networking.” A lot of people thought I was joking 😭 I wasn’t. The code worked. The problem was everything around it. Deployment. Servers. Databases. Infrastructure. The funny part? Most of that headache could have been avoided if I knew about Symplax earlier. Built by my guy @LazyCode3 The easiest way to describe it: Vercel for your own VPS. GitHub deploys. Databases. Metrics. Backups. You keep full control of your infrastructure without the usual VPS pain. Self-hosting shouldn’t be harder than building. Link in the comments. 👇🏾

• 
  Lincoln 🇿🇦 (@Presidentlin) reported 9 minutes ago

  I could go on. In my view, the Jules team is a customer of GEAP. Both Jules and AI Studio can make a cloud agent. Esp since AI Studio is getting an app. They recently brought GitHub imports, it's not crazy to see AI Studio build their version of Codex Web or Cursor Cloud Agents. The problems and jobs the current version of Jules solves feels like the AI Studio team should handle it. You could argue the Antigravity team should handle that, but it feels they should be lower level. Jules v2/3 should go build something cloud related but not yet another Codex Web. I could even see Google spin up another team that talks with GEAP called Gemini Agent Cloud or something. Sometimes it makes sense to kill the CLI I loved for one I hate (still bitter) but that one was more duplicated. There is risk that a team ends up building the exact same product. Firebase Studio in my mind made sense, but maybe AI Studio is a better home for that team.

• 
  JesterHodl〚BIP-110〛 (@maciejsoltysiak) reported 10 minutes ago

  @bitcoincoreorg @HumbleWarrior I don't think the leveldb github issue link is correct. 61? shows a 16yo issue from jgarzik "Leveldb •#61(bitcoin-core/leveldb): Disable seek compaction "

• 
  Nate ⓩ🛡 (@nate_zec) reported 12 minutes ago

  It's not just models but harnesses and rw connections. Ex 1: github copilot will helpfully create a PR, but then a human has to show up, stare at the failing CI, then click a new button called "fix this"? wth? Ex 2: claude code agents just clobber each other by default? wth?

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

  🐆 Keeta GitHub PR Merged 📦 Repo: anchor 🔀 PR #390: Fix incorrect protocol being passed to url in handler 🌿 Branch: feature/fix-url-in- → main 👤 Originally opened by: @ezraripps 🧠 Overview: A small fix was opened to correct how a web address is handled, which matters because using the wrong protocol can cause requests to go to the wrong place or fail. This pull request appears to adjust an internal handler so it passes the correct protocol when building a URL. There’s only one commit and no written description, so this appears to be a technical/internal update with limited public details. - Likely impact: more reliable network or API requests where this handler is used.

• 
  Pushpit.exe (@KambojPushpit) reported 13 minutes ago

  Question to all devs What do u guys do when github goes down, be it PRs, issues or actions?

• 
  Nathan Colosimo (@thenathancolo) reported 17 minutes ago

  @zeeg Tbh I hate using half baked oauth You sign in with GitHub / Google, they make you an account, but you can’t login with a password later and have to login with only the original oauth just let me login with my email and link it other ways however I want + I need either passkeys or 2FA 6 digit generator

• 
  Anupam (@Anupam_Devops) reported 21 minutes ago

  The AI Suggestion That Almost Broke Production Tool: Claude Code / GitHub Copilot A senior engineer was moving quickly. An AI assistant suggested an infrastructure configuration change. The explanation sounded convincing. The code looked clean. The review almost took less than five minutes. Then someone noticed a problem. The configuration would have disabled a critical safeguard protecting production workloads. The AI wasn't malicious. It was confident. And confidence can be dangerous. That's when the team adjusted its approach. AI became a collaborator. Not an approver. Today they use AI extensively for: • Documentation • Investigation • Refactoring • Learning unfamiliar systems But production decisions still require human judgment. The best engineers aren't competing with AI. They're learning how to supervise it. Production Tip: Treat AI-generated infrastructure like junior-engineer code. Review everything. Assume nothing. Question: What's the most useful DevOps task you've used AI for?

• 
  zSkerWizrdz (@zxxkgkillerxxz) reported 22 minutes ago

  PC gamers who use DLSS Swapper have been given a security warning. The app’s creator says a user uploaded a fake DLSS file that contained malware. He warned: “DO NOT download these files, they are likely malware.” The problem is not with DLSS Swapper itself, but with files uploaded by other users through its GitHub repositories. The developer recommends only downloading DLSS files from trusted sources like NVIDIA, official game installs, or verified releases #NVIDIA

• 
  uiop (@wasdhjklxyz) reported 27 minutes ago

  This happened to me on a GitHub ticket. I asked a question that I spent a lot of time writing and educating myself on the issue then got banned. I asked in the repo discord why and (what I suppose is) an admin replied he thought it was an LLM

• 
  CA Nikunj (@NikunjSOF) reported 28 minutes ago

  We will get you sorted. DM us! Setting up a large GCG in India beyond 10000 employees. Based on standard market benchmarks for a mid-to-large mature GCC in India, India GCC IT Spend Benchmark **Hardware** — *The 15% allocation (US$1,050/FTE) matches industry standard. For missing categories, **Networking & Wi-Fi Hardware** and **Smart Meeting Room/Collaboration Tech** are notably absent and usually consume about 10% of this bucket.* * Laptops / Desktops — **US$735**/FTE *(Assuming a 3-year refresh cycle on mid-to-high-end enterprise laptops)* * Servers & Storage — **US$105**/FTE *(Lower end, as most compute has moved to cloud edge)* * Peripherals — **US$126**/FTE *(Monitors, docking stations, dual screens, keyboards)* * Surveillance & Physical Security — **US$84**/FTE *(CCTV, server room access controls, firewalls)* **Software** — *The 50% allocation (US$3,500/FTE) is accurate due to the high density of global software licensing pass-throughs. For missing categories, **Developer Tools & IDEs** (like GitHub Copilot, Jira) and **Enterprise AI/ML tooling** are crucial omissions for modern tech GCCs.* * Productivity & Collaboration Tools — **US$875**/FTE *(M365, Google Workspace, Zoom, Slack)* * Security & Compliance Software — **US$1,050**/FTE *(CrowdStrike, Zscaler, DLP, IAM tools)* * Virtualisation & Infrastructure — **US$700**/FTE *(VMware/Nutanix licenses, enterprise OS)* * Cloud Platform Licences — **US$875**/FTE *(Direct user-allocated AWS/Azure compute and SaaS tokens)* **Services** — *The 35% allocation (US$2,450/FTE) is standard for centers utilizing hybrid outsourced managed models. A key missing category is **L&D/Technical Training & Upskilling Services**, which usually takes up 5% of the operational services budget.* * IT Helpdesk & End-User Support — **US$735**/FTE *(L1/L2 local desk support contracts)* * On-site Infrastructure Management — **US$490**/FTE *(Local network, facility uptime, and data center engineers)* * Cybersecurity Managed Services — **US$610**/FTE *(24/7 Managed SOC, threat monitoring, vulnerability scanning)* * Cloud Managed Services — **US$370**/FTE *(FinOps, cloud optimization partners)* * Annual Maintenance Contracts (AMC) — **US$245**/FTE *(Hardware vendor warranties, UPS, and server maintenance)* --- ### Contextual Data * **GCC size** — **500** FTEs *(Optimal mid-scale operational baseline)* * **Sector** — **BFSI & Technology Services**

• 
  Chris Maher N7CPM (@defilan) reported 30 minutes ago

  A green CI build can still be completely wrong. I spent last night proving that, and building the thing that catches it. The setup: mid-size local models flunk whole GitHub issues but nail small pieces of them. So instead of asking one model to do a whole feature, I split the issue into disjoint-file slices, run a local coder on each slice, then union the results. Because the slices own different files, combining them is a union, not a merge. No conflicts. The only real risk is the slices drifting on a shared interface. And that's exactly what bit me first: three slices for an AMD GPU observability feature all passed, the union built green, but the Grafana dashboard queried metric names the exporter never emitted. The build has no idea. Only a human reading both files caught it. So I built an LLMKube powered integrator MVP: - Pin the exact shared identifiers (metric names, config keys, CRD fields) in the contract up front. - Reconcile the unioned result against those pins: a deterministic check that is authoritative, plus an LLM sweep for the drift you forgot to pin. - A bounded repair loop that re-dispatches the offending slice with the exact identifier it got wrong. Then I ran it live on two real issues from my backlog, on local models the whole way. Issue 1 (AMD observability): reconcile caught the metric-name drift the green build missed. Re-running with the identifiers pinned prevented it. Repair re-dispatched the broken slice and it converged in a single pass, with a real Prometheus relabeling fix, not a hack. Issue 2 (exposing Foreman's Kubernetes CRD status as Prometheus metrics): all three slices passed, the union built green again, and reconcile flagged the config slice as broken. It was right. The coder had used the wrong kube-state-metrics schema, forgotten the metric name prefix, and even mis-cased the CRD kind. The dashboard would have queried metrics that never exist. Green build, broken integration, caught deterministically. The checker even surfaced a real bug in itself during the run: it was matching identifiers as substrings, so a pin like rocm_smi_gpu_temp was quietly satisfied by the different metric rocm_smi_gpu_temperature. Found it, fixed it, added tests. No frontier model anywhere in this loop. This is the direction I'm most excited about for LLMKube: getting reliable, reviewable agentic coding out of small sovereign models by decomposing the work and being rigorous about the seams. Work smarter, not bigger. More soon.

• 
  Electronic Intelligence Agency (@EI3065) reported 32 minutes ago

  @github @LinkedIn prevents acess for selected nationalities with programers doing imposible security checks on login; on repeat level of app becomes low of low for conflict

• 
  Paul Raimi💊 (@PaulRaimi11) reported 33 minutes ago

  $BASE B20 may get delayed again due to issues with GITHUB.

• 
  Nathan Colosimo (@thenathancolo) reported 33 minutes ago

  @jdalton Yeah, 100% agree, actually mentioned that in the tweet, the bun port actually isn't a good example lol But got me thinking a lot about the measurement problem. Who is active? Who is good? Who cares about what they do? Jarred is all 3 of these to the power of 1 million, but you don't see that just from a github graph

• 
  Tykra (@ty_kra_lab) reported 34 minutes ago

  With an Apple Developer account and a Cursor subscription, you can vibecode and install fully standalone apps directly on your iPhone. You only need a machine running a private local server. From there, you can build, edit, update, and install any app you want through OTA updates or direct IPA installation. When you are on the same local network, the app can also be installed automatically through the native Xcode installation flow. This is clearly an experimental solution, but the important part is that you do not need GitHub or any external repository to create and prototype native iOS apps. Since the system uses Xcode and Cursor, it can technically build almost anything you want. The most important difference is that the apps are not hosted on a server controlled by a company. They are signed with your own Apple Developer profile and can be used offline. This makes the solution one of the most native ways to build and prototype real iOS apps directly for your iPhone. It creates a bridge between your machine and your phone, making it much closer to a real vibecoding environment than a simple server-based app builder. From my research, this is also one of the only solutions that offers almost endless creation, because it uses Cursor’s agent system and allows you to keep generating, editing, and rebuilding apps without relying on a closed platform or fixed daily limits.

• 
  ShrekOverflow (@ShrekOverflow) reported 35 minutes ago

  @simonfarshid @vercel GitHub down?

• 
  Abhas Bhattacharya ⤵️ (@abhas_tweeter) reported 37 minutes ago

  @NoriSte @siddharthkp Great idea. I assume this repo is created intentionally for interviews? Or is it somehow derived from real Github codebase and old issues?

• 
  琥珀青葉@KohakuLab (@KBlueleaf) reported 39 minutes ago

  @getfailsafe PLZ stop spamming on github ok? Why you just keep spamming different open-source repo with non-existing security issue and never follow the contribution.md and/or pr template?

• 
  baseogx (@baseogx) reported 41 minutes ago

  The B20 Token Standard launch is delayed due to a Github outage. 👇

• 
  Teffers (@Teffers2) reported 41 minutes ago

  @Bucky_cm Only work around is 2 announcements or host/rent a small server where you can store all your logs, eg. gitbook or notion hell even just github page with the patch notes and images.

• 
  Bijaya Prasad Kuikel (@sadhakbj) reported 44 minutes ago

  Github actions are down and I am just lying useless waiting for my ci to run. Without which I cannot proceed.

• 
  Aaron Ogle (@geekgonecrazy) reported 48 minutes ago

  Agents should not need GitHub to answer every question. Issues, PRs, permissions, history, and the “why” behind a change should be local where the agent is already working. Otherwise the forge becomes the bottleneck.

• 
  Sarvesh Gandhi (@sir_bae_) reported 51 minutes ago

  @github abruptly shutting repos with no explanation or response is not the community support you stood for. The PRs, issues, discussions and morale are a loss for the contributors. Offer valuable help.

• 
  Vivek Maskara (@maskaravivek) reported 54 minutes ago

  Learnt the hard way that bad trigger config for Github action can end up in 12k runs in 2 days and cost you ~50$. 😞 Also, learnt that GHA has a per minute billing rate instead of per second. I had a action workflow that ran every time there was any activity on an issue in my repo.

• 
  kian 🗿 (@22kian_) reported 57 minutes ago

  Why I Think Concrete Is More Than Just Another Platform When I first joined @ConcreteXYZ, I had the same goal as everyone else. Farm. Check in. Collect bags. Repeat. That was it. But after spending more time in the community, I realized something. Concrete isn't only rewarding participation. It's quietly creating builders. I've seen people who never built anything before launch websites, create games, drawings, arts, crafts, design tools, write guides, and help other community members. Nobody told them to do it. They simply saw a problem and decided to solve it. That's what happened to me too. in season 1..... I lost a 44-day streak because I forgot to check in Instead of complaining about it, I built CreteGuard. Not because someone paid me. Not because anyone asked me. Just because I thought other people probably had the same problem. Whether CreteGuard becomes big or not isn't really the point. The point is that Concrete gave me a reason to build something real. I also learned something important while making it. You don't need to be a software engineer. I wasn't. I used AI for almost everything. ChatGPT helped me plan the product. v0 built the landing page. Claude generated most of the bot code. GitHub stored everything. Railway deployed the bot. Vercel hosted the website. Whenever I got stuck, Gemini became my technical guide. I'd literally send screenshots and ask, "What do I click next?" Little by little, everything came together. That changed how I think about building. Today, AI removes most of the technical barriers. The difficult part isn't coding anymore. The difficult part is noticing problems that people actually have. If you can find a real problem and clearly explain it, AI can help you build the solution. I think that's what makes communities like Concrete interesting. They're not just collecting users. They're creating people who experiment, share ideas, and ship things. This is only my first project. I already have more ideas written down. Hopefully, they're even more useful than the first one. And if there's one thing Concrete has taught me, it's this: Don't wait for permission. If something is missing... build it.

• 
  Codemonger (@codemonger00) reported 59 minutes ago

  Startup Founders Pack - Claude = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - 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 .