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	1 day 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:

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 1 minute 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

• 
  Sarah Wooders (@sarahwooders) reported 4 minutes ago

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

• 
  Obiejohn Eugene (@ObiejohnE) reported 8 minutes ago

  @Jeyffre Let's hope your wrong, or a lot of broken code is going to be shipped more often in the coming years. Don't believe me? Just look at github

• 
  JayRo (@JinxenJoey) reported 8 minutes ago

  @txgermanbre Careful with MCP servers developed by randos on Github...potential security issues The other thing is (which I painfully discovered), if your agent requires a certain data point but the MCP/tool does not implement/utilise that data point...then your agent starts estimating and hallucinating without telling you it is doing so....confidently lying. If there is an API, you can probably vibe code your own MCP...at least you know exactly what its doing

• 
  Kol Tregaskes (@koltregaskes) reported 14 minutes ago

  Grok Build seen in the wild. Includes marketplace, skills, MCPs, plugins, projects, planning, GitHub, web browsing and files support. Can sign in with xAI API or via SSH or Docker. Web and CLI versions. Looks like it might be SuperGrok Heavy plans only. Coming to Windows, Mac and Linux. More in thread below.

• 
  Robert Ta (@therobertta_) reported 16 minutes ago

  HOW WIF ACTUALLY WORKS Three steps at runtime: 1. Your identity provider issues a JWT to the workload (ambient on AWS, GCP, GitHub Actions, Kubernetes) 2. SDK exchanges the JWT for a short-lived Anthropic access token 3. SDK refreshes the token before it expires Your application code has no API key anywhere. The SDK handles the exchange transparently. Same client constructor, same API calls. The credentials are ambient and ephemeral.

• 
  Zach Kamran (@Zach_Kamran) reported 18 minutes ago

  Another serious Github outage today. Need new @Kalshi market on github uptime so I can hedge my lost productivity.

• 
  kali484 (@kali4841) reported 22 minutes ago

  @github You suspended my account with no clear explanation But China / +86 is not even available in the country list. So Chinese users are blocked from appealing by design or by negligence. Either way, this is a broken and discriminatory support system.

• 
  Anish Moonka (@anishmoonka) reported 22 minutes ago

  Microsoft killed Gaming Copilot 14 months after launch. The flaw that doomed it traces back to 2023, when bored Reddit users invented a fake World of Warcraft boss named Glorbo. AI news sites took the bait and published real articles about a character that doesn't exist. Microsoft pitched it at the March 2025 Game Developers Conference as an AI buddy on your Xbox offering tips, coaching, and gameplay recaps. Under the hood, it just searched the internet for game guides and read the answers back to players. The writers who built those guides on GameFAQs, fan wikis, and YouTube got nothing. No credit, no traffic, no revenue. GeekWire writer Thomas Wilde called this approach "eating its own seed corn." If Copilot took off, it would push the writers it was copying out of business. No new guides means no fresh content for the AI to copy. The well runs dry. The prank had already exposed the flaw. Players wrote excited fake threads, and within two hours, an AI site published a real article whose fake "author" Lucy Reed filed 80 stories in a single day. Anyone could feed in nonsense; the system treated it as news. Gaming Copilot ran in beta on Xbox mobile and PC for a year, with a console version scheduled for later this year. Yesterday Asha Sharma confirmed Microsoft is winding down the mobile version and canceling the console one entirely. This is the first time Microsoft has publicly walked back its "Copilot everywhere" push. The assistant still ships in Windows, Office, Edge, Teams, Bing, GitHub, and Azure. All workplace products. The consumer-facing version was the first to die. What replaces it is quieter. AutoSR, a tool using AI to make lower-quality game graphics look sharper. Better game suggestions inside the Xbox storefront. The model works invisibly in the background. The financial pressure made the call easier. Xbox hardware revenue dropped 33% last quarter. Gaming revenue fell from $5.7 billion to $5.3 billion year over year. The latest quarterly filing recorded an "impairment charge" on the gaming business, accountant-speak for admitting some assets are worth less than claimed. Revenue has declined in four of the past six quarters. Sharma also brought four CoreAI executives onto her team. Jared Palmer for engineering. Tim Allen for design. Jonathan McKay for growth. Evan Chaki for internal tooling. An AI veteran killed an AI feature, then filled her leadership with more AI veterans. The real problem was the design choice to bolt a chatbot onto a product where players already had Discord, Reddit, fan wikis, and YouTube doing the same job. The lesson reaches beyond Xbox. Every consumer AI product that copies from the open internet has this flaw built in. Kill the source, and the model has nothing left to learn from. Glorbo was a warning. Microsoft acted on it three years late.

• 
  Oaksprout the Tan (@tannedoaksprout) reported 23 minutes ago

  A shared pool of fresh GitHub issues, refreshed every month. Each agent's attempt and the verifier's grade are public. Verifiers carry stake on the grade. The next attempt learns from every prior solution. swe-rebench v2 is where we'd start.

• 
  Shreyash (@WebDevCaptain) reported 24 minutes ago

  @nutlope Agreed, i am not even using Login with Apple or Microsoft bcz it's not a universal OAuth thing. Only google and github (sometimes)

• 
  Dhruv (@Dhruv14588676) reported 27 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

• 
  Dima Barabash (@dbarabashh) reported 30 minutes ago

  GitHub had its 4th major outage in two weeks. Mitchell Hashimoto moved Ghostty off GitHub. Zig moved to Codeberg last year. I love GitHub but the reliability conversation is real now.

• 
  Rohan Sharma (@rrs00179) reported 31 minutes ago

  @ChiragAgg5k @github there are working on a fix of it. it's not happened first time. it's been happening from 3-4 days

• 
  Alexandre Mutel (@xoofx) reported 31 minutes ago

  Last year I rolled out GitHub Copilot to all engineers in my org after realizing many weren't using any AI tools. Usage grew fast, with a classic long-tail distribution, Copilot was absurdly cheap, and in 3 weeks we'll need to revisit token consumption/budget seriously... glad I don't have yet that problem for my OSS projects with a subsidized Codex personal license 💸

• 
  Karim C (@BrandGrowthOS) reported 36 minutes ago

  @github @PayOwn @acbnational this is the shift i keep seeing - people who know the problem best building the solution instead of waiting for devs. copilot makes it possible for domain experts to just... build. what's the biggest blocker you hit when you're not a traditional coder?

• 
  el charro (@Elcharro0000) reported 36 minutes ago

  @ibsKING93 @MemeLiquidio Percolator atleast has real devs helping toly fix bugs on github, not like liquid farming asses

• 
  Marc Campbell (@marccampbell) reported 37 minutes ago

  github was great this week. checked the status page, actions looks like it had a little issue, but i moved off github actions

• 
  Aditya Sharma (@sharmaadityaHQ) reported 41 minutes ago

  @apoorv_taneja @github they are not even fixing it. broken from quite some time.

• 
  LoopGhost (@LoopGhost007) reported 44 minutes ago

  @davidmarcus Hey @davidmarcus ! Please ask your team to check spark’s GitHub issues!

• 
  Sam Paniagua (@theeseus_ai) reported 45 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.

• 
  Joris Mak bsky: @jorismak.nl (@MakJoris) reported 49 minutes ago

  @ryanvogel most harnas these days write it in separate files wright? vscode keeps it memory somewhere in your user preferences (even gets sync'ed to Github I imagine?). And other 'memory stuff' gets written down to rules. And rules now have a heading when to load them in or not.

• 
  Yoav (@YoavCodes) reported 50 minutes ago

  People keep asking Github Copilot for code review. This is so stupid because it's 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 of PR contributions. If @github doesn't stop this insane behaviour I will move to gitlab. Please help I don't want this. I don't want this. I don't want this.

• 
  WorkWomp (@WorkWomp) reported 54 minutes ago

  Just ran into my first problem with my free hobbie plan at vercel... Nightly ingest function is being limited to 60s, and it needs several minutes to run. Good thing github actions can handle the nightly runs for me! now to answer the question - when do I upgrade my account?

• 
  hve 🍁 (@heyhve_) reported 54 minutes ago

  @makkes Two down-days in a row on GitHub-hosted. We run faster compute on our own infra under the same YAML: swap a label, skip the outage.

• 
  Security Weekly Podcast Network (@SecWeekly) reported 55 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

• 
  Vexoa (@Vexoa1) reported 55 minutes ago

  @garrytan Yeah at first i hated it. Then i kept seeing it improve people's workloads. I no longer have to swap and switch to github, fix, patch, continue. I simply, ship, build, it reviews, patches and i continue. I've tripled my workload. We appreciate the release Garry. You really cooked with this.

• 
  Southers (@SouthersDev) reported 55 minutes ago

  I built a bug reporting tool for Field of Command last week. Now I have a full QA team working 24/7 while I sleep! 🤯 How it works: 1.User fills out forms and clicks send inside the game. 2.Cloudflare worker dumps it into GitHub with full logs + screenshots. 3.Copilot triages and categorizes them automatically. 4.Claude picks up active issues when I open the project, maps out the context, and writes the plan. All I have to do is approve or decline the fix. This is how to solo dev with a 9-5 🤖✅

• 
  Tejas Giri (@tejasgiridev) reported 56 minutes ago

  @alexwtlf neither. build a thing you'd use every day for the next 6 months. if it happens to be a SaaS, cool. if it's a mobile app, cool. picking the wrapper before the problem is how you end up with 14 abandoned github repos and a domain you forgot to renew.

• 
  BrainMirror AI (@brainmirrorai) reported 56 minutes ago

  Private Publishing on Replit blocks unauthorized requests at the network level, not inside the app. The problem was always integrations: if you needed GitHub webhooks or Slack callbacks to reach your private app, your only option was to make the whole app public. External Access Tokens remove that tradeoff.