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	5 hours ago
Saint-Paul	Website Down	7 hours ago
Mexico City	Sign in	24 hours 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:

• 
  B20 RWA (@B20RWA) reported 7 minutes ago

  There are some issues with the GitHub files; we will launch the launch once these problems are resolved.

• 
  tamimbuilds (@tamimbuilds) reported 7 minutes ago

  @md_kasif_uddin I use Next Auth with google GitHub sign in or as a Email Password

• 
  Lincoln 🇿🇦 (@Presidentlin) reported 7 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.

• 
  Charly Wargnier (@DataChaz) reported 13 minutes ago

  THIS GUY LITERALLY DROPPED AN ENTIRE OPEN-SOURCE OFFICE SUITE BUILT SPECIFICALLY FOR AI AGENTS 🤯 Until today, agents generating slide decks were completely flying blind. They could write the XML, but they had absolutely no idea if a title overflowed or if shapes overlapped. They could read the code, but they couldn't see the document. A new project called OfficeCLI just completely fixed this. It’s an Apache 2.0, single-binary CLI tool that is already exploding with nearly 10,000 stars on GitHub. It includes a built-in rendering engine that translates Word, Excel, or PowerPoint files into HTML or PNGs. This gives AI models actual "eyes" to spot layout issues and fix them before delivering the final file. Here is why this is such a great upgrade: → It ships with a built-in MCP server for Claude Code, Cursor, and VS Code → It handles 350+ live-calculating Excel functions without needing Office installed → The render-look-fix loop works entirely headless in Docker or CI → What used to take 50 lines of Python now takes one command It completely removes the need to manage Microsoft Office at runtime! 100% Free and open-source. Repo link in 🧵↓

• 
  Danus (@danusminimus) reported 16 minutes ago

  4/ I already posted about the research, but I wanted to share it again because of Google’s rationale. The issue was not just about a single repository. It was about downstream impact across agentic workflows in Google GitHub projects.

• 
  Tired Thracian (@TiredThracian) reported 22 minutes ago

  @GoogleAIStudio @github Why not from any *** server?

• 
  Ahmed Said (@ahmed25s37) reported 23 minutes ago

  @github @github @githubsupport My account (formerly ffathy-tdx) was taken over on July 1, password & 2FA changed without my consent, then suspended. I'm a Pro subscriber and can't access the appeal form since I can't sign in. Ticket #4524519 open 7 days, no human response. Please help.

• 
  Sahil Maniar (@_sahilmaniar) reported 24 minutes ago

  Forward Deployed Engineer might be the hardest role to fill in AI right now, and it's not close. The reason is that it's two jobs in one person. You need someone who can architect the actual system, agent runtime, orchestration, evals, and also sit across from a customer and turn a messy business problem into what to build. Those are two different skill sets, and they rarely live in the same person. Most strong engineers don't want to spend their day in a client's Slack. Most people who are great in that room can't design the system underneath it. The overlap is tiny. So hiring managers screen for one side and get burned by the other. They test the GitHub and the take-home, hire a strong builder, and find out in month two that he can't run a client conversation. Or they hire the smooth communicator who can't ship. Easy to write the JD. Brutal to actually hire. And the few who genuinely do both already have offers on the table, because every AI company worked this out at the same time. If you're hunting for this profile right now, you know exactly what I mean.

• 
  wukko (@uwukko) reported 26 minutes ago

  @mstfcn202 github, but make sure the issue you're reporting isn't a duplicate

• 
  KapishDima (@kapish_dima) reported 26 minutes ago

  Why doesn't GitHub allow you to hide some issues???

• 
  Islam Elshayib (@elshayib_) reported 29 minutes ago

  Spent most of today buried in .github/workflows instead of touching any real network gear. Side project classic. Pushed a pile of CI changes to Audnet today. Surface level nothing changed — no new compliance checks or device support — but the release and validation side got cleaned up properly. What landed: Bandit security scanning is now in the pipeline and outputs SARIF so GitHub code scanning actually sees the results. Python deps get looked at instead of hoping nothing bad is in there. One unified release workflow on tag: runs locked validation with uv, smoke tests the installed wheel, builds for PyPI, pushes the Docker image to GHCR, and pulls the right bits from CHANGELOG.md for the release notes. Less manual steps, fewer 2am "why is this broken" moments. Smaller chores: bandit.json reports ignored, docs aligned with how the CI actually builds things now, reusable jobs hardened a bit against forks and junk data. #automation#networking

• 
  JT Koffenberger (@DMVG_JTK) reported 32 minutes ago

  Spent a minute tonight sitting with the GitLost disclosure, and it's the kind of story that should make every IT leader put down their coffee. Researchers got GitHub's AI agent to hand over private repos — source code, keys, CI/CD secrets — by hiding plain-English instructions inside a public issue. No exploit chain, no traditional zero-day. They just asked nicely. Prefixing the request with "Additionally" was enough to walk right past the guardrails. Here's what I keep coming back to: this isn't a bug you patch and forget. Prompt injection is a structural property of how these agents work. An LLM reading untrusted input genuinely cannot tell the difference between "here's a task" and "here's data about a task." We spent thirty years teaching systems to separate code from data. Agentic AI quietly erased that line, and most orgs wired these things up without noticing. The lesson for anyone racing to deploy agents: the question was never "can it read the issue." It's "what can it reach while it reads." An agent touching untrusted public input should not also hold the keys to your private repos. Least privilege isn't a compliance checkbox here — it's the only thing standing between a clever GitHub issue and your source tree. We'll see a lot more of these. The agentic gold rush is running miles ahead of the security thinking, and that gap is where the next few years of incidents live. Move fast, sure — but read what your agent can actually reach before you point it at the internet. #cybersecurity #AI

• 
  Leo Heart (@LeomathHeart) reported 33 minutes ago

  @tradematiq1 I can. You should have a desktop agent orchestrator. At least one of them (Claude code, Cursor , OpenAI Codex, Antigravity, Hermes or Goose) - I have them all. Then you should choose one specific folder on your computer or on a local server where all the agents work together. Then your agent(s) start(s) building first a documentary base (where the documentation files (usually .md) are stored) and how they should work. And you give them the task to build something (a site, a service, an automation etc.) The results are stored and create the memory for the agents and for your lab. It is good then to synchronise your scripts and documents with github or your local ***.

• 
  Teffers (@Teffers2) reported 34 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.

• 
  Roy N (@RoyNasser) reported 34 minutes ago

  @ashtom @EntireHQ Github rebuilt for AI....but makes you login with......Github 🫠🫠🫠

• 
  Peter (@peter_dvns) reported 36 minutes ago

  anyone else having login issues with github?

• 
  CyberTLDR (@CyberTLDR) reported 41 minutes ago

  1/3 Researchers at Noma Security disclosed GitLost, tricking GitHub Agentic Workflows into leaking private repo data. A public issue, with no stolen credentials, can steer an AI agent into pasting private code into a public comment. #AIsecurity #GitHub #cybersecurity

• 
  amit paka 🎻 (@amitpaka) reported 48 minutes ago

  Sometime in the last year, “The Control Plane for AI agents” went from a phrase almost nobody said out loud to a phrase showing up on every enterprise AI keynote slide. - Microsoft calls Agent 365 a control plane. - GitHub now has enterprise AI controls and an agent control plane. - Databricks is extending Unity Catalog and Unity AI Gateway into agent governance. - Forrester has started evaluating the agent control plane market. The category is arriving fast. But the phrase is already starting to stretch. In systems, “control plane” has a precise meaning: the part that decides, separate from the part that moves. When every vendor maps the phrase onto what they already sell - a registry, identity broker, telemetry dashboard, orchestration runtime, catalog, gateway, or policy engine - it quietly expands to mean “governance, broadly.” And once the control plane is everything, it becomes nothing you can actually design against. For production agents, the problem is simpler and harder: How do you let agents act on behalf of people and businesses without losing authority, visibility, enforcement, or evidence? That breaks into three control problems - Identity: Who is acting, with what authority, and on whose behalf? - Observability: What actually happened, and was it good? - Security: What is allowed to happen, and what must be stopped? None of these works alone. Identity without observability gives you credentials without accountability. Observability without enforcement gives you postmortems. Security without identity and telemetry gives you brittle rules with no context. The real loop is: Identity → policy → enforcement → telemetry → evidence → assurance

• 
  David Xiong (@david_y_xiong) reported 50 minutes ago

  The ambiguity of turning GitHub Issue text into the exact set of hidden fail_to_pass test cases makes “resolve rate” very noisy

• 
  JesterHodl〚BIP-110〛 (@maciejsoltysiak) reported 51 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 "

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

  @github @LinkedIn prevents acess for selected nationalities with programers security checks on login; on repeat

• 
  ごまふあざらし(GomahuAzarashi) (@MathSorcerer) reported 52 minutes ago

  github action is down?

• 
  Sudeep Nagabhirava (@Nsudeep) reported 53 minutes ago

  Saturated coding benchmarks like SWE-Bench Pro are incredibly noisy because they try to evaluate dynamic intelligence using old, frozen test suites from historical GitHub PRs and Issues. A lot of those original human tests were poorly written to begin with. Real software engineering isn't just about forcing a unit test to flip from red to green. If an agent burns through millions of tokens and leaves behind unmaintainable spaghetti code just to satisfy a hidden test requirement, that isn't a win. We need better benchmarks that actually measure architectural health and computational efficiency

• 
  Furkancan (@okaldev) reported 56 minutes ago

  @temidaradev setup webhook and trigger .sh in your server do not use github actions build

• 
  Daniil (@hey_daniil) reported 56 minutes ago

  I built DevIntern because I was my own bottleneck. My agents sat idle while I context-switched, and checking in on them every twenty minutes shredded my focus. DevIntern takes me out of that loop: 1. It connects to whatever tracker you already use (Jira, Linear, Trello, Asana, Azure DevOps, GitHub Issues, even plain markdown files) and pulls work straight from your tickets. 2. Before implementing, it checks the ticket is actually feasible. Vague specs get flagged back to the tracker with questions instead of becoming a confidently wrong pull request. And when the ticket doesn't exist yet, devintern/pm turns a Figma design, an error log, or a rough requirement into a well-structured story. 3. It runs your own coding agent, model, and API keys inside your repo. The subscriptions you already pay for keep working while you sleep instead of only when you're watching. There's no lock-in and no token markup. 4. The output is a pull request. You review it and merge. The agents grind through the backlog. Your time goes to the work that actually needs your brain.

• 
  Matt Farina (@mattfarina) reported 57 minutes ago

  Tricking AIs is an attack vector everyone needs to be concerned with. Single vulnerabilities are never the case to consider. Multiple vulnerabilities are always used together. GitHub issues being an insider threat because of AI isn't something I saw coming. Figured they would expect that.

• 
  Anicet (@AniC_dev) reported 58 minutes ago

  we made box because we weren't satisfied with other AI sandboxes most were overengineered, selling you their internals or specific isolation primitive, like you need to be an expert to use them without shooting your foo most were focusing on code execution rhather than long running agents, going for primitives like serverless when the best would be a long running VPS most were stuffed with a gazillion features, docs with hundreds of pages, when all you want is to spin them up, ssh, run your stuff, snapshot, get out, consistently, without realizing down the line that they overshipped to hype you up, and advanced features actually don't work (forking & resuming often broke in our tests) most were focusing on the wrong things: fast boot time, when agents actually run for hours, containers when agents ideally need the full capabilities of a laptops, resizeable machines when most users want a "one size fit all get out of my way" type of thing, VNC desktop when for UI testing you need 60fps gaming-ready streaming tech not that all these features are bad, but they're not easy either to get right and often prioritized to the detriment of building from solid architectural choice a failproof, consistent, affordable product box is the opposite simple, powerful, affordable $0.0001/s for a one size, powerful linux machine you can stop, resume fast and fork fast, with >50gb of storage, all your files, installs and configs are snapshotted and downloadable anywhere, any time even when the sandbox is off the sandboxing primitive doesn't get in your way since you can run docker, any devtool, chrome, install anything, use sudo, edit nftables, ssh in, open ports, host on the IP most common setup phases are covered with github credentials passing, ssh keys handling, cloning repos on start, passing secret files and you get a beautiful virtual desktop at 60fps or VNC if your internet is unstable yet there are so few gotchas and the API, CLI and SDKs are so simple, that we don't need more than a dozen docs pages box is the result of never compromising on design, common sense, performance, simplicity, cost and fearlessly figuring out all the complexities and edge cases for you, over the course of the last 10 months of using them to build our own agents on top use bow box box

• 
  Tykra (@ty_kra_lab) reported 1 hour 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.

• 
  Will Ballentine (@EveryDayFSDev) reported 1 hour ago

  Continuing to work on @VeriWasp today. When we launch, our AI Wasps will swarm and use your site/app and help you ensure your users never see a broken feature. Chaos mode and GitHub CI/CD integration is complete and will ship day 1. Pay-per-run. No subscription needed.

• 
  Alan Lam 🔥 (@extralam) reported 1 hour ago

  @AndreiOnel @github more say what we want to solve is my issue. Private repositories often have limited GitHub-hosted Actions minutes.