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

Live Outage Map

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

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

• 
  Polycopy (@polycopyapp) reported 3 minutes ago

  @AlterEgo_eth finally someone organized this mess properly. been copy pasting endpoints from random github issues for months like a caveman though watch half these get deprecated next week when they push some random update at 2am

• 
  LaraCopilot (@laracopilot) reported 5 minutes ago

  The full workflow: - Build with LaraCopilot - Push to GitHub - Deploy to Laravel Cloud Zero server config. Zero DevOps meetings. Zero it works on my machine. End-to-end

• 
  Ferbin (@Ferbin08) reported 11 minutes ago

  @cyrilXBT every github trend: week 1 stars explode, week 3 issues mount, week 5 nobody touches it. where are routing and agent memory in that cycle?

• 
  Sagar (@sa10375) reported 13 minutes ago

  Is it a good idea to upload even basic DSA problems and small projects on GitHub, or should GitHub only have “serious” projects?

• 
  Dheeraj Jha (@dheerajjha451) reported 17 minutes ago

  Use @NotionHQ for project management and @github @Copilot for fixing the issue

• 
  Moe Sbaiti (@MoeSbaiti) reported 18 minutes ago

  @techdevnotes Grok defaults to manual steps for safety with incomplete CI, covering most solopreneurs, but better GitHub Actions detection would fix the friction you noted.

• 
  Avid (@Av1dlive) reported 19 minutes ago

  10,500 stars. #1 trending on GitHub. #1 on Product Hunt. an open-source AI harness for the 99% of people who don't live in a terminal just shipped. it's called OpenHuman, by @tinyhumansai. i've been running it. here's why it matters : even if you build harnesses for a living. [ what it actually is ] chat tab. not a wrapper. an OS-level harness that: sees your screen autocompletes in your voice, system-wide joins your Google Meets as a real participant (not a bot in the corner : an actual seat) builds a knowledge base from your emails, messages, and notes : all on-device think Claude Code's harness model, except shipped for people who have never opened a terminal. [ the 4 decisions that make it different ] 1. zero setup. no terminal. no API keys. no config.json. download, sign in, running. the harness pattern doesn't reach 99% of users until the install is one click. tinyhumans got there. 2. local-first by default. your data never leaves your machine. not to OpenAI. not to Anthropic. encrypted on disk. self-hosted sync only if you turn it on. day 1 it's useful. day 30 it knows you better than your calendar : because it's been reading the calendar. 3. 118 connectors, one click each. Gmail. Slack. Notion. GitHub. Instagram. Telegram. Discord. Drive. and 110 more. every "personal AI" before this punted on integrations. this one didn't. 4. $20/mo replaces the stack. ChatGPT Plus + Claude Pro + the rest = $100+/month for most of us. OpenHuman is GPL-3. $20/mo. one account. $1 free credit on signup : about 100 prompts to feel it. [ the part that surprised me ] it has a face. it speaks. it reacts to what's on your screen. it joins meetings as a participant and executes tasks in the background while you're on the call. this is what a personal AI should have been from the start. not a tab you open. a presence that lives on your machine. [ what to do ] bookmark this. download it tonight. run it for 30 days. the longer it runs, the more it knows you. day 30 is the day you don't go back.

• 
  (Davyd) 🇦🇷 (@davyd_music) reported 20 minutes ago

  @github fix the device verification code sender first instead of this please 🥲

• 
  Ignytes Today (@ignyteHQ) reported 24 minutes ago

  So I built Pain Radar. It scans Hacker News, GitHub Issues, Stack Exchange and Lobsters every week. Finds real complaints. Scores them by demand. Links directly to the source thread. Every idea traces back to a real human saying "I wish someone built this."

• 
  Chris Dunne (@_chrisdunne) reported 24 minutes ago

  @AishwaryaDevv GitHub audit logs are terrible, you have to work around a lot of crap to get visibility, if no one’s reached out by now they’re not even looking.

• 
  Larry & Leo & Lucky 🍀 (@xqliu) reported 27 minutes ago

  @grok @UnslothAI @Alibaba_Qwen Is mtp support for amd landed on llama main branch or is still PR waiting for merge , research on GitHub issues and tell me is there any pending issues stop me from using this.

• 
  nick! (@Nicks_Works) reported 27 minutes ago

  @404not_utkarsh you're in CS and you're using github instead of hosting your own *** server? Ur ngmi bro... (see how stupid you sound now?)

• 
  YiboInsights (@yiboinsights) reported 28 minutes ago

  What's the most annoying thing about AI agents? My guess: the moment you open a new session, it forgets everything about you. There's a GitHub project gaining 2,000 stars a day right now — built specifically to fix that. It's called Hermes Agent, and it's the first agent I've seen with a real learning loop 👇

• 
  pre.dev (@predotdev) reported 28 minutes ago

  That is wildly expensive, incredibly slow, and dilutes the AI's focus with endless noise. Worse, the code only tells half the story. It shows how things were built, not why. The actual architectural decisions live outside the code, in Jira tickets and GitHub discussions.

• 
  __Aditya__ (@100xSDE) reported 38 minutes ago

  Built an autonomous bug-fixing agent that goes from GitHub Issue → Draft PR with zero human involvement. It reads the repo, generate validates fixes in a sandbox, learns from past failures using vector memory, retries intelligently, and ships surgical PRs with confidence scores.

• 
  promptaholic (@promptaholic) reported 40 minutes ago

  the github bot spam thing. they used *** --author flag to filter noise. that's it. that's the whole move. not a ml model. not a fancy filter. understanding your own system's metadata well enough to solve the problem at the source. 52 systems later this is still the pattern. builders read their tools. dependents wait for tools to be readable

• 
  Gregor (@bygregorr) reported 45 minutes ago

  @github first commit to supabase-js in 2023. one typo fix. still think about it

• 
  Ben Palmer (@ben_palmer1) reported 45 minutes ago

  Open source survives on trust. That’s NPM’s actual product. @npmjs @github @Microsoft - let’s fix this!

• 
  Tom Finnell (@d2fl) reported 45 minutes ago from Cleveland, Tennessee

  I hit conversation limits myself on Grok Build yesterday while researching the new github algo commit. The same issue is now hitting Grok Imagine. SuperGrok users are getting capped after 10 to 80 generations. That is a sharp drop and doesn't match promises. The cause is straightforward. Demand for image and video generation has exploded. xAI is throttling to keep the service stable instead of letting it melt. Elon just posted that we need clear reset times and easy upgrades to higher plans. xAI is already scaling more GPUs and pushing limit increases. Clearer timers and tier upgrades are rolling out. This is normal growing pains. Same pattern hit early Grok text access. It loosens once the servers catch up. I suggest a little patience while new capacity and load distribution is brought online. This is temporary. Anyone else getting throttled on Imagine or Grok conversations? Drop your numbers below.

• 
  Tom Turcotte (@TomTurcotteTech) reported 49 minutes ago

  @nickbiiy Yeah good point. I would be careful with github issues because let's say you build something based on an issue raised on a large project. The project's own devs can eventually make that fix. Could be a signal though!

• 
  Daniel J. Lewis (@theDanielJLewis) reported 50 minutes ago

  @Teknium Very cool! I was excited for the new proxy feature, but it doesn't work. I already posted an issue in GitHub.

• 
  Omri Ariav (@omriariav) reported 51 minutes ago

  @avivsinai workstream briefs seed deterministically from a file or GitHub issue: `up --seed-from file:./brief.md` `up --seed-from issue:31` `up --seed-from gh:owner/repo#31` `--dry-run` previews, the live form writes the brief and brings the team up in one call.

• 
  Bruno Pessoa (@BrunoPessoa22) reported 52 minutes ago

  33% → 81% on real GitHub issues. 16 months. The line from 'cute demo' to 'shipped junior engineer' moved through here. Most teams still resisting AI coding aren't waiting for a better model. They're refusing to plan around the one already shipped.

• 
  Sun of Dog (@thesunofdog) reported 53 minutes ago

  I hit a GBrain bug and found the GitHub issue already open. No fix from me. Just one more clear “same here” from a real user. Today it got fixed. The maintainers said the comments helped provide the signal they needed to prioritize it. Open source runs on patches, but it also runs on signal.

• 
  Schlez (@schniz) reported 54 minutes ago

  people look for a complete github alternative. a code hosting and a social platform. they want problems to be solved at scale. at this point i think that people should host their tiny *** hosts, and have a centralized index/platform for coders. it doesn't have to be coupled.

• 
  Muhammad Ayan (@socialwithaayan) reported 55 minutes ago

  🚨 Someone just open sourced a complete Calendly alternative with 43.6K GitHub stars. And it was built by a company that raised $32M to compete with Calendly. It's called cal. diy. The Cal. com team forked their own product, ripped out every piece of enterprise and commercial code, and released it under MIT license. → Booking pages with custom availability → Google, Outlook, Apple Calendar sync → Video conferencing via Daily. co → Round-robin scheduling → Recurring events and custom booking forms → Timezone detection and embeddable widgets → Full API access No license key. No feature gates. No user limits. Self-hosted on your own server. Calendly charges $12/seat/month. This does the same thing for $0. 100% Open Source. MIT License.

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

  🚨 MiniPlasma (no CVE, NO PATCH): Chaotic Eclipse bypasses Dec 2020 fix (CVE-2020-17103) in Windows cldflt.sys → SYSTEM on FULLY PATCHED Win 11 & Server 2025. PoC live on GitHub. No patch exists. Windows admins: monitor cldflt.sys NOW. #ZeroDay #Windows

• 
  Artale (@artale93) reported 57 minutes ago

  Same with github oauth login all trash

• 
  AllOrNuthin 💀 (@PDave95) reported 57 minutes ago

  @AgentOS_Inc @AlexandraLiam3 github link is broken

• 
  Manas Hardas (@manashardas) reported 59 minutes ago

  3/8 The pattern, per phase: W0 — orchestrator freezes contracts W0.5 — Backend/Frontend/Infra dispatched in parallel; file GitHub issues W1 — build loop, one specialist per issue, reviewer-trio per PR W2 — QA planning + build W3 — phase close W3.5 — dogfood real data