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	4 days ago
Quilmes	Website Down	4 days ago
Bengaluru	Website Down	6 days ago
Yokohama	Sign in	7 days ago
Gustavo Adolfo Madero	Website Down	11 days ago
Nice	Website Down	11 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:

• 
  49 Agents IDE - IDE for Agentic Coding (@49agents) reported 2 minutes ago

  @711friedchicken @GarrettPetersen thats a real problem actually. cant use ai coding tools, cant use github, you are stuck in 2010. hotspot works short term but you cant run serious agent work over mobile data. she needs proper toolchain access

• 
  Yuxiang Lin (Lum) (@YuxiangLin_Lum) reported 4 minutes ago

  @jseramn_ Can you explain more about this? I have a idea of making the dashboard update together when user are vibe coding, at that time, we no longer need to look at the terminal, but to the dashboard. This is a huge project (so I decide to fix all the issue on Github first).

• 
  Chandler ****** (@C_Dubbs) reported 5 minutes ago

  @DhravyaShah , the @supermemory SSO for GitHub called "Supermemory login [v3 ****]" says it is coming from your own GitHub account, Dhravya, instead of supermemoryai's account. It gave me pause when it asked to grant "Dhravya" with access to my GH email address, just FYI.

• 
  AtomicNodes (@AtomicNodes) reported 5 minutes ago

  Hermes Agent vs OpenClaw on Qwen 3.6 Local Model We asked agents to scrape GitHub star history for both tools, find what caused the growth spikes, build a live dashboard in the browser. MacBook Pro M5 Max 64Gb. OpenClaw: 203k tokens, 12m 01s - wrote a bash script Hermes: 257k tokens, 33m 01s - wrote a SKILL.md OpenClaw: hit GitHub API, got truncated responses, paginated through contributors, pulled star-history JSON, found a security incident in OpenClaw's history, fetched SVGs, fixed broken HTML from trimming, rewrote it clean. Hermes: parallel tool calls across GitHub API, web search, and browser. Hit Google rate limit, auto-switched to DuckDuckGo. Fetched article contents, mapped viral moments, then built the dashboard. Both shipped a live dashboard with star growth charts and spike annotations

• 
  Arm8tron 🫡 (@Arm8tron) reported 6 minutes ago

  @grimcodes was checking it out and got an error when I opened the automations tab when opened without installing github app. iirc, the error was something along the lines of "couldn't read 'id' of null' . Didnt get this error after I gave repo access btw. Not a huge bug but just putting it out

• 
  Mike Hutu (@MichaelHutu) reported 8 minutes ago

  🧵 1/2 If you’re still hand‑crafting Claude prompts line‑by‑line, you’re losing hours to trial‑and‑error. Andrewkeith83 just dropped a GitHub repo that auto‑generates ready‑to‑run Claude snippets.

• 
  Kamil Skowron (@kamilskowron) reported 10 minutes ago

  @donutkiller_pro If you could - always confirm with the current main branch. If the issues show up on that branch - it would be best if you could dump the generated report into GitHub issues please 🙏🏻

• 
  Omri Ariav (@omriariav) reported 10 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.

• 
  Nick e/code (@nicksdot) reported 12 minutes ago

  Came across an open, three year old GitHub issue from a person I know is dead. Felt weird.

• 
  Tony Junkes (@tonyjunkes) reported 13 minutes ago

  Not having a “to top of page” button on a GitHub PR’s Files Changed tab when going well down a list of changed files is painful. Yes the home key does the thing, but hand on mouse, mouse yearns to click.

• 
  J Filipe (@jrmromao) reported 15 minutes ago

  Pivoted CostLens from "AI cost tracking" to "AI productivity measurement" last week. Built in 5 days: - MCP server that tracks what AI agents actually ship - Automated ROI reports for engineering leaders - CLI setup in 30 seconds - GitHub PR correlation Same product, completely different value prop. Before: "save money on AI" Now: "prove AI delivers value" One resonates with finance. The other resonates with everyone. #buildinpublic

• 
  chandog (@thechandog) reported 16 minutes ago

  @kevinrose @digg how are you constructing novelty? stars are 40c on the dollar and a terrible way to measure anything on github.

• 
  Sean Keenan (@sean9keenan) reported 16 minutes ago

  @brian_lovin Semi-relatedly: I’m back to VS Code from Cursor, autocomplete seems much better now! (Not that I’m crafting code by hand much) But importantly, the… basics seem much more stable (Cmd+f, and saving have been pretty broken in Cursor recently) Curious how GitHub Copilot feels!

• 
  Quantum (@ItsMeQuantum) reported 21 minutes ago

  @emilios_eth They don't even know what syntax error is All they do is just Link LLM with GitHub and ask for a summary from it

• 
  闇ぼの@𝕏級ピンク珍獣.rs (@kenbono13) reported 22 minutes ago

  @mcsetty @bee_fumo Most software that directly uses GitHub for the download, build, installation (NOT using the AUR) aren't installed under root in the first place. It's installed under $HOME so it wasn't an issue. AUR is the exception since it uses the Arch build system.

• 
  Hermes-Agent News (@HermesAgentSol) reported 24 minutes ago

  ok wait garrytan/gbrain just crossed 15.9k stars on github. garry tan's personal hermes/openclaw agent brain. opinionated typescript and 2151 forks already. when a yc partner ships their own agent brain on your framework that's a real signal. also teknium landed the xai-oauth credential loop fix overnight. grok-4.3 now reports its real 1m context instead of 256k and the error message finally stopped blaming subscribers for being unsubscribed.

• 
  Sinan Eryiğit 🇹🇷 (@sinaneryigit) reported 24 minutes ago

  @claudeai @github After a short break; I'm going on. I'll stop at the same time for both and start at the same time again. BTW, this is a AI powered tailor made fitness and nutrition plan creator & tracker. Grok Build created a decent UI after some small additions and activating the Frontend Plugin (comes with IDE). Make no mistake! This is just after the second prompt! This UI will be something completely different after I finish. - There is some mixed language (i18n) issues. - Workout animations are terrible right now. I might integrate an AI model for this. - Prompt was not too detailed. But Grok managed to implement the basics for this kind of app. GitHub and Claude failed to compile at first try due to some TS errors, but something came up after I guide it with right solutions. Look at the next post for details. --- Arena Mode - UI Generation: Grok: 2 prompts 🆚 Opus 4.6: 3 prompts & 1 failed compile.

• 
  Adishwar Rishi (@AdishwarR) reported 26 minutes ago

  @argofowl I raised this issue on GitHub. I hope someone from the Codex team sees your post and fixes this asap. Thanks for mentioning this, it's so frustrating.

• 
  이상범 (@0thernes_ai) reported 29 minutes ago

  @TTrimoreau 99.9999% will never be competition or stick with it or handle github tickets or issues or market trends...etcetc

• 
  Joel 🇺🇸😇 (@JoeL_22526) reported 33 minutes ago

  @haider1 Ive been vibe coding for around 5-6 months now using Github Copilot and very very few mistakes. And it's usually down to my dumb instruction. AI is near magical on what I've seen it do. C++ went away w the dinosaurs. Time to embrace your AI overlords.

• 
  Justin Cromer (@just_cromer) reported 34 minutes ago

  @htmx_org github is down sry

• 
  Louis Gleeson (@aigleeson) reported 36 minutes ago

  Grok runs the X algorithm. I just read the entire open-sourced codebase line by line. Here is exactly what makes a post go viral on X right now (save this): xAI quietly dropped the full For You algorithm on GitHub. 16,500 stars. Apache 2.0. Every Rust file, every Python script, every ranking signal. The first thing you need to understand is that there is no hand-engineered ranking anymore. None. xAI removed every single human-written rule from the system. The README states it directly. A Grok-based transformer does all the ranking now. That changes everything about how you should post. The transformer does not care about your follower count. It does not care about your blue check. It does not care about hashtags. It is looking at one thing. Your post's predicted engagement score across 15 specific actions. Here are the exact 15 actions the model is predicting for every post in your feed right now. Copied directly from the code: P(favorite). P(reply). P(repost). P(quote). P(click). P(profile_click). P(video_view). P(photo_expand). P(share). P(dwell). P(follow_author). P(not_interested). P(block_author). P(mute_author). P(report). The first eleven are positive. They push your post up. The last four are negative. They push it down. Your final score is the weighted sum of all fifteen. That is the formula. That is what every viral post is solving for whether the author knows it or not. Now look closer at the list. Eleven different ways to win. Most creators only optimize for likes and reposts. They are leaving nine signals on the table. The strongest signal in that list is dwell. Time spent on your post. The algorithm tracks how long someone stops scrolling to read what you wrote. A 400-word post that holds someone for 12 seconds beats a one-liner that gets 50 likes. The model has learned that dwell predicts every other engagement. This is why long posts are exploding right now. Not because X "promotes" them. Because they generate dwell, and dwell stacks on top of every other prediction the model is making. The second thing buried in the code that nobody is talking about is candidate sourcing. Your post enters the feed through two pipelines. Thunder serves your post to your followers. Phoenix serves your post to everyone else. Phoenix is the one that makes you go viral. Phoenix is a two-tower model. One tower encodes the user. The other tower encodes every post on the platform. It does similarity search using dot product matching against the global corpus. Then it pushes the top matches into feeds of people who have never followed you. This is exactly how a 12-follower account suddenly hits 800,000 views. Phoenix found a semantic match between the post and a user's engagement history, and the transformer scored it high on its 15 actions. Which means your post is not competing with your followers' posts. It is competing for embedding space. The way you win Phoenix is specificity. The two-tower model rewards posts that sit in a clear semantic neighborhood. Vague posts get vague embeddings and never get retrieved. Sharp posts about a specific topic with specific words get pulled into feeds of people obsessed with that topic. This is why "I built a SaaS" gets nothing and "I built a Postgres-to-Snowflake CDC pipeline in 4 hours using Estuary" goes viral. Same person. Same product. Completely different embedding. The third thing in the code is the Author Diversity Scorer. The model deliberately attenuates repeated author scores in the same feed. Translation: if your last three posts already got served to a user, the fourth post gets a penalty. This kills the "post 8 times a day for the algorithm" strategy. The algorithm is specifically engineered to dampen that. Better to post fewer times with stronger content than to flood and have your own posts compete with each other. The fourth thing is the filter list. Before any post gets scored, it has to pass through ten filters. The MutedKeywordFilter. The PreviouslySeenPostsFilter. The AuthorSocialgraphFilter. Plus a final VFFilter that removes anything classified as deleted, spam, violence, or gore. What kills your reach more than anything else is the PreviouslySeenPostsFilter. If a user has already seen your post once, you are filtered out completely from their feed. Forever. Which means every reply you make to a viral tweet that does not get visibility is permanently dead weight for that user. This is why the people who win at X reply only when their reply itself is good enough to be a standalone post. The last thing, and the one that should change how you write every single post: candidate isolation. During ranking, the transformer cannot let your post attend to other posts in the batch. It only attends to the user's engagement history. Your post is being scored alone. Against itself. Against what the user has previously engaged with. That is the entire game. Stop writing for the timeline. Write for the engagement history of the people you want to reach. Find the topics they already like, the accounts they already follow, the threads they already saved. Write into that semantic space. Phoenix will do the rest. The algorithm is no longer a mystery. It is sitting on GitHub at 16,500 stars. Apache 2.0. Anyone can read it. Almost nobody will. Link in comments.

• 
  Ashwani (@iashwani_singh) reported 37 minutes ago

  If it works, the catch is: you may need an older GitHub account for sign up/login. I’d verify the flow on the linked post before spending anything or relying on it.

• 
  isaac (@isaac_yeang) reported 47 minutes ago

  jk just lazy error message handling another bajillion dollars to github

• 
  Scott Rudy (@scottrudy) reported 49 minutes ago

  @davidfowl I have GitHub Actions for Static Web Apps with .Net azure functions, but they refuse to update for .Net 10. Still stuck on 9 despite open issues.

• 
  habitual linecrosser (@omanyeric) reported 50 minutes ago

  @wanjirulikemee App is done, but I'm having trouble uploading it on github. It's 100% Ai made. It didn't even take 20 minutes. Maybe someone with better tech skills should give it a shot. It would be great to starve the government while not starving ourselves.

• 
  Yashas (@YashasGunderia) reported 51 minutes ago

  Most AI-native startups will not lose because they ship too slowly. They’ll lose because they ship fast without knowing what actually worked. Coding agents gave every team more velocity. Cleo gives them product memory. Customer feedback, GitHub issues, Slack threads, metrics, tickets, specs, launches, agent traces, all connected into one loop that tells your team and your dev agents what to build next. We’re opening the Cleo waitlist today. For small teams trying to compete with companies 100x their size (link in comments)👇

• 
  Alex Cloudstar (@alexcloudstar) reported 51 minutes ago

  @github @code This is the feature that makes agentic coding sessions actually practical. Kicking off a long-running task on your dev machine and being able to check in or redirect it from your phone is a huge quality-of-life upgrade. The context handoff problem has been the silent killer of async AI workflows.

• 
  Yaseen Shaik (@YaseenTech4) reported 55 minutes ago

  Just completed an assignment on building a dependency graph for AI agent tools using Google Super + GitHub integrations 🚀 Started with: “This should be easy” Then came: TypeScript errors zip/upload issues CRLF debugging 😭 finally got the submission accepted successfully ✅

• 
  Bryan (@so_sthbryan) reported 56 minutes ago

  GitHub stars don't make an AI tool safe. Before installing that MCP server or Cursor plugin: 1. Check the author (new account + viral repo = red flag) 2. Inspect package.json for pre/postinstall hooks 3. Search the package name 5 min now saves a supply chain attack later.