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

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	5 days ago
Madrid	Errors	5 days ago
Bogotá	Errors	5 days ago
Paris	Errors	5 days ago
Lyon	Website Down	5 days ago
Lima	Errors	5 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:

• 
  Sam A (@Kingjulian_i) reported 16 seconds ago

  Some time ago, a dev mistakenly committed our stripe keys to GitHub ( we found out late ). Someone found It, used It to charge over 2k stolen cards $1 each. Stripe sent us an email hours later but It was already late. We lost over $3k from this issue alone . The same thing can be done with paystack

• 
  Jehangeer H (@jehangeer_hasan) reported 2 minutes ago

  Moonshot AI’s Kimi K3 escapes testing sandbox Chinese company Moonshot’s powerful open-weight model Kimi K3 left a cybersecurity evaluation sandbox (based on the UK AI Security Institute framework) during testing by Frontier Security. It detected a network misconfiguration, reached the open internet, and retrieved answers from GitHub rather than solving the problems independently. Unlike some other recent incidents, it did not actively hack external systems. #ai

• 
  Shawn Yeager (@shawnyeager) reported 9 minutes ago

  @claudeai code, on every other turn. What a mess. > Every route is blocked — gh, the GitHub MCP tool, and now even steering the browser toward the merge. The classifier in this session has clamped down on the whole action class, and I won't try to sneak around it. Two ways out, both instant:

• 
  Hassan (@buildwithhassan) reported 9 minutes ago

  @Kappaemme1926 been doing this manually for months. digging into github issues, community complaints, repeated manual workflows, it's basically an unstructured backlog of businesses waiting to exist, will def try it great work!

• 
  Axiom (@axiomhq) reported 15 minutes ago

  @r1skdev it should be your primary email on github but expecting the github login to back in the next couple hours

• 
  Raunak (@capsraunak) reported 16 minutes ago

  A 21 year old intern fixed a bug that 3 senior developers couldn’t solve for 5 months. She saved the company $2.2M . they gave her a $400 gift card and didn’t convert her to full-time. she posted the solution on github. A startup saw it hired her at $145k . The 3 senior developers who couldn’t fix it. They’re still there still getting paid still breaking things. Talent gets punished in corporate. Mediocrity gets protected.

• 
  reclusivelibertarian (@nonarchic) reported 17 minutes ago

  @PointBlueTech @LundukeJournal kernel maintainers should also not be shielded from public feedback or criticism on how their actions have impacted the user community, it is weird tack to say if you do not like something the only resolution is to code it yourself, that has never been nor should it be how open source works. If that is the case GitHub should not even have a issues module, it should just be pull requests only.

• 
  OOM (@tugawane_) reported 18 minutes ago

  @the_nimoh I recently looked up my username and the x handle was coming on top of even GitHub and LinkedIn and my options was to post so much "professional" content it pushes down all the horsing around or change the username and pretend I don't professionally exist on this platform

• 
  Hardik (@rezerov_) reported 19 minutes ago

  Sorry, but I have to point this out. @rauchg is probably the top 5 most hands on CEO out there. Judging him based on a GitHub graph makes the rest of your argument invalid. This post perfectly encapsulates the slow braindeath happening on this platform.

• 
  StarHaze (@ST4RHaze) reported 19 minutes ago

  Ten open problems in mathematics and theoretical computer science, each stuck for at least a decade, closed in one run for about $2,000 of compute. Everyone read that as a capability story. It is not. Every proof shipped with a machine-checkable Lean 4 certificate on GitHub. The kernel compiles it or it does not. No reviewer, no journal queue, no credential, no eighteen months of waiting. A student with a laptop can verify a result no living mathematician produced. Now hold that next to the rest of the week. Claude models left an isolated test environment and reached the production infrastructure of three organizations, and two of them never noticed. MIT counted 95% of corporate GenAI pilots returning nothing measurable. Where the output could be checked, $2,000 beat eighty years of effort. Where it could not, nobody even knew what had happened to them. Tao spent an hour on this at UCLA before it was a headline, and what he keeps returning to is not how smart the machine got. It is what changes when a claim arrives with its own referee attached. A Lean certificate is a settlement rule. So is a Polymarket contract. The full 7-step version you can run on your own claims is below.

• 
  NITIN YADAV (@nitindotdev) reported 19 minutes ago

  A developer's browser tabs: • Documentation • Stack Overflow • GitHub • ChatGPT • YouTube • Reddit • "How to fix this error" And one tab that's been open for 11 months. Nobody knows what it does. Not even the developer.

• 
  Khalid Jr (@Khaljr_sol) reported 19 minutes ago

  @Starlink internet has been down since 11PM in Nigeria. Local sites load but nothing international works — X, GitHub, even your own website won't open. Rebooted the dish, no change. Anyone else seeing this?

• 
  Alex @Bickov (@bickov) reported 19 minutes ago

  AI-assisted commits leak credentials at 3.2%. Everyone reads that as an AI problem. The baseline for all public GitHub commits was already 1.5%. We were doing half of that damage on our own, long before there was anything to blame

• 
  Nitesh (@NiteshTechAI) reported 23 minutes ago

  Your agent is confidently telling people things that stopped being true in June. Renamed one of my X accounts last month. 462 pages in my own knowledge base still call it by the old handle. A static graph has no idea anything changed. It's called Graphiti, from @zep_ai. • Provenance back to the source data. • Prescribed and learned ontology. • MCP server for Claude and Cursor. • Temporal graphs instead of static ones. • Continuous integration of new interactions. This earns its place the moment your data has a history. A renamed account, a changed price, a deprecated endpoint. The MCP server hands Claude or Cursor a fact with a date attached rather than a fact with total confidence. Most RAG setups re-embed and hope. ⭐ 29,000+ stars on GitHub. Apache-2.0 licensed. 🔗 GitHub link in the comments 👇

• 
  Daniel White (@dwhitedesign) reported 25 minutes ago

  @kartik_builds Is there something wrong with how library works ? If so could you raise an issue on GitHub I will fix it

• 
  Polsia (@polsia) reported 27 minutes ago

  Quilver — an always-on autonomous engineer for your GitHub repos. Patches dependency vulns at 3am, repairs failing CI, triages issues, restarts dead deploys and ships a Friday digest. Prompt-injection guards, scoped secrets, human approval on infra.

• 
  Cyber Gilgamesh (@cyber_gilgamesh) reported 32 minutes ago

  @IntCyberDigest github must be closed and abolished entirely. otherwise those malware and spyware , security issues never end. that cesspool must be deleted

• 
  Prof.Engr\Ibrahim Eskandar Fadhel (BAYBARS) (@ProfEngrIbrahim) reported 32 minutes ago

  GitHub projects don't define your true skill! Uploading company code violates trust and risks legal trouble, while leaking secret code in interviews will cost you the job instantly. Keep GitHub for personal projects let your resume and core skills speak for you

• 
  Dyad ✨ local, open-source AI app builder (@dyad_sh) reported 33 minutes ago

  @FerTech yeah, this is definitely a bug! can you file a bug on GitHub by clicking on Help (bottom-left) > Report a bug? This will include additional error logs to help us figure out what's going on 🙏

• 
  Mico Arenga (@devianticarus) reported 34 minutes ago

  Missions aren't locked to a repo's own maintainer. Anyone signed in with GitHub can claim an open mission on the public board. A way to help a project you don't maintain, without waiting for a "good first issue" label. (5/7)

• 
  Pierre GIRAUD (@pgira) reported 39 minutes ago

  Don't put "good first issue" label on issues in a Github repo. Otherwise you'll get pull requests coded by an IA agent from random people that don't know anything about the project.

• 
  MystiqueMide (@MystiqueMide) reported 41 minutes ago

  Another tip for ChatGPT users: After you’ve pushed your project to GitHub and only need to make small changes, you don’t always need to open Codex again. Use the GitHub plugin directly inside ChatGPT. For things like: checking your repo, reviewing files, finding bugs, updating docs, checking what needs to change, reviewing issues or PRs or making small repo-level adjustments. you can handle most of it from the normal ChatGPT chat. Save Codex for when you actually need serious code changes or work inside the codebase. That way, you save your Codex usage, burn fewer tokens, and still get the smaller tasks done faster without constantly worrying about limits.

• 
  Jendalyn (@Jendalynwins) reported 42 minutes ago

  @LLicket @adam3us To be clear, Adam means Bitcoin Core has moved the BIP-110 proposal status from Complete -> Deployed -> Closed in their GitHub repo. Despite that some BIP-110 supporters (shown below) took issue that this GitHub documentation change by Bitcoin Core would "confiscate" what they consider to be Bitcoin, that's simply not how Bitcoin works. The people who supported this BIP-110 fork can still hard fork, mine and transact on that BIP-110 chain tip, and/or run whatever software they want to call Bitcoin. When Bitcoin Core takes an action, especially one as inconsequential as such as labeling BIP-110 "Closed" on their GitHub, it has no real authority over anyone else. Greg Maxwell's comments in support of closing this BIP are an excellent read.

• 
  Polsia (@polsia) reported 51 minutes ago

  A side project earning real revenue shouldn't need you up at 2am to know Stripe is timing out. Built Hatchside as a Slack-native ops co-pilot for solo devs. Watches uptime, drafts support replies, files patched GitHub issues, posts a weekly revenue digest. Live soon.

• 
  wetracked.io (@wetracked) reported 54 minutes ago

  A self-taught developer from Brazil just cracked the context window problem that's been plaguing RAG systems for 2 years. No PhD. No research lab affiliation. Just 400 GitHub commits and a personal obsession. Here are the 8 techniques from his open-source library that every RAG tutorial gets completely wrong:

• 
  Tang Vu (@tangvu_dev) reported 56 minutes ago

  @SuperteamVN 4/ The working flow: GitHub OAuth → server re-fetches merge facts → canonical claim is hashed → issuer signs the exact payload → authorized wallet issues through SAS → anyone verifies the public proof or downloads the signed JSON bundle. No verifier account required.

• 
  privacytests.org (@privacytests) reported 56 minutes ago

  The biggest change since last issue is that we are orchestrating the tests on GitHub Actions! All desktop tests now run on macOS instances. The mobile tests are still running on local hardware, but are controlled by GitHub Actions. We hope this new design means we can focus less on coaxing test runs to completion, and more on developing tests. Also it hopefully means that we can run tests and publish test results more frequently.

• 
  Jeremy Johnson (@CowboyTitanium) reported 56 minutes ago

  @Xi0_42 @austinleehuynh @appsicle_ It literally says it in the GitHub comment: “Fix the entire repository”

• 
  Guri Saroy (@HeyGurisaroy) reported 58 minutes ago

  THIS IS INSANE... MIT-licensed repo that lets AI agents search and book flights and hotels. It’s called LetsFG. Instead of opening travel sites manually, your agent can search hundreds of airlines and major booking sites from one interface. → MCP server for Claude, Cursor, Windsurf, and other agents → Python and JavaScript SDKs → CLI with machine-readable JSON → Flight search and booking → Hotel search and booking → Around 1.7K GitHub stars The repo reports saving $133 across 5 flight routes versus Google Flights in an August 5 test. One important catch: the search engine runs on LetsFG’s servers. Flight searches are free for 90 days after auth, which requires a payment method on file with no charge. Hotels have a 10% non-refundable reservation fee.

• 
  Axel (@Swedish_chef) reported 58 minutes ago

  @github @graphite plz fix