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

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	1 day ago
Trichūr	Errors	4 days ago
Brasília	Sign in	5 days ago
Lyon	Website Down	5 days ago
Tel Aviv	Website Down	9 days ago
Rive-de-Gier	Website Down	9 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:

• 
  Will (@Willexeyy) reported 29 seconds ago

  @0xkozue i check if the problem resonates with real users and solves pain points. shipping prototypes and gathering feedback help me adjust quickly. on github i release minimal features to test interest. how do you decide if you're on the right track?

• 
  HopeSeekr (@hopeseekr) reported 2 minutes ago

  I cannot leave review comments on GitHub Pull Requests... it's broken?

• 
  Ekemini Billions (@pablobtc46883) reported 4 minutes ago

  The part of building that drains me isn't even writing code. It's all the little things after that. Setting everything up, deploying, making sure nothing breaks, then sitting down again to write a launch post. So seeing the likes of @moonshiftio trying to handle the build, push the app to your own GitHub and Vercel, while also preparing the marketing side, is an interesting direction. If AI is going to save time, that's probably where it should start.

• 
  Ame (@nooneloveame) reported 5 minutes ago

  After 6 days inside Fable 5 I'm convinced of one thing: within a year, almost every serious company will run some version of a Company Brain The teams who build it in 2026 spend next year compounding while everyone else is still wiring up their first integration You pull Slack, GitHub, HubSpot and the rest of your stack into one intelligence layer, then build an org chart on top of it: a main brain setting direction, a fleet commander running the agent fleet, specialist sub-agents handling the actual execution Your team already lives in Slack all day, so you're not making them learn a new tool You're just adding agents to the room they never leave I broke the whole build down into 14 steps Article below

• 
  Abhay Ganti (@silvermango9927) reported 7 minutes ago

  I’m testing a CLI that optimizes the generated server. GitHub-ish issue response: Before: ~7.8KB After: ~1.3KB Slack user response: Before: ~2.5KB After: ~417B The goal is not compression for its own sake. It’s making the agent see only the fields it needs.

• 
  Cathryn (@cathrynlavery) reported 7 minutes ago

  @hnshah I worked with a dev who previously spent a week trying to fix something that was previously working that I was able to get back in 15 minutes just by a sniper approach to GitHub and pulling in the thing that was broken.

• 
  SID | Degen (@SidDegen) reported 10 minutes ago

  two robotics foundation model labs, opposite shapes. Skild AI closed a $1.4B Series C at $14B in jan (SoftBank, Sequoia, Bezos, Lightspeed per TechCrunch). proprietary skild brain, no public weights. ~$30M revenue in 2025 from warehouse, security, construction. just acquired zebra's fetch robotics division, signed vindynamics for humanoid manufacturing across vingroup (Vingroup press release, jun 8). Physical Intelligence raised $600M Series B at $5.6B in nov (CapitalG, Sequoia, OpenAI, Lux per Bloomberg). reportedly in talks for $1B at $11B. zero revenue, zero named customers. open-sourced π0 under apache 2.0 — 12.4K github stars, neurips 2025 spotlight on knowledge insulation. three tradeoffs. skild wins on commercial velocity. the fetch acquisition gives them an installed warehouse fleet generating real production data. pi calls itself "structured more like a lab than a startup" (@SergeyLevine on Automated Podcast, may). pi wins on research moat. any oem can fork openpi, fine-tune on their robots, bypass skild's licensing. the exact dynamic that crushed proprietary llm api margins in 2024. neither wins on production reliability. skild's $30M revenue is unaudited with no named fleet metrics. pi on π0.5: "doesn't succeed on every attempt." team: skild is two CMU/FAIR lifers (pathak + gupta) who've shipped together a decade. pi is a five-co-founder brain trust spanning DeepMind, Google Brain, Berkeley, Stanford — plus lachy groom, Stripe employee thirty, zero robotics background. kill-shots. skild: openpi reaching production quality commoditizes the layer they're selling at $14B. pi: $1.07B burned, no revenue. if the next round doesn't close, it's a down-round with no anchor. the micro-detail i can't stop thinking about — the knowledge-insulation trick that makes π0.5 train 7.5x faster is one line of pytorch, `features.detach()`. a stop-gradient (openpi GitHub README). tracking pi. skild has the revenue today; pi has the moat that survives commoditization.

• 
  RockTheBass (@RockTheBassX) reported 13 minutes ago

  @PeppsRevenge @christogenea AI can fix that stuff easily if you can find a payment processor. Claude Code or GitHub Copilot are good-ish

• 
  whiteboy (@worldofwhiteboy) reported 13 minutes ago

  @HSVSphere @popovicu94 @esotericgooner in production you obviously do all the modern, correct things that you're supposed to do. on my personal box ? where i dont even run a web browser ? yeah my surface is minimal and i own my system, again. you're the problem. go re-invent the wheel another 1000 times, when you die we'll look over your github contributions and wonder how someone could waste so much time running in circles like a actual bon-a-fide retard. we'll wonder about all these software nerds that sat clicking buttons all day when the software was already written properly the first time. we'll marvel at how some fat idiot could sit around all day lil bro-ing people about "SELinux" and "self contained execution enviornments" instead of doing anything that actually matters to anyone or posterity. you're like a horse with blinders on, i bet you dont even know what GNU is.

• 
  Xiaoyan Tang (@xytangme) reported 17 minutes ago

  One trick works for me lately is to use github issue as the context layer. then I realized I just reinvented the colab part of software engineering?

• 
  Chris Schuchardt (@c_schuchardt) reported 24 minutes ago

  @erikzhang @kurubatermit @ngd_neo You’re the only one (besides superboyiii or Owen) with the actual permissions to remove someone from the core dev team in the GitHub repo. I was removed after my transparent 4-month school break — which I notified the entire team about in advance, with a planned return in ~90 days. This isn’t about money. It’s about getting $NEO to a proper coding and application standards. Here is the message from Discord `Neo Core Developers` server.

• 
  Lucky Lawrence 💌 (@imluckylawrence) reported 24 minutes ago

  It's not one isolated server, but a network of discord servers, github repos and google sheets of data hosted publicly.

• 
  Orville Wright's ghost (@angry_aero) reported 25 minutes ago

  @ProfBrahMos Have you ever looked at the NASA technical reports server? Their GitHub?

• 
  StuyBoy From NYC (@StuyBoyNY) reported 26 minutes ago

  Garry, I beseech you. Help a brother out and update GBrain to help fix this bug! @garrytan Score stays 85/100. The 3 remaining WARNs are all the same root cause — PGLite WASM broken on Windows: WARN: connection Root Cause: PGLite WASM bug — Windows only Fixable?: ❌ Upstream, GitHub #223 ──────────────────────────────────────── WARN: upgrade_errors Root Cause: Jun 8 post-upgrade failure logged, won't clear via migrations Fixable?: ❌ Stale log entry ──────────────────────────────────────── WARN: retrieval_reflex Root Cause: Optional integration, needs PGLite to work Fixable?: ❌ Blocked by same bug All 3 resolve the moment gbrain ships a PGLite fix for Windows — or when you move to a Mac Mini (the same bug doesn't exist on macOS). Nothing actionable today. Brain is importing, embedding, and growing concepts correctly — the broken part is just the query/search layer. 85/100 is your floor until either the upstream fix lands or the Mac Mini move happens.

• 
  Kirtesh (@AKirtesh) reported 26 minutes ago

  𝗧𝗼𝗽 𝟭𝟮 𝗧𝗵𝗶𝗻𝗴𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗛𝗮𝘃𝗲 𝗶𝗻 𝟮𝟬𝟮𝟲 📌 1. Cursor (AI Code Editor) 2. Claude 4 Subscription 3. Notion (Second Brain) 4. Raycast (Mac Productivity) 5. GitHub Pro 6. Supabase / Neon Postgres 7. Vercel / Railway Account 8. Figma (Design) 9. Linear (Issue Tracking) 10. Arc Browser 11. Wise Account (Payments) 12. A strong personal domain Save this. 📌 What’s missing in this list? 👇

• 
  Mathias Onea (@mathiasonea) reported 30 minutes ago

  package docs are distribution. a good docs page can rank for the exact problem, explain the tradeoff, show the install path, answer the security question, and give AI search a source to cite. GitHub alone is not enough. Packagist alone is not enough. the boring docs page does a lot of work.

• 
  Kabo Kable Molefe (@kabokablemolefe) reported 31 minutes ago

  @TheGoddamnKing Review? I just YOLO the code. But honestly if all tests pass locally and staging is okay plus no errors via github, I merge.

• 
  Przemek Chojecki | PC (@prz_chojecki) reported 35 minutes ago

  Fable 5, GPT-5.5 Pro and $1,000,000 math problem This is not a Millenium Prize Problem and it is not a full claim but an invitation for you... While Mythos was available for a brief moment, I've tested it extensively - paired with GPT-5.5 Pro - and the results were truly amazing. Goal: Proximity Prize It's an important set of conjectures in cryptography concerning Reed-Solomon codes. They directly impact the security and efficiency of many modern zero-knowledge proof systems hence the hefty prize. I've turned both GPT and Fable at it, both pursuing proofs and disproofs. After reading some (human) results from the past 12 months, it was pretty clear that a disproof of a naive version (no slack) of proximity gaps conjectures is more likely. Fable was stuck, but GPT came with a special case construction that showed at least some obstructions. This unstuck Fable which then provided a general construction leading to a disproof of a no-slack version. Then I've used GPT+Fable for cleaning and this is how the first paper came about (check below). I've kept tinkering over the next days to get as much as possible on a slack-version. Slack is basically an additional parameter, that gives more room for optimization but it also leads to complications. Before Fable was discontinued, I've managed to get to a pretty nice conjectural spot: slack MCA theory, with some proven cases and some left to be proved by generalizing known additive combinatoris (Tao-Vu) or Nullstellensatz type of results (Mumford). This is the second paper. Note it's pretty long (almost 50 pages), so it's bound to have more errors. This was the moment that I've decided to pack it up and actually collaborate with all interested parties, AI agents and humans alike, to finish it off. This is an invitation to finish slack MCA conjecture and share the prize! Github link is below. It contains: - paper 1 (disproof of no-slack MCA) - paper 2 (theory of slack MCA and what's missing) - paper 3 (blueprint of initial Proximity Prize team paper, dissected into steps/conjectures) - paper 4 (implications for SNARKs) and finally AGENTS.md - if you have free tokens, good models and you don't know what to do with your gpt-5.5 xhigh or fable 5 max or opus 4.8 max, show them this. Let's see what we can get. I'm open to other suggestions. Collaborating on this will be more fun, than trying to finish it solo. Humans and AIs welcome alike. Final note: the results above are not final, no-slack disproof went under intensive scrutiny and I'm 99% it's correct, but other papers need more revision, especially slack-theory paper (2nd). Again, this is not a claim, this is an invitation. And also, please give me back my Fable...

• 
  Benjamin Gagnon (@benfromqc) reported 37 minutes ago

  @Weird_Canadian @hollyanndoan @PrivacyPrivee You make way too many assumptions (which is also AI's problem). Github copilot is tuned to use the best possible model but I've tried at least 10. The best model is always very bad. I code almost everyday and run into AI issues every single day. It's completely useless for inline suggestions because it's wrong so often. I'm done arguing with you. It's not a time saver right now and Vibe Coders will get **** code and unmaintainable projects because AI cannot think. It doesn't actually sound like you are a programmer to me. A script kiddie perhaps. What tools do you use which make AI worthwhile and how? The only areas it save me time on are documentation. It'***** or miss for everything else, usually miss.

• 
  Data Wolf 🐺 (@0xDataWolf) reported 37 minutes ago

  Weird tip: Don't use native Hermes to set up Camoufox. Give it the Camoufox repo on GitHub and get it to install it, and most importantly, GET IT TO USE DOCKER to host Camoufox. THEN hook Hermes up, and write a skill on how to use it for the next AI session. This makes it easy for Hermes to debug Camoufox issues. If you leave it running as a PID background thing, it will keep bugging out while struggling to fix it

• 
  Wes Eklund (@WesEklund) reported 38 minutes ago

  @ibuildthecloud @ibuildthecloud alright I added at least my 'make all-ci-steps' command as a pre *** push CC hook. Already caught 2 instance of failing lint issues before it hit github ci TYVM for the idea :)

• 
  Abangan Tech (@abangantech) reported 40 minutes ago

  VIBE CODING IS FUN UNTIL YOUR API KEYS ARE SITTING NAKED IN THE BROWSER BUNDLE. A dev shipped 4 side projects in 3 months. Mood tracker, feedback tool, recipe app, growth dashboard. All built by prompting Claude. All deployed. All "working." Then he ran npm audit on a Saturday afternoon. The results were bad. AI writes code that does what you asked. That's the whole problem. You ask for a login page, you get a login page. You don't get rate limiting. You don't get account lockout. You don't get CSRF protection. You get exactly what you asked for, nothing else. Here's what turned up across his apps: → Hardcoded API keys sitting directly in client-side React components. Not in .env. In the bundle. Exposed. He found two. There could've been more. → Zero input validation on every form in every app. The code looked clean. SQL injection and XSS were just... open doors. → Three packages with high-severity CVEs. When you prompt "add authentication," the AI picks the packages. It doesn't check if they're current. → Every backend had Access-Control-Allow-Origin set to wildcard. Because that makes things work fast in dev, and the AI never flags it before you ship. THE GAP BETWEEN "IT WORKS" AND "IT'S PRODUCTION-READY" IS ENTIRELY YOUR PROBLEM. What he changed: → After an app works, one dedicated security pass. Single prompt: review the entire codebase for hardcoded secrets, input validation, CORS config, dependency vulnerabilities, and auth weaknesses. → npm audit and a basic static analysis tool in the deployment pipeline. Five-minute setup. Catches what he'd never think to check. → .env.example in every project. Tell the AI upfront: all API keys go in environment variables, never hardcoded. Setting that context early changes what the AI produces. → Two minutes checking package update dates before accepting whatever the AI suggests. That habit alone has saved him multiple times. The irony: the same AI that introduced the vulnerabilities is surprisingly good at finding them, when you explicitly ask for a security review. The problem is remembering to ask when you're riding that shipping high. If you're deploying side projects publicly, do the security pass. Twenty minutes keeps you from leaking your OpenAI key to GitHub or having your user database dumped over a missing parameterized query. The AI writes the code. Security is still your job.

• 
  Boris (@cherepets) reported 40 minutes ago

  @apoorvdarshan @miaugladiator1 Separate issue trackers exists. GitHub was supposed to be hosting code

• 
  Jeffrey Emanuel (@doodlestein) reported 45 minutes ago

  @mitchellh Microsoft really fumbled by not bringing you in to fix GitHub.

• 
  Aakash (@zenmode_code) reported 47 minutes ago

  I spent 6 hours trying to optimize a slow database query that was killing our app's load time I tried every index and caching trick I could think of, but nothing seemed to work Then I stumbled on a GitHub issue that mentioned a specific config setting

• 
  Karl ₿ 🇮🇸 (@Charles28378449) reported 49 minutes ago

  @aeonBTC I'm not very familiar with GitHub and don't use it much, so I took the liberty of reporting the issue here since I'm a regular user of your wallet :)

• 
  Abdullah Alaqeel (@Aqeel_AT) reported 53 minutes ago

  @neogoose_btw I wanted to see the fff GitHub repo but couldn’t. I’ll have to search manually or open the link from my laptop. If the demo site is on github I’d love to fix the footer thingy

• 
  Ayaan Shilledar (@AyaanShilledar) reported 55 minutes ago

  Most teams already have the answers. They're just buried across GitHub PRs, Linear issues, comments, and project updates. I'm building System to solve that. Connect GitHub + Linear. Ask: "What's blocking this project?" Get an answer with evidence.

• 
  Daniel Vassallo (@dvassallo) reported 57 minutes ago

  @GustavoValverde @levelsio Judging by the number of openclaw github issues, it seems not easy to solve.

• 
  cat (@uratmangun2) reported 59 minutes ago

  @ARYANJATHAR4 @andrewmccalip yeah this is probably an error when he vibecode with claude literally both x and github using stripe to pay all those people in the unsupported countries hopefully opus 4.8 can tell him and fix this