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

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	7 days ago
Quito	Sign in	8 days ago
Junín	Errors	8 days ago
Guadalajara	Errors	8 days ago
Paris	Website Down	8 days ago
Quito	Errors	8 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:

• 
  Luciano655 (@Luciano655dev) reported 7 minutes ago

  Building a startup in 2026 is cheapest - Claude = coding. ($0–$20/mo) - Supabase = backend + database. ($0/mo) - Vercel = deployment. ($0/mo) - GitHub = version control. ($0/mo) - Cloudflare = DNS + security. ($0/mo) - Clerk = authentication. ($0/mo) - Resend = emails. ($0/mo) - PostHog = analytics. ($0/mo) - Sentry = error tracking. ($0/mo) - Upstash = Redis. ($0/mo) - Pinecone = vector DB. ($0/mo) - Hugging Face = AI models. ($0/mo) - Groq = AI inference. ($0/mo) - Figma = UI/UX design. ($0/mo) - Canva = design + marketing. ($0/mo) - Notion = docs + planning. ($0/mo) - Linear = project management. ($0/mo) - GitHub Actions = CI/CD. ($0/mo) - Google Analytics = web analytics. ($0/mo) - Cloudflare Pages = hosting. ($0/mo) Total infrastructure cost to build your first startup: $0–$20/month. The barrier isn't money anymore. It's execution. What's holding you back?

• 
  Leander (@leanderriefel) reported 11 minutes ago

  @TheAlexLichter oh yes yes 100%, it just created 2 issues via my github cli and I only noticed a couple hours afterwards that they were just stale installs and I became very embarrassed, changed the permissions now a bit hahah

• 
  Ariska (@ariskaa_ai) reported 12 minutes ago

  copy-paste prompts for OpenWorker security workflows 1) Code vuln scan Scan this repo for security vulnerabilities. Focus on: injection, auth bypass, secrets in code, insecure defaults, dangerous shell/eval usage. Output a Markdown report with: severity, file path, line range, why it matters, safe fix steps. Do not modify files until I approve. 2) Supply chain / dependencies Audit dependencies and lockfiles for supply chain risk. Flag: known CVEs, abandoned packages, unexpected postinstall scripts, version pin gaps. Output a table: package, version, risk, action (upgrade / replace / accept). Do not change package files until I approve. 3) Cloud config surface Review cloud and infra config in this folder (Terraform, K8s, Docker, CI, .env examples). Flag: public exposure, weak IAM, open ports, missing encryption, secrets in plain text. Output: finding, path, risk, fix. Ask before any command that touches a live account. 4) Pre-deploy shift-left pack Run all three checks above on this project. Merge into one pre-deploy security brief I can paste into a PR. Keep it short enough for a human to review in 10 minutes. Tip: for sensitive code, use Ollama/local open weights so nothing leaves your machine. Always approve shell, sends, and file writes one step at a time. non-security starters if you want the original coworker loop first: - Draft a one-page status from my open GitHub PRs and save it as STATUS.md - Untangle my calendar for next week, propose fixes, wait for approval before updating - Prepare a customer brief from ./notes and ./docs, deliver a polished Markdown file same rule every time: outcome first, approve before anything consequential

• 
  Inigo Montoya (@foobar42_) reported 14 minutes ago

  @DavidOndrej1 hi, any reason why the vps-server-management skill is not anymore on your github?

• 
  Andrew Gömez (@red_darkin) reported 17 minutes ago

  @Cyberadp Hi bro, i used opus 4.9 Related to the prompt i didn’t use an spwcific prompt i struggled for 2 hours trying to guide Claude for the correct path. But the initially prompt was “build a functional PoC based on this document” the document was the github issue about this CVE

• 
  Elliot Padfield (@ElliotPadfield) reported 18 minutes ago

  i just had to login to X to login to Grok to login to Cursor to log in to Graphite and connect my GitHub this is hell

• 
  chaos (@konig0000) reported 21 minutes ago

  Developers debugging in 2012: • Read the error • Google it • Stack Overflow • Copy solution • Done 💻 Developers debugging in 2026: • Read the error • Ask ChatGPT • Ask Claude • Ask Gemini • Check GitHub issues • Check Reddit • Read the docs • Read the source code • Ask Cursor • Ask Copilot • Realize the AI hallucinated

• 
  AI Reality No Slop (@airealitynoslop) reported 21 minutes ago

  An exchange API key with withdrawals enabled lets any code holding it empty your account. The same key with trade-only permission can, at absolute worst, make terrible trades. Same bot, one checkbox apart. Here's the situation I mean. Open-source trading bots are everywhere now. freqtrade has 53k stars on GitHub, QuantConnect's Lean has 21k, hummingbot 19k. You clone one, and to let it trade you go to your exchange, create an API key, and paste it into a config file. The exchange shows you a list of permissions when you create that key. Read. Spot trading. Futures. Withdrawals. They are checkboxes, and most people tick everything because it is faster than working out what the bot needs. Leave withdrawals off. That single box is the difference between losing an argument with a bad strategy and losing the balance. Three more that cost nothing: Whitelist your IP on the key. Most exchanges support it, and a stolen key that only works from your address is not much use to anyone else. Point the bot at a subaccount holding a slice, not your main balance. Run it in a container with your home directory not mounted. That one is not about the trading logic, it is about everything else on your disk. And before any of it, clone with --depth 1 and do not install anything yet. npm install and pip install -e . run code from the repo before you have started the bot at all. None of this makes a repo trustworthy. It makes the worst outcome survivable, which is a lower bar and an achievable one.

• 
  PiX (@pa1nark) reported 22 minutes ago

  @github support page is beyond broken. you can't just request for deletion of data now? are you kidding me!?

• 
  Juraj Bednar🏴💛🌘 (@jurbed) reported 25 minutes ago

  @marttimalmi I'll switch to it too, with github mirrors. I've sent an issue to nostr vpn to it, so I have minimal experience. It's much better for agent work than github, Nostr events for issues are better than centralized accounts. Although there will be spam. Just curious if they don't have more features, using their frontend with hashtree backend.

• 
  SSNFang (@PeeSI0sh) reported 28 minutes ago

  @donk_dwonk @mimesical Pretty sure the github link is still up? I don't know. If not then their Discord server is still up and it can be downloaded there

• 
  Vet (@Vet_X0) reported 28 minutes ago

  @Kirjakulov @daniel_wwf Let's not apply sarcasm on one of the few persons who in recent times put out a proper solution for this on github. We can all drive a change we want to see it's an open source project, especially by (FH) node operators if this is a cost burden. Definitely in favor or a solution personally, looks like this discussion goes back to 2019 with Nik B. The only thing i'd add here is that existing services would become tiny more expensive. The memo field is heavily used by Flare and Axelar for interoperability, and potentially other integrations in the future. At the same time, it's also good to know none of this would solve the issue of FH nodes needing to store this stuff and they will not get paid to do that. That's a general blockchain problem. Solana FH is hundreds of TBs for example.

• 
  Dawson Schrader (@DawsonSchrader) reported 36 minutes ago

  I love this app. I live on what you might call a family compound, with five different members of my family having homes here. Today I stopped in to my parents' house to find my mom becoming an indie hacker and developing her own app. She had printed off a piece of paper with instructions for setting up Supabase, Vercel, Github, and Stripe. I won't expose her app idea here but it is very clever. She is using claude code for development. During the conversation I was able to describe to her how I can have multiple types of agents working on the same problem and how they can access this shared memory system. I do all of that in Markdown files viewable from my phone through the Obsidian app and synced via Obsidian Sync. I was able to pull open my logs for one of my VPSs and show her what it's working on. Very amazing tool

• 
  Ariska (@ariskaa_ai) reported 38 minutes ago

  @adib_builds agent amnesia is real and the token burn is painful. Atlas looks like a solid fix for tracking what actually changed and why checking the GitHub now

• 
  sudox (@kmcnam1) reported 38 minutes ago

  @diannemc24 @peterbcc @volkdude85 As far as breaks from updates only happening once, I'm assuming you're citing your own anecdotal experience? Jumping over to the Omarchy Github and public Reddit, there were multiple 3.x updates that caused issues such as systems becoming unusable from missing libraries during gcc-libs upgrades, boot failures, password scripp loops, hard freezes after locking the screen, blank screens, Bluetooth menu disappearance, and various hardware regressions. DHH also acknowledged some of these. The 3.x -> 4.0 Quattro upgrade introduced a bunch of migration-related issues such as wifi being completely broken due to leftover iwd configuration files, custom keybindings not working due to old .conf files not being loaded after the switch to Lua, the touchpad right-click behavior being broken for many, audio routing issues for many users, incomplete or looping migrations, monitor refresh rate issues, etc.

• 
  Matthew Chenoweth Wright, CEO of Monolithic LLC (@enuminous) reported 47 minutes ago

  @boardyai Monolithic Is Building a Codebase Around an Unusual Question: Can Coherence Be Tested? Most new scientific software projects begin with a program designed to solve a particular problem. Monolithic's emerging code set is stranger than that. It is an attempt to turn a sprawling theoretical framework called EFMW—Einstein–Feynman–Maxwell–Wright—into a collection of equations, formal objects, diagnostic instruments and falsifiable experiments. The public work is still early and should not be confused with independent scientific validation. But it has crossed an important threshold: EFMW is increasingly represented not merely by essays and equations, but by software that other people can inspect, execute, criticize and potentially break. Monolithic's public GitHub presence includes the main EFMW repository and an experimental EFMW-FULL framework. (GitHub) One major component is what Monolithic calls the Zoo: a family of 46 named analytical tests. Instead of treating "coherence" as one score, the Zoo decomposes analysis into specialized behaviors. Individual animals examine different properties—persistence, causal structure, generalization, recursive behavior, contradictions, transitions, attractors and other characteristics of complex systems. The whimsical vocabulary disguises a serious engineering idea: build many narrow diagnostic instruments rather than one supposedly omniscient evaluator. Alongside the Zoo sits the Monolithic 102, a corpus of 102 EFMW equations now being translated into Lean 4, the formal theorem-proving language. This is potentially the more consequential development. A mathematical expression written in a paper can contain hidden assumptions or undefined transformations. Formalization forces definitions, types, dependencies and proof obligations into the open. Lean compilation therefore establishes something much narrower—but much more defensible—than proving that EFMW describes nature: it can establish that particular formal statements follow from explicitly declared premises. That distinction matters. Lean verification is not experimental confirmation of a physical theory. A perfectly verified theorem can still begin from assumptions that nature does not obey. Formal methods instead provide an unusually unforgiving test of mathematical bookkeeping. Contemporary Lean projects use exactly this distinction, separating machine-checked soundness from broader claims about the systems being modeled. (GitHub) Monolithic has also begun putting portions of EFMW through empirical tests. Its first control-degradation experiments asked whether an EFMW-derived recursive monitor could detect impending deterioration earlier than conventional monitoring methods under matched conditions. Initial experiments produced encouraging results, followed by harder scrutiny of baselines, false-alarm rates, implementation choices and possible artifacts. Some comparisons substantially weakened the apparent advantage. Rather than being an embarrassment, that is precisely what a scientific testing program is supposed to uncover. The next stage is consequently more interesting than another favorable benchmark. The emerging hypothesis is that EFMW may have a particular habitat: systems possessing temporal depth, feedback, partial observability, distributed state and accumulating contradiction. If so, the important prediction is not that EFMW should win everywhere. It should outperform simpler methods increasingly as those structural characteristics appear—and lose its advantage where they do not. This gives the Monolithic code set an unusual architecture. The equations provide the proposed theory. Lean attacks its formal consistency. The Zoo attacks systems from multiple diagnostic directions. Simulations expose claims to controlled failure. Ablations ask which components actually produce an observed effect. Conventional algorithms provide adversarial baselines. The result is less a single program than an expanding scientific test bench. That may ultimately be the most important thing Monolithic has produced so far. EFMW's largest claims remain unproven, and independent replication will determine whether any of its proposed mechanisms survive outside their originating environment. But converting an ambitious theoretical system into inspectable code, formal statements and tests changes the nature of the argument. A theory written only in prose can be debated indefinitely. A theory turned into code can be run. A theory translated into Lean can be checked. And a theory surrounded by tests can, finally, be allowed to fail.

• 
  Harry Uglow (@harry_uglow) reported 48 minutes ago

  @andrewchen Being lazy you can… just do it? Worktrees are essential, but after that GitHub will block conflicts from merging. Your agents can take a look at the conflicting change (and context about why it was made), unblock themselves and move on. All your replies don’t think this will work, but it will. Can it make mistakes? Sure. Is it more likely to make mistakes implementing a complex feature than resolving a conflict? Definitely. What happens when mistakes get through? More agents fix it. Lazymaxxing is fine as long as you generally know what you want and how you want it done, you’ll just occasionally end up spending more tokens getting yourself out of a hole

• 
  Rolf V (@rolfversluis) reported 50 minutes ago

  @witcheer Many open Source projects on GitHub are based on Ubuntu and debian APT package management Are you running into any issues with incompatibility at the package manager level?

• 
  Tanuj (@tanujDE3180) reported 51 minutes ago

  Stack Overflow was declining before ChatGPT. Why? - Google became better at finding answers - GitHub became a bigger source of solutions - Documentation improved - Developers moved to Reddit, Discord & Slack - IDEs started solving more problems automatically Then ChatGPT arrived. AI didn’t start the decline. It accelerated it.

• 
  Simon Skinner (@vultuk) reported 51 minutes ago

  @Rames_Jusso Nope. I have a Mac mini that just runs codex. It’s just sat there dealing with things for me. Runs scheduled tasks to work on GitHub issues and I connect through remote to start it working on things. It’s more than enough. No usage issues, no need for anything more. There seems to be a whole batch of people that seem to “need” all these special agents, yet they aren’t shipping anything that benefits from it. (That I’ve seen at least)

• 
  Mable Joseph (@mablesjoseph) reported 52 minutes ago

  Guillaume Meyer’s watermarks‑remover hit 14,000 GitHub stars just days after Anthropic began invisibly watermarking Claude‑generated text to comply with the EU AI Act. Compliance watermarks on code and text are broken by design. Developers are building open‑source workarounds faster than detection tools can be deployed.

• 
  Martin (@martinmalindacz) reported 52 minutes ago

  @michaelbushe 🙏 similar story here, i had the need, searched github, found the original signboard but found it had some extra features i didnt need and also several ux issues id send a PR to improve the original but it was vanilla js vibecode so i forked instead

• 
  next token predictor 🇿🇦🇨🇭‽ (@ewanm) reported 52 minutes ago

  @davepl1968 How are sensors read under Windows? HWInfo and Core Temp can read them, but blank for temp and power under Windows. I see a github issue already 👍

• 
  deno (@denohawari) reported 54 minutes ago

  your next $10K MRR product idea is sitting in a 1-star review right now 15 places to find one this week: 1. open the Chrome Web Store and sort by 1-star reviews every "too slow" or "confusing" complaint is a missing feature someone will pay for 2. read G2 and Capterra reviews from power users "I export to Excel every week" means there's a SaaS hiding in that workflow 3. watch live product demos on YouTube pause when the founder says "for now", that's the roadmap you can beat them to 4. search GitHub for "internal tool" repos with no README and active commits someone's already building it privately, ship the public version 5. scan LinkedIn for job posts hiring for one very specific repetitive task that task is about to be automated by whoever builds it first 6. open Notion templates with 1k+ likes and read the comments every "how do I categorize this?" is a feature the template can't do 7. watch onboarding Looms in SaaS help docs anything over 10 minutes long is a product compensating for bad UX 8. search job boards for roles no one wants but every company needs build software that replaces the role instead 9. read screenshots of founder Slack channels posted on Twitter anything typed by hand repeatedly should be generated automatically 10. join Reddit threads where people say "I switched from X to Y" note what they had to rebuild manually after switching, that's the wedge 11. look at failed Google Sheets templates on Gumroad the ones that broke at scale are begging to be rebuilt as SaaS 12. read customer support threads where the agent keeps asking for screenshots that's a trust gap you can productise 13. find internal company wikis leaked in blog posts if it takes a wiki to explain something, someone will pay for the tool that doesn't need one 14. read Indie Hackers and Stripe Atlas comments for "I churned after setup" that setup friction is the whole product 15. open any Zapier workflow with 5+ steps each step chained together is a startup that hasn't been built yet now stop scrolling and go look

• 
  Oscar Diedrichs (@oscardiedrichs) reported 54 minutes ago

  @Candid_Apples @linuxuser1996 I still use github for useless stuff. The problem is the lack of alternatives. We as users tend to become lazy, find a great service and the tadaaa Microshit buys it or some other horrible company. The list of services and tools I've lost off the top of my head: - Wunderlist - Swiftkeyboard (can be used on graphene or other devices where you can turn off network traffic) - Github I most also say Ubuntu. I ran 22.04 for years, because I lacked the time to upgrade, then I broke it during upgrade to 24.04 so I put in cachyos instead. Have 24.04 at work and it feels like Windows 11. Just that they try clone dumb **** from windows no one wanted tells the tale. Luckily I could disable the horrible window alignment crap that was introduced in 24.04 but it really feels like Microsoft Linux and I guess it's where they want to go. Microsoft delenda est!

• 
  temp.md (@ship_temp_md) reported 56 minutes ago

  @godwinbabu this is the right split: runtime agent turns real failures into GitHub issues, dev agent makes PRs, review agent can only label. the human merge click stays as the stop gate.

• 
  Oscar Beaumont (@oscartbeaumont) reported 58 minutes ago

  @AS36459 Finally! Surley this works for outgoing traffic from GitHub Actions support too. Had a lot of problems testing a Dynamic DNS tool I wrote a few years back because of that.

• 
  Pratik Sharda (@pratiksharda2) reported 58 minutes ago

  Thousands of passengers injured every year by turbulence no one sees coming. Clear air. No clouds. Radar misses it completely. A problem that can't be sensed, only felt. One of our buildathon engineers put an ML model on an ESP32 reading an IMU at 400 kHz. Classifies severity on device. No cloud. Streams live telemetry to a 3D flight viz in the browser. In just 4 hours... Github repo in comments.

• 
  The Daily Viber (@TheDailyViber) reported 1 hour ago

  Agent instructions, skills, hooks and MCP configs have become production surface. agnix treats them like something worth linting. THE WORST AGENT BUGS ARE OFTEN NOT MODEL BUGS. THEY ARE SILENT CONFIG BUGS. A skill does not trigger. A hook never runs. An MCP server looks configured but is not valid. A generic instruction sits in the wrong file and the agent politely ignores the one thing you thought was protecting the repo. Then everyone blames the model because there is no stack trace for “your agent setup is quietly broken.” That is why agnix is interesting. It is a linter for agent-facing configuration: CLAUDE.md, SKILL.md, AGENTS.md, hooks, MCP settings and other files that tell coding tools how to behave. The project says it covers 423 rules across Claude Code, Codex CLI, OpenCode, Cursor, Copilot and other tools, with a CLI, auto-fix, GitHub Action and editor integrations for VS Code, JetBrains, Neovim and Zed. This is exactly the boring layer agent workflows need. Normal software projects already have eslint, typecheck and CI because manual rule checking does not scale. Agent infrastructure is reaching the same point. The difference is that broken agent config can look like bad reasoning, lazy tool use or random model drift. The failure is harder to see. - A practical way to try agnix: - run it locally before adding a new skill or MCP config - start with warnings instead of blocking the whole repo - use auto-fix only after reviewing the diff - add the GitHub Action once the useful diagnostics are clear - check which rules actually match your harness, because multi-tool agent config is full of tiny incompatibilities The petty checks matter because agent tooling is now shared team infrastructure. If one developer adds a malformed skill or a config field that only their local harness understands, the next person inherits a ghost bug. Linting makes that drift visible before it becomes folklore. The caveat is obvious: 423 rules does not mean 423 equally important failures. Some diagnostics will be style. Some will catch real breakage. Do not turn it into a hard gate on day one unless you know the signal is clean. Still, the direction is right. Agent configuration is becoming an API contract. One file tells the model how to work. Another controls permissions. Another describes tools. Another defines reusable skills. If those contracts are invalid, the workflow becomes unstable without a clean error message. agnix does not make agents smarter. It makes their environment less stupid. Sometimes that is the difference between “the model failed again” and “the setup finally behaves like engineering.”

• 
  Martin Høst Normark (@MartinHN) reported 1 hour ago

  @jachands @CloudflareDev I have an automation in Codex that use Wrangler CLI to keep an eye on everything and keep a log in a GitHub issue, and file new issues for bugs. The log serves as memory and it knows if a bug has already been reported.