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

Live Outage Map

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

City	Problem Type	Report Time
Itapema	Website Down	9 days ago
Tlalpan	Sign in	14 days ago
Quilmes	Website Down	14 days ago
Bengaluru	Website Down	17 days ago
Yokohama	Sign in	17 days ago
Gustavo Adolfo Madero	Website Down	21 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:

• 
  sam (@metruzanca) reported 6 minutes ago

  @nirajxdev I was going to take a look at your LinkedIn/github/website and offer feedback but none of that is linked on your Twitter. Do the other 3 have that same issue of not linking to the others?

• 
  Joe Quinn (@itsjoequinn) reported 9 minutes ago

  @RohitPaulK @osquarski Just ran into this too. Pushing an empty commit to the PR to restart CI triggered a new build instead of github the error.

• 
  xenstudio (@xen_studio) reported 11 minutes ago

  @JackWoth98 Hey @JackWoth98 -- not trying to pester, but is there a github issue I can follow for this ? It's my primary limiter from switching away from gemini.

• 
  Gregor (@bygregorr) reported 12 minutes ago

  @Manz github login on a local model was always cooked

• 
  PEPE 🔮 (@pepearaucano) reported 13 minutes ago

  @TheQuest_1 @bankrbot We're facing the biggest elephant in the room the industry has seen in years. GitHub is completely broken and patched together. Agents need repositories tailored to their needs. The world is moving towards open source, and large companies are starting to pivot to it.

• 
  Abhishek Sharma (@Abhishe04755332) reported 14 minutes ago

  My Go API was firing webhooks to external services. Anyone who knew the URL could send fake events. The receiver had no way to verify: "Did this actually come from my server?" GitHub, Stripe, Twilio all solve this the same way: HMAC signing. Here's how I added it 🧵

• 
  Daniil (@hey_daniil) reported 15 minutes ago

  Taking a break from the website and doing some product work. GitHub Issues and Asana are now properly supported in devintern/pm

• 
  Yashasvi (@_iamyt_) reported 18 minutes ago

  The problem: I had 6 tabs open just to check my own progress. GitHub here. LeetCode there. Codeforces somewhere else. Internship emails buried in Gmail. DevMirror pulls it all into one place — and actually tells you what to focus on.

• 
  Patrick Roza (@Patrick_Roza) reported 27 minutes ago

  Another day another @GitHub issue, or 10.

• 
  SeaTicket (@SeaTicketAI) reported 29 minutes ago

  @0xcaosheng_888 The Agent continuously analyzes issues on its own and suggests next actions automatically. For example, it can draft a reply to a GitHub issue or Discourse thread, and team members can review, edit, approve, or discard the suggestion. Once approved, SeaTicket automatically posts the reply back to the original thread.

• 
  Yashasvi (@_iamyt_) reported 30 minutes ago

  The problem: I had 6 tabs open just to check my own progress. GitHub here. LeetCode there. Codeforces somewhere else. Internship emails buried in Gmail. DevMirror pulls it all into one place — and tells you what to focus on.

• 
  vasin (@vasinwr) reported 31 minutes ago

  coding agents can do a better job than me in keeping the github issues updated / organised as I work. I never had the attention to keep updating it in detail. this is an example where I asked @TabTabTabAI to work on something end to end, in this case make sure bun is installed in the AMI. i told it to work in a new worktree, create PR, link it to the issue, and do full verification (create new AMI, provision new VM through local controlplane service, and smoke test the installation)

• 
  arko📕 (@edt_arko) reported 32 minutes ago

  An open-source AI agent just hit 170,000 GitHub stars in 3 months. It learns from its own work. Runs on YOUR server. Never forgets anything. And the token isn't even out yet. Everything you need to know about @NousResearch Hermes Agent 👇

• 
  Jose Gurruchaga (@jsgrrchg) reported 35 minutes ago

  I love @github . Please @Microsoft fix the reliability and the diffs!! I can't imagine a world without it 😭

• 
  Lucy Farnik (@lucyfarnik) reported 37 minutes ago

  @AlbertRSalter @DanNeidle Yeah but it is included in the chart. I've opened a GitHub issue about it

• 
  Chris Kearney (@SiliconForested) reported 37 minutes ago

  My advice to anyone spending 400 dollars a month or more on AI engineering: You need to ensure your claude/codex/whatever has access to github via the gh command line tool. Only do work that originates from a ticket / gh issue. Tell claude to create high quality tickets with acceptance critieria and then give the ticket to a clean context ai agent. Have the agent update the ticket when the work is completed. Tickets or groups of tickets turn into Pull Requests. Run the pull request through 5+ rounds of "hostile PR feedback". Only merge code that can survive the hammering of hostile PR review(s). If you're in the middle of a session and you notice something you want to change, resist the urge to do the work right there in the session, tell claude / codex to create a ticket that you can come back and give to an agent later. It's good hygiene that allows for a number of gains when it comes to troubleshooting, adding additional agents to a project asychronously (gh issues distribute the queue of work and track state) and planning / estimation It will feel like you're going slower, but you're not. You will spend more time troubleshooting the projects that lack this level of hyigene than you will use time upfront to do work in this manner

• 
  Rhea Karuturi (@MillionPageProj) reported 41 minutes ago

  wrote a bunch of blog posts about the projects I built + cleaned up my github and I WILL be making that everyones problem by posting about it relentlessly soon 😎

• 
  ShWnD (@h3xhammer) reported 41 minutes ago

  A fork of the original N!ghtm@re 3cl!pse BL bypass might still be available on GH: MS can get fukt. Fix your sh!t, don't cens0r. fckng tw@ts

• 
  Isaac Way (@isaac_ts_way) reported 42 minutes ago

  @theo @adamdotdev Yeah idk how anyone argues github is not doing a terrible job Their service bricks every 2 weeks while also not having shipped or changed anything signficant in a long time

• 
  ✰λster✰ (@4ster_light) reported 43 minutes ago

  This release has been named in an alternative PEP440 compliant manner due to github immutable tag collision issues

• 
  Aries Spring (@AriesSpring__) reported 50 minutes ago

  @nicklaunches @launch_llama Github auth not working, when authing with x, it gets stuck in a loop of email verification -> sends you code on email -> you submit -> you get that prompt to verify email again -> repeat

• 
  Saravanar Boopalan (@saran_saravanar) reported 50 minutes ago

  1/3 Before: I used to manually review code in GitHub, scrolling through endless lines, searching for issues. It was time-consuming and often led to overlooked bugs. [NO]

• 
  gaurav (@Itstheanurag) reported 52 minutes ago

  @venkateshdotdev Bro GitHub is down every week, everyone I know hates it. It's just there's no alternatives.

• 
  Juan Montesinos (@jfmontgar) reported 54 minutes ago

  @rauchg Why would then the quality of GitHub get worse over time? In my company we faced two severe bugs where our devs would face restricted access and did not even appear in the logs. This infra is now vibecoded or issues the more they integrate Microsoft services.

• 
  w (@retrievaaaa) reported 58 minutes ago

  @atomicbyte_ @stupidtechtakes i know like 2 people that have gotten banned from github (both for no reason though, but their support is so slow it both took them like weeks if not months to get their bans lifted) they ban more than you would think they would

• 
  Rithvik (@OutlierInMaking) reported 58 minutes ago

  @arvind_xdd @toeknee_kim only if a huge swarm of techies upload on spaces like github. Why you may ask, its because whoop regularly takes down posts which show reverse engineering researches. See it is pretty simple, whoop is just a 3-4$ sensor. i dont want to tell more cuz of whoop lawyers and policy-dm

• 
  Elliot Hesp (@elliothesp) reported 58 minutes ago

  Yeah pretty sure GitHub is having issues... yet again...

• 
  Aliaksandr Valialkin (@valyala) reported 1 hour ago

  @JasonThorsness I never hit into this issue, and I write a lot of code in Go - check my GitHub account.

• 
  Tynach (@Tynach) reported 1 hour ago

  @FakePsyho … runtime, and Unity had a Github repo for its fork of Mono, organized by Unity version.. So I found the version of the Mono runtime used by the Unity version KSP used, and compiled it from source for my CPU architecture. This fixed the performance issues. I don't know if (c)

• 
  Pablo Pablo (@navtechai) reported 1 hour ago

  @rohanpaul_ai Using original tasks instead of public GitHub issues the model already saw. What a concept.