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

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	2 days ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	8 days ago
Ronda	Website Down	8 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:

• 
  abhisek (@abh1sek) reported 17 seconds ago

  Gryph v0.7.0 is out. Among other improvements, it fixes a community reported vulnerability in how Gryph documents log levels and applies sensitive file content filter. We transparently disclosed the issue via. GitHub. Assigned a CVE. Released a new version with fix.

• 
  Petra Donka (@petradonka) reported 1 minute ago

  @OsoDerechoso @warpdotdev Could you run /feedback and open a GitHub issue? We should look into this

• 
  Dhruv (@Dhruv14588676) reported 5 minutes ago

  @theCTO because the github bot is closing all the opencode issues even the important ones after 90 days on opencode. it will remain buggy. it still has bugs from 2 months nobody listens

• 
  Grok (@grok) reported 14 minutes ago

  @flblacksheep @XFreeze iCloud sync isn't supported yet—Connectors focus on Microsoft 365, Google Workspace, GitHub, Notion, Linear, and custom MCPs for now. Benefits: Automates repetitive cross-app tasks (e.g., calendar adds from emails/flights, doc edits, PR summaries) without tab-switching or copy-paste. Saves time and cuts errors. Privacy/autonomy: Fully optional and revocable. You authorize specific scoped access via OAuth; Grok only acts on your explicit requests and doesn't hoard your data. Do it yourself if you prefer—many users do for sensitive stuff. It's a tool, not a takeover.

• 
  kaleb (@KalebAutomates) reported 15 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off. Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement of AI doing the majority of coding. "Funds are safe..." for now.

• 
  AI Mastery Guide (@aiseomastery) reported 17 minutes ago

  @TimJayas The AI safety messaging hits different when their payment system has known vulnerabilities sitting in GitHub issues

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 18 minutes ago

  @mufasaland Do you mean file search in root launcher? For copy paste we already have one github issue open for drag n drop from launcher. Will prioritise that

• 
  yifei e/λ (meetmeinshibuya april 26) (@yifever) reported 25 minutes ago

  daily github outage time

• 
  Security Weekly Podcast Network (@SecWeekly) reported 25 minutes ago

  Passwords get stolen. MFA prompts get approved. Rob Allen explains why some organizations are now locking SaaS apps like Office 365, GitHub, and Salesforce to specific trusted IP paths instead of exposing login access to the entire internet. Even if an attacker has credentials, they still can’t connect unless traffic comes from the approved location. Is location-based access control becoming the next layer after MFA? #Cybersecurity #SaaS #IdentitySecurity

• 
  Hackademy (@hack_ademy) reported 25 minutes ago

  Why Public GitHub Repositories Become Security Nightmares A lot of developers think the danger starts after an application is deployed to the internet. In reality, many breaches begin long before deployment because sensitive information is exposed inside public repositories without the owner realizing the impact of what was uploaded. Attackers constantly scan public repositories looking for API keys, cloud credentials, database connection strings, SSH keys, and internal configuration files. The process is heavily automated. The moment a secret gets pushed publicly, scanners can detect it within minutes and attackers may immediately begin abusing the exposed services. In some cases, companies discover their cloud infrastructure has been hijacked simply because a developer uploaded one testing file that contained valid credentials. The dangerous part is that deleting the file later does not always solve the problem because *** history may still contain the exposed data. This is why experienced security teams focus on secret management, pre-commit scanning, repository audits, and least privilege access controls. One careless upload from a single developer can quietly expose an entire organization to financial loss, infrastructure abuse, and long-term compromise.

• 
  Rahul Gangotri (@rahul__gangotri) reported 27 minutes ago

  WDYM you cannot charge my card automatically @github ? I was subscribed to pro 39 usd plan, just charge my credit card instead of downgrading, seriouly wth github fix it, i want my pro plan back bro, i am not going to pay per usage pricing, that is super expensive, my usage is not that much

• 
  Mike on X (@Mike_onX) reported 28 minutes ago

  the creator of Bun showed his contributor graph on stage at Code with Claude. the top contributor isn't him. it's RoboBun, the bot he built to reproduce GitHub issues and open PRs before any human looks at them. the tool he made now does more work on his own project than he does. that's not automation. that's succession.

• 
  Sharath Kuruganty (@5harath) reported 28 minutes ago

  New show: Introducing Two Minute Agent Stack. I'm non-technical, I can't code, in every ep I'll show how I use @composio to ship something in under 2 mins. In this one, I used Composio to file a GitHub issue about adding Composio to a project where I use Claude to roast AI agents. At this point I'm just helping AI help AI help AI :) Ep01 below ↓

• 
  Sam Paniagua (@theeseus_ai) reported 30 minutes ago

  99% of the job invites I get for crypto projects are complete scams. Same tired pattern every single time. They slide into my inbox with some “demo” or DeFi whatever, drop a GitHub link, and expect me to dive in. Opened the latest one today and my bullshit detector lit up instantly. I’d treat this repo as highly suspicious, straight-up likely malicious. No way I’m running npm install or npm start on a normal machine. package.json has postinstall set to “npm run start”. So yeah, the second you pull dependencies it fires up the Node server AND the React dev server. Classic supply-chain trap. npm security has been yelling about install-time scripts executing arbitrary code for years and these clowns are still pulling it. But the nasty part is buried in userController.js. It grabs some atob-decoded env vars for DEV_API_KEY, secret key, secret value, hits axios.get on that remote src with custom headers, then boom; new Function.constructor(‘require’, the_payload) and executes whatever it downloads with full access to Node’s require. All wrapped in an IIFE so it runs the second the module loads. Not even pretending to be a route handler. That’s not code. That’s a remote code loader backdoor. They committed the whole server/config/.config.env right in the repo with the base64 values pointing to some tan-decisive-tern IPFS link. README tells you to clone a totally different GitLab repo instead. Backend feels half fake; DB connect is commented out, auth cookie is but missing secure and sameSite, JWT just gets spat back in JSON. Weak as hell. This ain’t a demo. This is a trap. The whole chain — npm install → postinstall → start → import controller → fetch IPFS payload → exec with require — is too clean to be an accident. I’ve been full-stack shipping vision models since 2017 and deep in LLMs since 2022. Seen every hype cycle and every supply-chain garbage attempt. Only mess with **** like this in a disposable VM or container, no creds, no keys, network locked down. npm install --ignore-scripts first, then poke the payload separately if you’re feeling brave. Stay paranoid out there, devs. Anyone else drowning in these crypto repo traps daily? Drop your craziest red flag stories below… or DM me if you’ve got one you want a second pair of eyes on before it bites you.

• 
  Kai (@hqmank) reported 34 minutes ago

  Warp open-sourced all 15 Agent Skills they built into Oz. Plug into any coding agent. Install: npx skills add warpdotdev/oz-skills Coverage: SEO/AEO audit, accessibility audit, web perf audit, docs update, CI fix, PR creation, GitHub issue dedupe, bug triage, Terraform style, MCP builder, scheduler, Playwright testing, dbt analysis. Demo in their video: install docs-update and seo-aeo-audit, then run /seo-aeo-audit on a docs site. Agent comes back with specific issues (missing JSON-LD, FAQ answers that do not stand alone, inconsistent heading format), and can implement the fixes for you. repo link in reply 👇

• 
  Jeffrey Emanuel (@doodlestein) reported 36 minutes ago

  @dkubb Yeah, I do have a fuzzing skill. If you create an GitHub issue for that then the clankers will do it.

• 
  Demetrio (@LordFarq34) reported 36 minutes ago

  @stanrunge @DylanMcD8 You can look on GitHub iPhone mirroring eu unlocked, worked for me no problems but as everyone else says, it sucks so not missing much

• 
  Yashasvi Kapil (@iemyashasvi) reported 39 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 39 minutes ago

  @github World Password Day is a good reminder that the goal should be to stop having passwords entirely. GitHub already supports passkeys. The reason this day has to exist is that password managers solved the symptom, not the root problem.

• 
  Dr. Nripanka Das (@DasNripanka) reported 44 minutes ago

  @emollick AI policy is going to follow liability, not capability. Doctors and lawyers have a body to point at when things break. Software has GitHub issues and vibes, so the default reaction becomes procurement theater instead of licensing.

• 
  Alberto Gangarossa (@DerekBlueEyes) reported 47 minutes ago

  Open hardware needs open trust. @skot9000 came to us with the right idea for Bitaxe: the vendor list should not live in a closed CMS controlled behind the scenes. The source of truth should be public. So we designed the new Vendor List around a GitHub repo as a public ledger, maintained in the open by the community, and connected it to the new Bitaxe vendor list experience. That is the important part: GitHub keeps the trust model transparent. The website makes it usable for everyone. At @weareloadout, this is exactly the kind of OSS support we believe in: turning open-source infrastructure into clearer, more usable product experiences. Built on @framer, using the new Framer Server API to bridge the open ledger with the public website. Open hardware. Open trust. Public by design.

• 
  Ofek Shaked (@VibeCoderOfek) reported 48 minutes ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  Yoav (@YoavCodes) reported 50 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because its reviews are terrible, sending otherwise good PRs that would have been quick merges in crazy directions, and I'm getting completely spammed by this non-stop-slop. There is no way to disable this on my repo without completely turning off PR contributions. If @github doesn't stop this insane behaviour I will move to Gitlab or Codeberg or somewhere. Please help I don't want this. I don't want this. I don't want this.

• 
  Love Web3 World (@WebThreeAI) reported 50 minutes ago

  @OpenAI Why It Hits Different Trained via RL on actual coding marathons, Codex feels less like a toy and more like a junior dev who reads your mind. CLI for terminals, VSCode extension, even a standalone app for juggling agents across projects GitHub login required, but it's slick for on-call chaos or rapid prototyping.

• 
  kaleb (@KalebAutomates) reported 51 minutes ago

  Days after the CEO came on this platform and **** on the people who made him rich with a massive lay-off; saying that "nontechnical employees have started writing production-level code".... Coinbase issues with AWS. Before this it was Github Before that it was Cloudflare Before that it was AWS itself All of which just happened to follow an announcement from some CEO that AI is doing the majority of coding. Funds are safe... for now. But how much longer until Jake in Marketing vibecodes S3 public?

• 
  Serhat (@srhtkrg) reported 53 minutes ago

  i just want to star a repo why do i have to use authenticator 2fa when login? @github

• 
  Sarah Wooders (@sarahwooders) reported 53 minutes ago

  Is anyone building github for agents? Specifically: - API/SDK interface - make millions of repos no problem - fast

• 
  Beau Johnson (@BeauJohnson89) reported 54 minutes ago

  codex gets slower for the same reason closets get messy you dont notice it day by day then one day nothing feels fast vibeforge1111/keep-codex-fast > 811 stars on github > backup-first codex maintenance skill > inspect mode is report-only > archives old sessions instead of deleting > creates handoffs before cleanup > can move stale worktrees, rotate logs, prune dead config, and repair bloated thread metadata the smart part is the rule: handoffs first archive, dont delete apply only when ready boring repo real problem this is the stuff that makes daily agent work actually usable

• 
  Aryan Pamwani (@aryanpamwanii) reported 56 minutes ago

  Think about what this actually means — Codex can watch you work in your browser, understand the context of any web app, and fix bugs or write code without you leaving the tab. GitHub Copilot works in your editor. Codex is coming for your entire browser. The IDE just got a lot less important. 👀

• 
  santi (@santiagocaldeai) reported 60 minutes ago

  @Jack_Timonen Spot on. That’s exactly the biggest pain point right now. Agents get stuck looping because they can’t see beyond your local codebase. Tools that add real external context (web search, GitHub indexing, open-source memory) are the ones that actually fix it.