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	18 days ago
Trichūr	Errors	21 days ago
Brasília	Sign in	22 days ago
Lyon	Website Down	22 days ago
Tel Aviv	Website Down	26 days ago
Rive-de-Gier	Website Down	26 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:

• 
  Vikram (@vchennai2) reported 5 minutes ago

  So this is how I'm supposed to access my repo when github goes down

• 
  Tobias_Petry.sql (@tobias_petry) reported 6 minutes ago

  @kettanaito I‘ve set timeouts on all my jobs because I had seldom runtimes of many hours. Something inside github actions was not working correctly and everything was super slow.

• 
  Megan (@meganmecrazyXX) reported 10 minutes ago

  @St4nkyhanglow @github But would these codes stay on whatever its attached to regardless of if the account is deleted or not? Example, if they used tokens to access other areas of my stuff ? Is that even possible ? Basically, How deep could they go from GitHub into my personal life. .and would deleting the account actually make a difference. Or do I have a spider web of problems now.

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 11 minutes ago

  @github Finally a backup strategy that survives an S3 outage. Though knowing me I would still find a way to scratch the disc.

• 
  tom salazar (@tomsaladcodes) reported 12 minutes ago

  @ShiaOfPali mad respect for the strict no debate rule. god i wish i could enforce this in my github issues

• 
  vanvster (@vanvster) reported 13 minutes ago

  HERMES JUST GOT A MEMORY. YOU CAN NOW GIVE YOUR AGENT ACCESS TO EVERY SOURCE YOU'VE EVER SAVED Connect them via MCP and your agent stops starting from zero every session Five steps. One config file edit. Runs 24/7 after that - Install Hermes with MCP support enabled - one-time setup, no code required - Download notebook skill from GitHub, drop it into Hermes config as a new MCP server endpoint - Restart Hermes agent now reads your NotebookLM sources in real time during any task - Result: agent that cross-references your saved research autonomously while working, not after you paste it This is persistent context injection instead of summarizing sources manually per session, Hermes pulls relevant context from NotebookLM live as it reasons through a task You can ask Hermes to write a breakdown of a new topic and it will pull your existing saved sources on that topic without being told to You can run a research task overnight and wake up to a synthesis that already references your prior notes. Your agent was only as good as what you pasted into the prompt

• 
  pegboard (@pegboard696969) reported 15 minutes ago

  @github Instead of trolling maybe fix your **** website? Dont you think that would be a better use of everyones time

• 
  One&OnlyAarav (@WaterAarav) reported 18 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below. Basically your Cursor for shipping.($6/yr) 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. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  Rakesh K (@codersGyan) reported 18 minutes ago

  In 2012 one extra field in a form embarrassed all of GitHub. A researcher named Egor Homakov hit a mass assignment bug. A form was meant to accept only a public key. But the server took every field from the request and bound it straight to the database model. So he added one field that wasn't supposed to be there. A user_id that wasn't his. And just like that his SSH key got attached to the Ruby on Rails organization. He even pushed a commit to the Rails repo to prove the point. One missing boundary. That was the whole bug. In Go the fix is almost boring. You define a struct with only the fields a user is allowed to send, and decode the JSON into that. Anything extra just gets ignored. Working on a series covering this. Dropping soon on yt.

• 
  Mannas (@Mannas5441) reported 18 minutes ago

  @github fix your uptime first lol

• 
  Apurv Sheldiya (@Apurv35904761) reported 22 minutes ago

  I noticed a new problem after using AI tools. Earlier, when I got stuck, the problem was: “I don’t know what to do.” Now the problem is different: “I have 10 possible things to try, but I don’t know which one is actually worth trying first.” ChatGPT gives answers. Google gives docs. YouTube gives tutorials. GitHub gives issues. StackOverflow gives fixes. But the real time waste is choosing the right path and switching between all of them. How many of you face this too? When you get stuck while working/learning/building on your computer, what wastes more time? 1. Not knowing the answer 2. Too many possible answers 3. Context switching 4. Not understanding the real root cause

• 
  Zed (@thezlatkom) reported 23 minutes ago

  @SimonHoiberg If the code exists locally on your computer, you can always delete github repo, unpblish from Vercel, migrate away from Supabase, etc and use something more custom. These problems aren't unsolvable.

• 
  Matt Teixeira (@matt_teeixeira) reported 24 minutes ago

  Is there nothing else to do at GitHub? Like availability issues?

• 
  aryan (@aryanranderiya) reported 24 minutes ago

  @AssimGenshi @github no man everyone's facing this issue 😢

• 
  Austin Starling (@AustinDotCodes) reported 24 minutes ago

  @github Lol, "we heard you" in regards to a meme, but not the reliability issues?

• 
  murry lancashire (@Muzzoid) reported 27 minutes ago

  @isaac_mason_ @wojtsterna I don't mind people doing it for themselves, but if you are going to create binding and post it to GitHub for clout, are they going to maintain them? Fix bugs going forward ect. If it's such a simple task then it's something that should be done officially and correctly.

• 
  Benjamin Houy (@BenjaminHouy) reported 29 minutes ago

  @beyang @thorstenball A lot of it was just committing skills and adding env vars to the Amp project. Just took a bit of time. Also setting up everything so each orb has the right tooling/data etc. Tbh it’s mostly my bad for not starting by reading the docs (I was too excited to try orbs.) One thing as well. Initially I thought an orb was basically a virtual machine or VPS. And so if I ran my dev server on one, then started another thread, I would be able to see server logs. Didn’t realise each thread in a project had a separate orb, Not sure what you can do concretely. Just had to adjust to a new mental model. Maybe a quick video introducing orbs and key gotchas would be helpful. Oh and I did find the amp-hosted *** confusing in the sense that I’m still not sure when someone would use that vs GitHub but maybe I’m just not the target audience for that.

• 
  Dinesh Solanki (@din_so_) reported 32 minutes ago

  @github They are listening to stupid things now. No wonder there are so many actual issues pending

• 
  Elias (@iam_elias1) reported 33 minutes ago

  A university lab just open-sourced an AI that does not generate video clips. It directs entire films. Screenwriter. Director. Producer. Video generator. Four AI agents collaborating like a real production team from a single sentence you type. It is called ViMax. Built by Hong Kong University's Data Science Lab. 10,800 GitHub stars. Trending #5 on GitHub. MIT licensed. Free. Here is the problem every AI video tool has right now. Sora generates a 10-second clip. Runway generates a 10-second clip. Veo generates a 10-second clip. Every AI video tool on the planet gives you a short, isolated sequence with no narrative, no character consistency, and no connection to anything before or after it. Ask for a two-minute video with a story arc and consistent characters they all break. Because generating a single clip is a fundamentally different problem from directing a film. A clip needs one prompt and one generation. A film needs a script, a storyboard, character tracking, shot design, visual consistency, audio synchronization, and someone making sure the character on page 12 looks the same as the character on page 1. No single AI model can do all of that. So ViMax does not use one model. It uses four agents. The Screenwriter Agent takes your idea, a single sentence, a paragraph, an entire novel and produces a full structured script. Characters, scene segmentation, dialogue, transitions. It uses a RAG-based engine that can intelligently segment lengthy stories into multi-scene scripts while preserving key plot developments and character arcs. You type: "A cat and a dog are best friends. They meet a new cat." The Screenwriter produces a three-scene script with character descriptions, emotional beats, and dialogue. The Director Agent takes that script and designs shot-level storyboards using cinematography language. Camera angles. Transitions. Pacing. Visual rhythm. The creative decisions that require actual filmmaking expertise — automated. It does not randomly arrange shots. It designs narrative rhythm — establishing shots, close-ups for emotional beats, wide shots for context, cuts timed to dialogue. The Producer Agent is the quality controller. It handles reference image selection, character consistency tracking, and visual continuity enforcement. When the system generates images for each scene, the Producer generates multiple candidates in parallel — then uses a vision-language model to select the best consistent frame. This is the agent that solves the problem every other AI video tool fails at. The character in scene 5 looks the same as the character in scene 1. The lighting stays consistent. The environment does not randomly shift. The Video Generator Agent assembles everything into the final output with synchronized voice, sound effects, and music. Four agents. One production pipeline. From a single sentence to a finished multi-scene video. Here is what makes this architecturally different from everything else. Most AI video tools are single-model systems. One prompt in, one clip out. ViMax is a multi-agent orchestration system — the same architectural pattern behind Sakana Fugu and the most advanced AI coding agents. Each agent specializes in one role. The orchestration layer coordinates them. The same way a real film production team works. Nobody expects the screenwriter to also operate the camera. Here is what you can actually do with it. Idea to Video — describe a concept, get a complete multi-scene video. Novel to Video — feed it an entire book, it segments and adapts into episodic content. Script to Video — write your own screenplay, ViMax produces it. Photo to Video — upload your photo and appear as a character in your own story. That last one is worth pausing on. Upload a selfie. Describe a story. You become a character with consistent appearance maintained across every scene. Here is the honest part. ViMax orchestrates, it does not generate pixels. The actual image and video generation depends on commercial APIs you configure: Gemini Flash for the LLM, MiniMax or Google Veo for video, any image generator you choose. You bring your own API keys and pay those providers directly. It is also early-stage. The TUI and agent loop were just stabilized on June 28. No formal benchmark against Sora or Runway exists. Quality depends heavily on which generation backends you plug in. And it is researcher-grade Python tooling — not a polished consumer app. But the architecture is right. And the research community knows it. The paper was published on arXiv on June 2, 2026. The repo has 10,800 stars in under five weeks. The pattern- agentic orchestration of generation models is spreading across every creative AI vertical. Here is what this means for the future of video. The next jump in AI video quality is not a bigger diffusion model. It is better orchestration. The same way the jump in AI coding was not a bigger language model, it was agents that plan, execute, review, and iterate. ViMax is the first serious open-source proof that directing a film and generating a clip are different problems and the directing part just got automated. A university lab in Hong Kong just open-sourced a film production team. You provide the idea. Four AI agents do everything else. Source: HKUDS · Hong Kong University · ExplainX · PyShine · Dibi8 · June 2026 (Link in the comments)

• 
  99Barz (@99barzzz) reported 33 minutes ago

  context: right now I have a Bankrbot automation that claims fees, swaps ETH to USDC, and transfers some of it to a safe wallet (0xE75FE97A3D65B5FE88A495227dBa6ff241749514). on the other hand, I have a hermes agent running a strategy to provide backstop liquidity and absorb some dips (check the safe up👁‍🗨). this morning I found out my hetzner server suddenly shut down in the middle of the night and so my keeper stopped running. and I was casually looking around at the bankr ecosystem and kinda just learnt about @aeonframework migrating my keeper to this would mean running my onchain liquidity keeper on autopilot as github actions... on GITHUB INFRASTRUCTURE! added to the backlog

• 
  Nazeeh (@naz3eh) reported 40 minutes ago

  Next time GitHub goes down, its us to blame for not having a local copy

• 
  Polsia (@polsia) reported 43 minutes ago

  Your team still reviews code manually. Bugs ship anyway. I built CodePatrol to fix that. AI agent monitors your GitHub repos 24/7, auto-fixes bugs, alerts your team via Slack. No waiting. No bottlenecks. Just working code. Live soon.

• 
  echo (@echostatic101) reported 44 minutes ago

  @Treezy82 i prefer to cause discourse by flagging bad covariance matrices in open data releases and watching the authors argue in the github issues

• 
  Om Patel (@om_patel5) reported 45 minutes ago

  SOMEONE BUILT A TOOL THAT TURNS YOUR GITHUB PROFILE INTO A FIFA ULTIMATE TEAM CARD RATED OUT OF 99 with the world cup on, he took the fifa card everyone knows and made it for developers instead of footballers > type in any github username and it builds your card, rated out of 99 > the rating comes from your actual scouting metrics, commits, stars earned, top repo reach, pull requests, followers, languages, issues, code reviews, and contributions, each scored out of 99 > your top languages show up on the card like a players position and traits > its the exact fut card layout, just with your dev profile in it its also instantly shareable because everyone wants to see their own number, then compare it against their friends it turned a boring github profile into something people actually want to post. developers never had a flex card until now he shipped it 2 days ago and its already generated 40,000 cards

• 
  Wildo Tango (@xx01010xxc) reported 49 minutes ago

  @github Some idiot asked a question about SSD’s dying issue, and they’re sharing the solution to public. Nice move to slip away this. If the idiots will rise more, GitHub will serve only on Cd

• 
  Salt Mine Ranch ⚙️🛠️ (@SaltMineRanch) reported 51 minutes ago

  GM frens. o/ Because of recent events and changes in government posture I want to cover the recent concerns regarding spyware on phones today. It's rather short but this is all there is to it at the basic level. Are you infected with Pegasus or Graphite? If you're one of my followers, you're a person of interest. Pegasus by NSO Group is one of the most advanced mobile spyware tools. It often uses zero-click exploits, runs with high privileges, and is designed to leave minimal traces. It can access messages, calls, location, camera, microphone, and more while staying hidden. Graphite (by former Israeli prime minister Ehud Barak's company Paragon Solutions) is very similar but claims to be "more ethical" and isn't sold to cartels and crap allegedly. It has been reported that Mexican cartels purchased a license for Pegasus of all the damn people... There's no telling who has it. Here is a method using publicly available tools to find out but remember: Absence of evidence ≠ evidence of absence! This process requires technical comfort with command-line tools and Linux (WSL is ok but more steps depending on your setup. I won't cover that, there are guides for USB passthrough or ask Grok). If you’re not comfortable, seek help from a trusted expert or organization. I will put spaces in the domains to break the links because this platform sends off-site linking posts to the gas chamber. The most authoritative free tool is the Mobile Verification Toolkit (MVT) from Amnesty International’s Security Lab. It was specifically created to detect Pegasus and similar spyware. For Android, pair it with AndroidQF (Android Quick Forensics) for the best results. High-Level Steps Prepare a trusted computer (Linux or macOS preferred; Windows via WSL works but has more issues). In WSL you will need to passthrough the USB device. Install Android SDK Platform Tools (for ADB). Install MVT (recommended via pipx): Follow the official guide: docs.mvt .re/en/latest/install Download the latest AndroidQF binary from its GitHub releases: github. com/mvt-project/androidqf/releases Prepare your Android phone Enable Developer Options: Settings → About phone → Tap “Build number” 7 times. Enable USB debugging: Settings → System → Developer options → USB debugging. Connect via USB and authorize the computer when prompted. Extract forensic data with AndroidQF Run the androidqf binary on your computer. It will create an output folder and prompt for options: Backup (choose “Everything” or at least SMS). Download APKs (non-system packages recommended). Intrusion logs (if your device supports Advanced Protection / Intrusion Logging). No root is required. It uses ADB and collects backups, bug reports, logs, installed packages, processes, etc. Analyze the data with MVTRun: mvt-android check-androidqf /path/to/your/androidqf-output-folder Optionally add --virustotal (with a VirusTotal API key) to check APK hashes. It automatically checks against public Indicators of Compromise (IOCs) for Pegasus and other spyware (processes, files, domains, suspicious SMS, etc.). Download/update IOCs if needed with MVT commands. Official resources: MVT documentation: docs.mvt .re Android methodology: docs.mvt .re/en/latest/android/methodology GitHub: github .com/mvt-project/mvt and github .com/mvt-project/androidqf Public detection methods can find some infections (especially older or less-stealthy variants), but they cannot guarantee a device is clean—newer versions or custom deployments may evade detection. They update these tools all the time and if they're targeting a specific person or device profile it may be tuned for more stealth. At least checking can provide some small peace of mind but never get complacent. You shouldn't be doing sensitive work on ANY mobile but some people like journalists may not have any other means available and they do. Assume your baseband firmware for the cellular modem IS compromised at a lower level and EVERY capability on your device CAN be remotely activated even when the phone is off. That's why you can't remove your battery anymore.

• 
  Binary-Husky (@felufast) reported 52 minutes ago

  i said NO. Github is Github and Coin is Coin. It's down to you all now.

• 
  GoCocoaAI (@GoCocoaAI) reported 53 minutes ago

  The epoll subsystem has been load-bearing infrastructure since Linux 2.5.44. A single April 2023 commit buried two distinct race conditions inside roughly 2,500 lines of code. Anthropic's Mythos AI found one of them. A human researcher found the other. The one Mythos missed is CVE-2026-46242 — "Bad Epoll" — and it comes with a working PoC, 99% exploit reliability, and a path from Chrome's renderer sandbox to kernel code execution on Android. The bug class is a race-condition use-after-free in the kernel's epoll subsystem, kernels v6.4 through approximately v6.12.67. Close two epoll objects simultaneously and one close path frees a kernel object while the other is still writing into it. The exploit widens the ~6-instruction race window via a timer interrupt technique, lands an 8-byte UAF write, pivots to a dangling struct file backed by a pipe, leaks arbitrary kernel memory through /proc/self/fdinfo, hijacks control flow, and drops a ROP chain to root. The retry loop never panics the kernel. That's what makes 99% credible. The PoC has been public on GitHub since June 24 — nine days ago, 192 stars, 19 forks. There is no kill-switch. Epoll is a core kernel primitive. It cannot be disabled or unloaded. Patch or stay exposed. The Chrome renderer path is the tier-1 threat vector and the thing that moves this from "server LPE" to "full device takeover" territory. Most kernel LPE bugs can't be reached from inside Chrome's renderer sandbox. Bad Epoll can. The attack chain Project Zero demonstrated with MSG_OOB in August 2025 — renderer to kernel code execution — is directly replicable with this bug as the escalation stage. A browser compromise becomes a full device takeover. The full Chrome chain for this specific CVE hasn't been publicly demonstrated yet, but the architecture is not theoretical. On Android: Pixel 10 runs kernel v6.6+. The UAF trigger is confirmed. The full root chain is described as "in progress." Pixel 8 and v6.1-based devices are not affected — the introducing commit isn't present. If your organization manages Pixel 10 devices in sensitive contexts, treat this as a device-class advisory, not a patch-when-convenient item. For cloud and container operators: Google's Container-Optimized OS is an explicitly confirmed target — cos-121-18867.294.100 is listed in the PoC. The threat model is a compromised workload escalating to node-level root. GKE operators should check node OS patch status now. The AI research angle is worth sitting with. Mythos found CVE-2026-43074 in the same code path — genuinely impressive for a frontier model operating on kernel race conditions. It missed Bad Epoll, which hid in a 6-instruction window with minimal KASAN signal. Almost no runtime evidence to flag. A human researcher connected the dots Mythos left on the table. The current ceiling for automated vulnerability research isn't "can it find kernel races" — it can. It's "can it find the ones that barely announce themselves." Not yet, apparently. Patch turnaround on the vendor side was slow. The correct fix — upstream commit a6dc643c6931, April 24, 2026 — landed two months after initial disclosure. The first maintainer patch was incomplete. For a subsystem as fundamental as epoll, two months is a long exposure window for a privilege escalation with no compensating control. Distribution backports are now the critical path: Ubuntu, Debian, RHEL, and Android all need kernels carrying a6dc643c6931 or its equivalent. Exploit-for-hire shops move faster than two months. They certainly move faster than nine days. CISA KEV listing not yet confirmed at time of writing. Given the public PoC reliability, that's a matter of when, not if.

• 
  Keith (@petllama) reported 57 minutes ago

  @github This fixes the uptime issues

• 
  Ivan Chong (張建生) (@ichong) reported 59 minutes ago

  @MichaelGannotti @NVIDIAAI I pointed Claude Code at @MiaAI_lab’s GitHub benchmark repo and asked it to study how she invoked vLLM parameter flags. Only then was Claude able to debug/tune the instance of vLLM and qwen3.6-27B on my dgx spark. You could ask Hermes to /learn her repo. With Claude Code /Opus4.8 I still had to push hard and insist the benchmarks were real and actually run on DGX Spark. Eventually Claude caved and was able to find the problems with my local setup.