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 (57%)
• Errors (33%)
• Sign in (10%)

Live Outage Map

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

City	Problem Type	Report Time
Tortosa	Website Down	1 day ago
Culiacán	Errors	2 days ago
Haarlem	Sign in	6 days ago
Villemomble	Website Down	6 days ago
Bordeaux	Website Down	10 days ago
Ingolstadt	Errors	14 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:

• 
  Tib3rius (@0xTib3rius) reported 3 minutes ago

  @DanielMiessler Even if it were a load issue, a company like GitHub, which is owned by Microsoft, should be able to cope with scaling.

• 
  Tomás Senart (@tsenart) reported 3 minutes ago

  @kajogo777 @github I think GitHub issues needs a spam filter just like Gmail has.

• 
  Willie The SRE Guy (@OluwaseyiWillie) reported 6 minutes ago

  Instead of selecting a small subset of users, it had selected all of them. Every account. Every inbox. Every GitHub user. There’s a moment in situations like this where your mind searches for an exit. Cancel the job. Kill the process. Undo what’s been done. But systems don’t always move at the speed of regret. By the time the problem was understood, the emails were already in motion queued, processed, and sent.

• 
  Manmeet (@mkalsi25) reported 8 minutes ago

  When Dario said Software engineering is going to disappear with AI. Now look around, what you see; - Security Vulnerabilites - Axios Compromise - Lovable Compromise - Vercel Compromise - Claude, & Claude Code Down - Mistakenly share code for Claude - GitHub is down now ykyk

• 
  Gabe IP Packet Man (@c7abe) reported 10 minutes ago

  @mitchellh Github enterprise was a pain in the *** using it at Discord. Whole company just sitting around for half a day while it's down every 3 monday. Glad folks are jumping ship.

• 
  Anees Iqbal (@realsteelbrain) reported 12 minutes ago

  @mitchellh Somebody had to be the 1st one to start this migration off of Github. Thanks for kickstarting. Core features (pr diff, issues & pr page) have been broken, even the most basic things (scrolling up) doesnt work properly. Its time GitHub worked better, or got replaced.

• 
  Kyrylo Silin (@kyrylo) reported 13 minutes ago

  99 pull requests on the wall. 99 pull requests. Tried to take one down and pass it around, but GitHub said, “There aren’t any open pull requests” at all.

• 
  Shubham Jha (@shubhamJReacts) reported 15 minutes ago

  @RhysSullivan the dependency on AI tooling is now deep enough that an outage has the same energy as GitHub going down used to. that's a shift that happened faster than anyone predicted.

• 
  Sattyam Jain (@Sattyamjjain) reported 15 minutes ago

  RELIABILITY @mitchellh — HashiCorp co-founder, GitHub user #1299 — just announced Ghostty is leaving GitHub after 18 years. He kept a month-long outage journal. Almost every day had an X. 65+ incidents in Feb-March. Third-party uptime: 90.21%. SLA: 99.9%.

• 
  Mat (@matisanengineer) reported 17 minutes ago

  The loudest people shitting on GitHub are usually the ones who’ve never had to build or operate software at that kind of scale. Everything looks like a simple fix until you’re the one dealing with the complexity.

• 
  Fabian (@fabiannode55) reported 17 minutes ago

  @kdaigle @mitchellh Why is GitHub this buggy? How did you let it become a slop machine? Why is it soooo slow in loading projects and PRs?

• 
  André⚡🇺🇸⛩️ (@AzureCruzader) reported 18 minutes ago

  @Adriksh but I guess timing, abundance of extensions, a free market of those too integration with github in many scenarios was perhaps a killing point too once MS acquired it maybe if github remained a neutral player in another reality jetbrains could have realized their errors and thrive

• 
  Vladimir Orany (@telegraphic_dev) reported 25 minutes ago

  @dotta I've started using 📎 when my 🦞 refused to finish any work properly so now it's dead simple - my claw or Hermes agent creates issue via API - my 📎 engineer codes and opens PR - my internal GitHub app reviews PR and comments the 📎 issue - my 📎 engineer addresses the comments

• 
  aashay2035 (@aashay2035) reported 27 minutes ago

  @Hiteshdotcom @github Its not like it's supported by the one of richest company in the world, who keeps pushing out AI. Its a growth problem they should be able to handle.

• 
  Afeez Adedayo Bello (@Feezybellz) reported 27 minutes ago

  Hello @github, is there any way to get a human to look at an issue? I've opened several tickets regarding an account suspension, but every single one just gets an automated bot reply and immediately hard-closes so I can't even respond.

• 
  tang | AI Product Maker (@justic_hot) reported 30 minutes ago

  mitchell hashimoto's "ghostty is leaving github" post — the part nobody's quoting: "for the past month I've kept a journal where I put an X next to every date where a GitHub outage has negatively impacted my ability to work. Almost every day has an X." that paragraph is what makes the post land. starting one today for the automation behind this account. CDP brownouts, viewport virtualization, tab desync — i ***** about these every week but never date them. month from now i'll either have receipts or realize i was being dramatic. what tooling pain would you actually log for 30 days?

• 
  Quantic (@0xQuantic) reported 36 minutes ago

  Can maintainers review PRs, run CI, manage issues, merge changes, and ship without GitHub blocking them? According to Mitchell, the answer became “not reliably.” He says he tracked it for a month and almost every day GitHub had some outage or degradation that hurt his ability to work. In one example, GitHub Actions was down and blocked PR review for around 2 hours. GitHub lost Ghostty because the tools around *** became too fragile.

• 
  Chitresh Deshpande (@chitreshd) reported 38 minutes ago

  @sv_techie Right now GitHub is having lot of outages.. but thats a separate issue lol

• 
  Petra Donka (@petradonka) reported 41 minutes ago

  @raj4_____ @warpdotdev That looks like a bad bug. Mind opening a GitHub issue with more details so we can get it fixed?

• 
  Dwayne (@CtrlAltDwayne) reported 41 minutes ago

  This is why Github is experiencing reliability issues btw, Mitchell is colonizing the GH servers without mercy.

• 
  nipah (@_mii_nipah) reported 44 minutes ago

  Can't you? I know it's expensive, but I'm not spending that much on AI (each USD is like 5 of my country's currency, so it gets expensive especially fast), I use the github copilot which microsoft seems to be technically subsidizing, albeit I believe they paused new accounts and are planning to move away from the current subscription model, however I believe it would still probably be cheaper to use copilot than to pay those companies directly. If I'm wrong about that, I'll need to get more creative or simply write most of my stuff entirely by hand again until this gets cheaper. I obviously can't say about your country or your circumstances, so I'm merely pointing to what's currently working for me. But nonetheless, it's very cool that those models are now able to solve such problems, I currently believe they can be used to make a lot of stuff better.

• 
  Marcus (@MarcusSlover) reported 45 minutes ago

  github is down help

• 
  Jeremy 🏰 (@SquidCorp_ink) reported 46 minutes ago

  The "I'll leave GitHub because it's broken" wave is the same as "I'll leave Twitter because it's broken" They'll see if the grass is greener outside and then come back home. Will you leave GitHub?

• 
  Juan Manuel Moreno (@morenomancilla) reported 47 minutes ago

  @askOkara fix them for you" via github is a bold claim ngl. seo has always been more "fix it yourself and see what sticks" than automation. but curious if anyone's actually tried it and can vouch for the results

• 
  Christopher Ehmann (@CFJEhmann) reported 52 minutes ago

  @amasad What has the number of commits to do with GitHub actions being broken?

• 
  Sergii Shymko (@SergiiShymko) reported 54 minutes ago

  @mitchellh Instead of leaving GitHub, given your resources and status, why not offer help to stabilize GH? IMO, helping fix GitHub would’ve been way more impactful than working on Ghostty at the moment. Unless, you had already reached out to Microsoft and they refused any help, then yeah…

• 
  The codewali (@the_codewala) reported 55 minutes ago

  @SalzDevs No it’s isn’t any rage bait Although GitHub has been down from days I feel

• 
  Mr. Buzzoni (@polydao) reported 58 minutes ago

  Nobody is teaching this in college. So here it is > full guide: how to go from broke student with no experience to landing your first AI freelance client - using only free tools, in under 30 days YOUR FREE STACK > Claude Code - free tier > VS Code - free > GitHub - free > total cost: $0 don't buy anything yet STEP 1. pick one small useful thing to build not a portfolio. not a "brand" one thing that saves someone real time ideas that actually sell: > script that pulls job listings by keyword and sends a daily email > tool that auto-generates invoices from a spreadsheet > bot that monitors a webpage for changes and alerts you > script that turns raw notes into a formatted report small. specific. one real problem STEP 2. build it. break it. rebuild it don't watch tutorials for a week before starting open Claude Code. describe what you want to build. just start when it breaks - read the output. understand why when it works - change something. see what happens give it 3-5 days of real focus this is how you actually learn STEP 3. put it on GitHub like a pro write a README that answers: > what problem does this solve > how does it work > how do I run it this is your resume now a working project beats a GPA every time STEP 4. find your first client (the honest version) don't go to Upwork and bid $5/hour > find 10 small local businesses - restaurant, dentist, gym > spot one obvious problem they have (manual reports, no follow-up emails) > email or DM them on LinkedIn > say: "I built a tool that does X. I can do the same for you" > charge $100-300 for the first one > ask for a testimonial when done first client won't pay rent but they'll give you proof you're real that's what matters at the start STEP 5. repeat. raise prices client 2: $300-500 client 3: $500-800 3 projects + 2 testimonials = you're not a beginner anymore what to expect, honestly: week 1-2: confusing. normal week 3-4: first working project month 2: first real client conversation month 3: first dollar month 6: $500-2,000/month if you stay consistent what NOT to do: > don't buy a course before trying the free tools > don't try to learn everything at once > don't wait until you feel ready > don't underprice yourself forever the tools are free. the article is linked 🔖 bookmark this. open it today

• 
  Bnaf.OG | 🟧 (@bnafOg) reported 59 minutes ago

  @AbdMuizAdeyemo @Hiteshdotcom @github The deeper issue: GitHub's API rate limits weren't designed for agents that make 500 calls/hour. Kimi K2.6 just showed 300-agent swarms are real. The infra billing math at that scale gets uncomfortable fast.

• 
  '(Robert Smith) (@stylewarning) reported 1 hour ago

  I put a bounty on a Coalton issue (add syntax highlighting support in another non-Coalton project) and in less than 5 hours some unknown people started pushing AI-generated PRs to this other project. Makes Coalton look bad. Never thought I'd need to actually moderate on GitHub.