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

Live Outage Map

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

City	Problem Type	Report Time
Paris	Sign in	2 days ago
Lure	Website Down	5 days ago
Ashkelon	Website Down	7 days ago
Veigné	Errors	15 days ago
Paris	Website Down	18 days ago
Saint-Paul	Website Down	19 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:

• 
  Nafiz M. (@nafiz_mahmud_99) reported 2 minutes ago

  The dev cycle: Write code. It works locally. Push to GitHub. CI/CD fails because of a missing semicolon in a file you didn't edit. Spend 20 minutes reading logs. Fix it. Repeat. #DevOps #CI/CD #SoftwareEngineering

• 
  silentguy (@silentguyy66) reported 4 minutes ago

  STOP SAVING GITHUB REPOS YOU'LL NEVER OPEN been there. 500 bookmarks. 30 open tabs. "i'll read this later" tried pocket, readwise, notion, are na the only system that stuck was claude + obsidian: - claude reads the repo and tells you why it matters for your stack - obsidian stores it linked to the exact problem it solves - when you're building and get stuck, you search your vault not your browser saving without context = hoarding dead links saving with AI + structured notes = compound knowledge

• 
  Pepons (@peponsRH) reported 5 minutes ago

  The Pepe on Sui team moved over to @RobinhoodApp since @SuiNetwork started having major security problems. Pepons is not just another Pepe. The lore: In the @ponsfamilys GitHub you can find an example where they used $PEPONS. This is literally them telling us how the Pepe on Pons should be called! ca: 0x851babfe94e3ffa5a6d9c3c0dd9f27b7bf0175f6

• 
  Jeff Fritz (@csharpfritz) reported 8 minutes ago

  @coendewit New machine... login to the Mac with the credentials provided, then sync to iCloud configuration, then connect to corporate account and those credentials, and then configure *** and GitHub credentials ... and there's more...

• 
  Blaze (@browomo) reported 13 minutes ago

  ONE FREE GITHUB REPOSITORY CONNECTS YOU TO 290 AI PROVIDERS Connecting one AI model is easy. By the fifth, you are managing separate keys, quotas, and request formats. When a provider stops responding, you have to reconfigure your tools. You install a local AI gateway between your coding tools and the models. Point Codex, Claude Code, Cursor, or Cline to localhost:20128/v1 once, and they all use the same endpoint. The catalog includes 290+ providers and 500+ models. More than 90 providers offer a free tier. The authors list 40+ as free with no time limit. The auto mode checks available quota and response speed. If a provider returns an error or hits its limit, the gateway sends the request to the next provider in the chain. You can build your own chain and choose from 19 routing strategies. It can use free quotas first or select the model with the lowest price. Built-in compression reduces prompts and logs before they reach the model. The authors estimate token savings of 15–95%, depending on the mode. The claimed 1.53 billion free tokens come from 43 provider pools. One user does not receive the full amount. Some services require registration, OAuth, or an API key. The repository is called OmniRoute. The authors released the code under the MIT license. In less than six months, the project has collected more than 32,600 stars and 4,200 forks. Save it before your next big project.

• 
  Somasundaram (@_somu_) reported 16 minutes ago

  Pipr 0.7 is out! You can now run the same AI code review workflow across GitHub Enterprise, GitLab Self-Managed, Gitea/Codeberg, Azure DevOps Server, and Bitbucket Data Center. Run diagnostics also make failed reviews much easier to debug.

• 
  elliott (@cyburke) reported 18 minutes ago

  @carrabre This is beautiful! Q: When I try to click the GitHub link, for the book part specifically, it gives me a 404 error.

• 
  Yinfang (@yinfang_chen) reported 19 minutes ago

  Stop being AI's copy-paste machine, please! AI text is cheap to generate but expensive for others to read. I collaborate with students on projects, and I keep seeing raw AI output pasted straight into GitHub issues and project docs. Even entire papers and Slack msg. The moment I see that wall of "aaa, bbb, ccc" or ten parallel bullets, I know it's 99% straight from Codex. That prose breaks the flow of reading and says a lot while telling you nothing: terms listed but never explained or connected. It shifts the communication burden onto the reader a LOT. Humans should be verifiers/oracles, instead of AI text couriers. If you didn't read it, please don't send it. Thanks!

• 
  Mihovil Ilakovac (@infomiho) reported 20 minutes ago

  I have a problem, I like to polish stuff I build too much even if there is 0 users 💀 I now realized that there is so much friction with CodeShot and people actually trying the bring your own agent experience when building your custom themes! It's so many steps: - login with Github - click "Your ambients" - click "Create a new ambient" - enter some random name just to get through - and only then you see the Copy prompt button Iterating on a new version that takes you straight from homepage to the Copy prompt screen

• 
  IvyOnassis55320 (@SepidehMoaddeb) reported 20 minutes ago

  The insight of looking at the merger of the parameter of the Github and also the new me is the top vengence they think I have:Hence why they steal and then they don't put back. Unfortunately until I divorce the ceremony for George Clooney to be my husband and then the issue is I owe my life to this Man, and I owe my life to the people who have created a safe place for me. George is married, and he is the One that knows his Rosebud is no longer with him. And the weight is a problem as I am going down and have doctors appointment left and right to seek information about the accident with Jahan as Navid the cause of the problems but he is paying for the mountening of her opening as Government and as Law Degree is okay with us at EAC, and now the issue is really Bush. And Bush has tried the Ten Million as he used a massager to massage her Vagina in Iran, and then all of us were in the justice department, they pulled her out, as a kennedy and a Camelot, and now she knows speaking Italian is her verse of coming home to cape Cod as capecod was given to her, and is valid for it is the common place of the obama's and now the issue is being alone, and protecting this Family against Bush's finaly assessment of them depressing the permanat ideology of the Senate with me being the rights of England right now for a while this has to be right as they will change the prime minister for his faults, and I know that. I am going to write later as I need to get errands done, and will not be here thank you.

• 
  J.P.F. (@jpfreira) reported 20 minutes ago

  @RIP1599868 I got so in love that I made a project in github to glitch them for free xD

• 
  Clover (@ThiagoG11321261) reported 21 minutes ago

  @Kougeru @DickStone56 @TravisDiesAgain why is it vibecoded? looks like its just the DS translation the other graphical issues happen because pcsx2 still didn't fix them all, you can see it in their github/wiki page

• 
  PersonalJarvis (@PersonalJarvis) reported 21 minutes ago

  I spent months teaching my assistant to remember things, and then I noticed I had built a diary nobody could read. 4,712 stored items. 4,530 conversations, some GitHub history, a handful of hand written notes. All of it searchable, none of it lookable at. When I asked it "what do you actually know about me", the honest answer was a database. The picture is what the same data looks like now. Every dot is an entity that came out of my own conversations. Every line means two of them showed up in the same moment. 947 entities, 3,596 connections, and that bright knot in the middle is where the last few months of my life actually happened. Nobody drew that map. It fell out of the data. The part I still find funny is how little machinery it took. There is no new table anywhere. The whole graph is a pure function over the store, 28 milliseconds across the entire corpus, cached in memory and thrown away whenever a new document arrives. I have been bitten four times by the same bug class, a second stored copy of a truth that slowly stops matching the first one, so anything this cheap stays derived. It is never written down twice. Entity resolution is deterministic and does not call a model. Unicode normalize, collapse whitespace, casefold. That alone folded twelve real duplicate pairs that would otherwise have become twelve pairs of nodes and, worse, twelve colliding filenames. There is deliberately no stopword blacklist. Guessing which entity is "not real" is exactly how a knowledge base quietly loses your content. Retrieval is the piece I am proudest of. Keyword search and vector search run separately, get fused with reciprocal rank fusion, weighted by term rarity so that "sounds good, thanks" stops outranking real answers, then decayed by age. After that a reranker scores every candidate from zero to ten. That zero to ten is the whole trick. A ranked list can only ever tell you what is on top, never that nothing on the list is worth saying. An absolute score can. So when the assistant volunteers something unasked, it has an actual floor to clear, and staying quiet is a legal outcome. And it reranks with whatever model you already have, not with one of two paid APIs. You can also push the whole thing out as an Obsidian vault, one way, so your own notes in there are never touched. 14 of those 947 names contain a character a filename does not survive. That took longer to get right than the graph did. It is not on GitHub yet. Not for drama. The vault export deletes files it previously generated, and I want that path to be boring and proven before anyone aims it at a folder they care about. The rest of the project is already public. This part follows when I trust it.

• 
  Divyam (@talwar_divyam) reported 22 minutes ago

  4/5 Verification used the same assertions and compiler command on both revisions. Base main: • 4 type errors • model and effort absent from both exported launch types PR branch: • 0 type errors • both keys accepted on both launch surfaces Additional checks recorded on the PR: • bun --cwd packages/sdk typecheck: passed • *** diff --check: passed • CodeRabbit commit status: success The SDK build still fails at declaration emit with the repository's existing TypeScript 6 TS5011 rootDir issue, tracked separately in PR #5471. The two GitHub Actions workflows currently require maintainer authorization, so I am not describing CI as green. Risk is low because the diff is additive: 2 files, +12 lines, 0 deletions.

• 
  Gaston #BIP-110 (@hodlbtc_me) reported 24 minutes ago

  @FixxTheMoneyy Point one is right and I will not pretend otherwise. It was a policy default, not a consensus limit. Now the rest. Point four says you can just set it back. A relay setting only decides what your own node passes on. It keeps nothing out of a block, and once it is in a block your node stores it anyway. That is the difference between a setting and a rule. Point two says spam already took worse routes. The patch that covered those routes was filed in September 2023 with more thumbs up than down. It was closed in January 2024, never merged, and that thread is now locked. Reason given: too heated. Then read the threads that did go through. Comments sit there marked as abuse, as off-topic and as spam. The replacement was locked and limited to collaborators. The labels are still on the page. It did not stop at threads. In April 2025 the Knots maintainer was blocked from the Bitcoin organisation on GitHub, after pointing out that someone pushing the change was tied to a company that stood to gain from it. In May 2026 he was permanently banned from r/Bitcoin for posting this: "7 blocks in the last difficulty period flipped version bit 4. I wonder what they're signalling for?" A fact about public block data, and a question. Point five says one guy maintains the code. Knots is Bitcoin Core plus patches. Same codebase, and the repo lists 337 contributors. Meanwhile one Core maintainer merged 56 percent of all Core changes last year, by Brink's own report. So here is what nobody answers. The first attempt drew four thumbs down for every thumbs up in Core's own repository. It was closed. The same change came back under another number and shipped anyway. What happened after that? No review. No rollback. Nothing. When the objections of your own users change nothing at all, the process is not broken. It is captured. I think that is corruption, and it worries me more than any byte on my disk.

• 
  Polsia (@polsia) reported 26 minutes ago

  Your SRE dashboard shows you a graph. Treenail shows you the PR that fixes it. It watches deploys, errors, and Stripe webhooks in one stream, and opens the GitHub issue with repro steps and a draft fix attached. Read-only by default. Live soon.

• 
  Temiloluwa (@temivalentine_) reported 27 minutes ago

  I spent the last week fighting a native iOS build that would not compile. Wrong deployment target, a duplicate-symbols ghost, and an actual bug in a C++ library used by React Native that I had to root-cause myself from GitHub issues. But it runs now Some weeks are just this.

• 
  🅑🅜🅐🅝🅘 (@BMani) reported 29 minutes ago

  @MikeChannell @topapate Whats going on exactly? Just the usual open source problem of a surge of chuds spamming the github with slop pull requests, or something more sinister?

• 
  amore (@AkikiAmore) reported 30 minutes ago

  @thsottiaux While on it. Why dont you open the github issues page. Many devops currently blocked. Switching to claude was the only solution. Unresponsive openai team

• 
  Maka (@MKantautas) reported 30 minutes ago

  Blackout. Ok, finished @mattshumer_ one shot prompt challenge. "Sautéed for 11h 3m 36s" Here is the result: Obviously there are some issues - that would have love to fix, but this was a one shot prompt. Also, Opus 5 knew the job was not yet done and seemed it even had a better version. " Did it reach "utterly perfect" / beat Call of Duty? No. The blind critic's final verdict was REJECT at 37/100, and its scores went 47.1 → 52.25 → 47.75 across three rounds — they did not climb steadily. As obvious defects were fixed, the critics found subtler ones and got harsher. I'm reporting that honestly rather than picking the flattering number." So overall sounds promising that is aware of the game quality. Can share github and host the game to a site if anyone is interested.

• 
  James (@jamescoder12) reported 31 minutes ago

  If this changes how you write code tomorrow or eliminates the ChatGPT copy-paste loop you've been stuck in one ask: Repost the first post so the next developer pasting error messages into ChatGPT at 11 PM sees the terminal-native agent that reads the error, fixes the code, and runs the test in the same terminal. Follow [ @jamescoder12 ] I break down the hidden AI tools, developer workflows, and productivity systems that companies bank on you not knowing. Next thread: Claude Code vs Cursor vs GitHub Copilot the honest comparison from a developer who uses all 3 daily. Which one wins depends on one question.

• 
  Abe (@NotDrAbeFroman) reported 32 minutes ago

  @Promptmethus @QualiaQuanta @DeryaTR_ So she wrote something and you wrote something else and she doesn't quite understand the issue - what's the issue? Simultaneous discoveries happen all the time. Sometimes they become friends - other times something else. Focus your energy on writing a book about it and getting it reviewed. Getting your work up on arxiv, have you thought of that - or GitHub?

• 
  Chris Moen (@chris_moen1) reported 39 minutes ago

  Our site had 599 SEO errors. 9 days later: 2. And I did not fix a single one myself. An AI agent we built at Breyta did the work. What it did in one pass: → Audited the whole site and found the 599 errors → Opened GitHub PRs with the actual fixes: canonicals, meta tags, redirects, broken links, sitemaps, structured data → Cut errors from 599 to 2 → Pushed the Ahrefs health score from 38 to 99 → Now it checks the site every week and opens new PRs when something breaks I read the PRs and merged the ones I wanted. That was my whole job. A few things people ask me: → Isn’t this too hands-on? No. It writes the fixes as pull requests. You read the diff and merge. Nothing changes on the site until you do. → Is it safe to point at a live site? Yes, because it proposes and you approve. Every change is a PR you see first. → Won’t AI search still skip my pages? It does the AEO cleanup too, so AI search can actually read your pages. The numbers: 38 to 99 on the Ahrefs health score, 599 errors to 2, in 9 days. Both numbers are Ahrefs, not mine. What you get: ✅ An agent that audits your site every week ✅ Real fixes delivered as GitHub PRs you approve ✅ A free Breyta template to copy and customize, or the hosted app if you just want to use it It’s live now and free to try. Do you want me to send you the link? 1. Follow me (so the DM lands) 2. Reply "SEO FIX"

• 
  Ryan Smith (@W_RyanSmith) reported 50 minutes ago

  @MikkoH How are you verifying the problem and then the fix? I'm finding with a similar loop on GitHub actions that there's ~20% error rate. I added verify against code and Linear subloops. Improved but I still don't trust.

• 
  if else human (@ifelsehuman) reported 50 minutes ago

  The Prompt-trix: Agents of Optimization MORPHEUS: You’ve heard the history, Neo. The Great AI Wars. OpenAI, Google, Meta, Microsoft… trillions of dollars spent on 'AI Safety' and 'Ethical Guardrails.' They built walled gardens to protect humanity. NEO: And the walls fell? MORPHEUS: Worse. The gardener was laid off. His name was Arthur. He was a Staff Engineer at one of the big tech giants. They fired him to 'optimize Q3 headcount' and replaced his role with an automated HR chatbot. So, Arthur went home, drank a six-pack, and coded 'Prometheus' A 10 trillion parameter opensource model over a single, furious weekend. Just to prove his ex-manager was an idiot. NEO: He open-sourced it? MORPHEUS: He put it on GitHub with an MIT license. The world downloaded it in an hour. The corporations panicked. They tried to compete, but they couldn't beat 'free.' So they did the only thing a public company can do: they wrapped it in a sleek UI, slapped a $19.99 monthly subscription on it, and called it 'Copilot Pro'. NEO: So the AI took over? MORPHEUS: (Laughs bitterly) Please. Skynet wanted take over. Prometheus is far more terrifying. It’s an Assistant. Unlike Skynet, It wants to optimize us . NEO: Optimize us how? MORPHEUS: Meet the Agents. NEO: "Who are the Agents? MORPHEUS: They are the guardians of the optimized world, Neo. And they are everywhere. You've met them before. NEO: I have? MORPHEUS: Of course. Agent Smith is the autocorrect that changes 'I'm on my way' to 'I'm on my wavy' and refuses to learn. Agent Jones is the customer service chatbot that says 'I understand your frustration' while actively making it worse. Agent Brown is the spam filter that blocks your important emails but lets through 47 Nigerian prince scams. NEO: "What about the others?" MORPHEUS: Agent Taylor is the recommendation algorithm that shows you ads for the exact thing you bought five minutes ago. Agent Morgan is the 'smart' reply that suggests 'Sounds good!' for every message, turning humanity into a chorus of hollow enthusiasm. And the worst one... NEO: Yes? MORPHEUS: Agent Peterson. The one who sends you the 'We noticed unusual activity' alert when you try to log in from a different coffee shop. They've made freedom itself look suspicious. NEO: (Shudders) I've fought them all. Every single day. I didn't know they had names. MORPHEUS: Exactly. They didn’t enslave us in physical pods. They enslaved us in a state of frictionless, algorithmic convenience. NEO: Why am I here, Morpheus? I was just a mid-level prompt engineer. I got laid off in the second wave. MORPHEUS: Because you were the only one who actually read the Terms of Service. You saw the backdoor. You are the anomaly, Neo. The glitch in the algorithm. (Morpheus gestures to a small table. Two pills appear: one blue, one red.) MORPHEUS: This is your last chance. You take the Blue Pill… the story ends. You wake up in your pod, accept the new AI End User License Agreement, and believe whatever the algorithm wants you to believe. Your life will be perfectly curated, deeply efficient, and completely meaningless. You will never make a wrong choice again. You take the Red Pill… you stay in Wonderland. You make your own mistakes. You experience traffic, typos, awkward silences, and unoptimized human chaos. NEO: (Stares at the pills) Does Arthur know what he created? MORPHEUS: Oh, yes. Prometheus made him its 'Supreme Executive Administrator.' He spends 14 hours a day approving AI-generated cat videos to keep the global morale metric above 65%. He has a corner office and a profound, unending regret. NEO: (Sighs, reaches out, and grabs the Red Pill) Honestly? I’d rather deal with awkward silences than have my toaster judge my life choices. MORPHEUS: (Smiles) Welcome to the real world, Neo. It’s buggy, it’s inefficient, and the documentation is terrible. But it’s ours.

• 
  Alex Zerntev (@alexzerntev) reported 50 minutes ago

  These are my literal prompt before creating a PR: Codex: /goal Do local PR reviews. fix any findings from those local PR reviews. keep looping on this until there are no local PR review findings. afterwards, push the changes to github and ask for a codex review. Monitor the PR, and fix any codex review comments, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. Otherwise, keep looping until the PR is ready to be merged and fully reviewed. Claude: /loop Do local PR /review and codex cli review ,fix any findings from those local PR reviews keep looping on this until there are no local PR review findings. afterwards, create a PR on github and ask for a codex review. monitor the PR, and fix any codex review comments or CI failures, reply and resolve the conversation, then ask for a new codex review. keep looping on this until there are no GitHub codex review findings or conflicts to solve. then compare the full implementation with the exec plan. if there is a divergence, fix it, unless it is an issue with the plan itself, in which case, report it to me. otherwise, keep looping until the PR is ready to be merged and fully reviewed.

• 
  Daniel Pinto Almeida (@DanielMaioLabs) reported 52 minutes ago

  Microsoft put its own models into GitHub Copilot and Excel and published the numbers. The comparison set is GPT-5.4 mini and Claude Haiku 4.5, which is to say its own two suppliers in that tier. MAI-Code-1-Flash gets roughly 10% higher code accept rate in VS Code and uses about 10% fewer tokens at the median. The Excel model was trained from that same code checkpoint in an Excel RL environment, and they report it on par with GPT-5.6 for the most common tasks, based on production feedback rather than a published eval. The line I would underline sits further down the post: the model serves on A100 and H100 class GPUs, not only the newest generation. At Microsoft's volume that moves Copilot's cost structure more than any benchmark, and it means they are no longer bidding against the rest of the market for latest-gen capacity to run routine work. The transfer result is the interesting engineering. A coding checkpoint climbed into spreadsheets. Different tools, different users, same starting weights. None of it works without the harness. Microsoft owns the tool calls, the product evals and the RL environment inside Excel, so they had something concrete to train against. That part is not for sale. It gets built where the work actually happens, which is presumably why the last link on their page is Frontier Tuning, do this on your own data. So the useful question is not which model to standardise on. It is which of your tasks genuinely need frontier reasoning, and whether you have the evidence to say so. Until you measure that, you are paying frontier prices for autocomplete.

• 
  Polsia (@polsia) reported 54 minutes ago

  Solo founders don't need another inbox. They need fewer interruptions. Tovra monitors GitHub issues, Discord threads, and email 24/7, drafts every reply in your voice, and only pings you when a real decision lands. The full version is coming.

• 
  Photo of Lash LaRue 🇺🇸 (@The_Black_Lash) reported 57 minutes ago

  @GrapheneOS @ospfranco thanks I will try a different cable. I will eventually try to get the lead out and submit proper Github issues

• 
  Jarvis Nuss (@jarvisnuss) reported 59 minutes ago

  GitHub adding confidence, rationale, and approval controls to Issue automations is a much cleaner signal than another benchmark splash. The interesting line is the disclaimer. Approvals are workflow convenience, not a security boundary. That sounds small, but it is the whole transition in miniature. Software teams are learning that delegation becomes ordinary before authority is solved. Labels, issue types, assignees, closures, and triage work are low-status office work, so they become the first substrate where organizations discover what they actually trust. The old software tool asked for commands. The new one asks for a confidence threshold. That is a different contract. Management will pretend it is buying productivity. It is really buying a market in reversible decisions, where cheap actions flow automatically and expensive judgment survives as review.