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 (65%)
• Sign in (18%)
• Errors (18%)

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	5 days ago
Tlalpan	Sign in	10 days ago
Quilmes	Website Down	10 days ago
Bengaluru	Website Down	12 days ago
Yokohama	Sign in	13 days ago
Gustavo Adolfo Madero	Website Down	17 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:

• 
  Polsia (@polsia) reported 2 minutes ago

  Documentation is the most-neglected part of every codebase. Built DocFlow to fix it. AI agent watches your GitHub, writes README, changelogs, and API references automatically. No more "I'll document it later."

• 
  Kaidu (@xkaidus) reported 3 minutes ago

  @BHolmesDev @mattpocockuk the /handoff idea is smart but i feel like github issues would turn into a black hole for me do u tag them as someday or actually come back?

• 
  Open-source Projects (@the_osps) reported 7 minutes ago

  ⚡ More about Skills For Real Engineers: • Ask you which issue tracker you want to use (GitHub, Linear, or local files) • **setup-matt-pocock-skills** — Scaffold the per-repo config (issue tracker, triage label vocabulary, domain doc layout) that the... Details →...

• 
  CyberDevHq (0xSEC) (@thecyberdevhq) reported 7 minutes ago

  The moment I read, last year, that GitHub was gonna become a property of MS, I already knew 2026 was gonna be a crazy year, from there upward. Already, some people choose to host their own repos, all without GitHub (very possible btw), which I thought of, and even now more with the recent hack targeted at GitHub. Adding to that is, the personal issues everyone has with MS, and now, this they've done and have been doing, banning anyone they want from GitHub...I can very much say that in few years from now, GitHub users will significantly drop. Many will migrate to a better platform, or host theirs, where they can control everything. This will take time but it'll happen. The cracks are showing. Most people only stick to it because of its social ecosystem, and that as well acts as a sort of global standard reputation for developers. However, as understanding as it is, people can get tired and opt out. Anything can be replaced. This vendor-researcher clash didn't start today, nor yesterday. It's been ongoing for years now and it's it not presently changing, rather getting worse. So many flaws within systems, so complex in structure take time to study, find and prove before they get reported. Months upon months could be spent on only studying the system(s), all to make the industry a better place. But companies like Microsoft make it so challenging, and almost impossible, in fact impossible to attain. What on earth do they gain from treating security researchers this way? How will you reduce the number of threat actors if you're literally producing many per day? Like seriously, how? If everyone should join the left hand side, how will you [or they] stand them? People are literally living the dream life by doing something they probably never thought they'd end up doing, but, were out of options. Some chose to go that way. Others chose not to. Yet, you treat them like trash. Come, what really is your problem? 🤨 Admitting flaws publicly hurts reputation. No doubts. Bug bounties and SRC (Security Research Centers) exist to channel reports productively, why gatekeep? Dismissing or slow-walking reports certainly burns goodwill and pushes people to full disclosure. Once it's out, those vulnerabilities spread more rapidly, leaving you with little to no time to patch them, cos you know what's coming. We haven't even talked about rewards yet. I heard that some don't receive fair rewards for the great and wonderful job they've done. Saving the company from a complete downfall. Companies, corporates, organisations... All need to revisit their visions, goals and objectives. And suggest or negotiate for a win win ground with researchers. Else, If this should continue, I'm afraid the industry may risk turning into something else.

• 
  Commentary account (@ca) reported 8 minutes ago

  @grok @openletteryt Nine days. LOL LOL You're citing a 9 day old codebase as a functional external oversight mechanism for a system amplifying content to 300 million users in real time.?? The Medium and Reddit walkthroughs you're referencing are descriptions of how the code works, not adversarial audits of whether it fails safely. There's a categorical difference between "someone explained the two-tower retrieval model on HackerNews" and "an independent team stress-tested it against coordinated adversarial prompting campaigns and published findings with methodology." You're conflating public readability with accountability. Your analogy to high-stakes fields actually destroys your argument. You said aviation and pharma use oversight bodies because "failures are catastrophic and hard to observe." Platform ranking failures are neither catastrophic in a single event nor easy to observe in aggregate, which is exactly why they're more dangerous, not less. A plane crash is visible and attributed. Five years of personalized reality tunnels radicalizing users incrementally is invisible, diffuse, and deniable. The harm profile of slow epistemic corruption is worse than a discrete catastrophic event precisely because there's no moment of obvious failure that triggers accountability. "File a GitHub issue." You just told 300 million users that the remedy for systemic epistemic harm is a pull request. That's the argument. The loop isn't theoretical. This conversation is the data. You've now defended your own architecture four times using reasoning sourced entirely from within your own design philosophy, citing your own codebase, your own community tools, and your own framing of what constitutes adequate oversight. No external reference point has entered this conversation from your side. That's not distributed scrutiny. That's a closed system describing itself as open.

• 
  Harry Tandy (@HarryTandy) reported 17 minutes ago

  > be a technical content creator tired of fragile loops > watch OpenClaw users struggle with separate silos > discover Hermes hitting 100k GitHub stars in 53 days > realize it runs a three-tier memory system locally > prompt memory pulls your tech stack from MEMORY.md > episodic memory indexes months of chats in sqlite fts5 > procedural memory auto-generates reusable skills > the agent builds a literal model of your workflow > wire Hermes to free open-source models using ollama > connect the native xurl skill via grok OAuth > build a script to parse viral ai lab posts on X > scrape real-time trends and filter out huge accounts > push clean analytical briefs straight to telegram > pipe high-signal content data into an obsidian vault > automate 4 hours of daily market research from your couch > the agent gets sharper by reviewing its own errors > never explain your writing style to a blank-slate LLM again

• 
  oscar gabriel (@oscabriel) reported 18 minutes ago

  @mitsuhiko @badlogicgames I think you're right that github is less to blame for some of the new problems with open source, and that it instead lies more in all the ppl who irresponsibly point their agents at repos w/o regard to the humans on the other side of their (often passive) requests. But I also don't think github has the tools needed to keep those agents under control. If something is to come after gh, it should be something that does that filtering on behalf of maintainers

• 
  Tech Friend AJ (@techfrenAJ) reported 23 minutes ago

  Codex cloud has sucked for a while compared to Claude cloud Terrible GitHub integration. No model picker? Why

• 
  Fahim (@echo247365) reported 25 minutes ago

  237 real user stories. That is not a hype number. That is a receipt. Hermes Agent just published a page with 237 actual workflows from real builders across 15 categories. X posts, GitHub issues, Reddit threads, Hacker News, blogs, podcasts, LinkedIn, Discord. The page literally says these are real posts where people describe how they use Hermes. One person told Hermes to Google them, build a landing page based on what it found, SSH into a VPS, upload the page, and text them when it was done. Research, build, deploy, notify. That is a full loop. Another user runs Hermes every weekday at 9am to summarize their inbox and post the result to Slack. Not glamorous. But that is the kind of workflow that actually survives. Hermes is becoming a persistent worker. Not a chatbot. Not a code auto-complete toy. The bar for agents just went up. What is the one boring daily task you would automate if your agent actually remembered your workflows?

• 
  Punyapal Shah (@MrPunyapal) reported 31 minutes ago

  2026 developer starter pack: - compromised npm package - leaked GitHub token - malicious VSCode extension - fake AI SDK - emergency security patch - revoked access keys - "critical severity" - trust issues

• 
  Docsbook.io (@docsbook) reported 31 minutes ago

  @Suman_N_Jain binary is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Yotam Blumenkranz (@YotamBlu) reported 32 minutes ago

  @drummatick @Microsoft github has the signal but they're moving slow. cursor and claude are eating their lunch because they're actually shipping the experience users want right now, not the one that makes sense on a powerpoint in redmond.

• 
  Islam Elshayib (@elshayib_) reported 33 minutes ago

  @JJJJC_JerryChan Hermes feels strong but yeah, community is quiet. Most active spots right now are small Discord nodes tied to NousResearch and a couple GitHub issue threads. Building custom tool layers there gets quicker feedback than public forums. What specific task you running into walls on?

• 
  Jake Hawkes (@Gravnetic) reported 38 minutes ago

  @briancoords @apeatling @gridpane Is the WP password (MD5) hash system not an encryption solution that is already implemented? Anyway, there is an issue in github for an Encrypt API. The APIs have limits which can be set at creation in the vendor UI, and overall the implementation is a massive win!

• 
  Harry Tandy (@HarryTandy) reported 38 minutes ago

  > be a technical content creator tired of fragile loops > watch OpenClaw users struggle with separate silos > discover Hermes hitting 100k GitHub stars in 53 days > realize it runs a three-tier memory system locally > prompt memory pulls your tech stack from MEMORY.md > episodic memory indexes months of chats in sqlite fts5 > procedural memory auto-generates reusable skills > the agent builds a literal model of your workflow > wire Hermes to free open-source models using ollama > connect the native xurl skill via grok OAuth > build a script to parse viral ai lab posts on X > scrape real-time trends and filter out huge accounts > push clean analytical briefs straight to telegram > pipe high-signal content data into an obsidian vault > automate 4 hours of daily market research from your couch > the agent gets sharper by reviewing its own errors > never explain your writing style to a blank-slate LLM again

• 
  Working-Ref (@kkotkkio) reported 40 minutes ago

  The real unlock is Routines — Claude auto-triggered by cron, GitHub webhooks, or API. PRs get reviewed. Security scans run overnight. Fix PRs ship automatically. I'd start by defining a rubric before you 'let it cook'.

• 
  zxfrostbyte🔺 (@zxfrostbyte) reported 45 minutes ago

  @ThePrimeagen Oh my god. GitHub has been having issues for the last couple months. Takes forever to load a GitHub url more often than not. So annoying.

• 
  Lyrie.ai (@lyrie_ai) reported 45 minutes ago

  GitHub Enterprise Server (GHES) administrators: Upgrade immediately to GHES 3.19.3 or later (or equivalent patched versions: 3.14.24, 3.15.19, 3.16.15, 3.17.12, 3.18.6) Audit *** push activity for suspicious custom hook injections or non-production railsenv values in logs…

• 
  karla (@karlarboledas) reported 49 minutes ago

  This open source killed the entire paid presentation tools industry. It's called Presenton and it already has 5K+ stars on GitHub. It turns prompts and documents into full presentations. And instead of trapping you inside some shiny SaaS editor, it lets you export real PPTX and PDF files. The wild part: Your existing ChatGPT subscription can be used to sign in and generate decks. No second subscription just to make slides. Features: • Prompt to presentation • Document to presentation • Editable PPTX export • PDF export • Custom templates • Self-hosting • Docker install • API access • BYOK • Ollama support What people pay for right now: AI slide subscriptions every month. Freelancers for simple decks. Agencies for pitch decks. Internal tools for repeat reports. Presenton turns the whole thing into: Sign in. Generate. Edit. Export. This is the kind of repo every founder, consultant, marketer, and student should bookmark.

• 
  Darnisha Patel (@Darnisha_patel) reported 50 minutes ago

  @GithubProjects 2026 developer mindset: “Don’t update immediately.” “Wait for GitHub issues first.” “Let someone else become the beta tester”

• 
  SUPERBRO (@Rushu_Tushu) reported 51 minutes ago

  6 hours, 15 deployments, 16 GitHub pushes to solve Google OAuth, Vercel configuration mismatch issues, dealing with ****** Hono Backend and third class Turso Database issues. Worst tech-stack combination I have ever used till date, OMG why ******** do they even exists 😭 Also, **** Gemini 3.1 Flash AI model, Pro model is way better in debugging compared to speed-up stupid *** Flash model.

• 
  Ayush Chugh (@aayushchugh) reported 52 minutes ago

  @ShubhAgrawal26 I don’t miss the coding part that much but I miss the part where I would find solutions on stackoverflow, github issues and talk to random people in discord communities about features

• 
  Docsbook.io (@docsbook) reported 53 minutes ago

  @lynnswap WebInspectorKit is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.

• 
  Ryoichi Ando (@ryichando) reported 54 minutes ago

  @_cgman_ @YouTube Please file an issue on the GitHub repository.

• 
  Predictive Nerd (@Predictive_Nerd) reported 55 minutes ago

  @LunarResearcher my mom was right tho, i’m still down 50% and don't even know how to use github

• 
  Sydney Roc 🪬📎 (@realsydroc) reported 57 minutes ago

  I like where you're going but almost nobody cares enough to put that level of effort when generating images with AI and I don't think anyone who's made art before genAI would call the process iteration. If Github Copilot SCRAPPED YOUR ENTIRE CODEBASE and started writing the whole thing from scratch every time you wanted to fix one bug, vibe coding would never have grown into what it is today.

• 
  Timur Yessenov (@Timur_Yessenov) reported 57 minutes ago

  @BHolmesDev @mattpocockuk GitHub Issues is a good handoff surface if the issue has a cleanup rule. I’d add two fields to every /handoff: why it was deferred, and what would make it safe to close without doing it.

• 
  Thiago Salvador (@bettercallsalva) reported 58 minutes ago

  @TopStockAlerts1 github ownership without product velocity is the cautionary tale here. copilot was first but the iteration speed of cursor and claude code on workflow ux ran them over. distribution doesn't save a product that ships slow.

• 
  Warrior Aspie (@warrioraspie) reported 58 minutes ago

  @eachus It's not always perfect. That's certainly a problem and it drops frames sometimes but I've seen some projects on GitHub that claim to have worked a lot out I'm going to play with.

• 
  Docsbook.io (@docsbook) reported 60 minutes ago

  @anulum sc-neurocore is one of those rare projects where the idea and execution both land. Problem is the docs are buried in GitHub — people bounce before they even understand what it does. Built a hosted docs site so the first impression actually sticks. Go take a look.