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 (67%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	4 days ago
Paris	Website Down	7 days ago
Saint-Paul	Website Down	8 days ago
Saint-Paul	Website Down	8 days ago
Mexico City	Sign in	9 days ago
León de los Aldama	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:

• 
  LOVE&PEACE (@SuddyNC) reported 2 minutes ago

  @chuckuddin I think u have to consider the fact that coding has been kinda open to the point where people were using other people's code from stackoverflow and open source github repos even before ai. if you're just looking for a solution to a problem in coding, ai does that part for you

• 
  Dr. Jose Silva 🪽🇧🇷 (@jseluisX) reported 3 minutes ago

  CyberTalks: 🤖📱Mobile OS The LineageOS is your ultimate playground if you want to rip out corporate bloatware and breathe new life into dying hardware. It is fully open-source, giving you total root potential and high customization. If you flash it clean without GApps, you completely cut the corporate tracking record. It is highly versatile and runs on almost any device you throw it at I prefer the GrapheneOS, which is a completely different beast built like a digital fortress. It is designed for maximum operational security and hardening against zero-day exploits. It locks down vulnerabilities by sandboxing every single app and disabling tracking networks at the baseline firmware level. It is the gold standard for high-risk targets, but the catch is you can only run it on Google Pixel hardware. If you want the GrapheneOS fortress, we are strictly targeting a Google Pixel (Pixel 6 or newer is ideal for long-term security patches). The hardware architecture of the Pixel allows GrapheneOS to re-lock the bootloader with custom keys, keeping the device secure.If you are targeting LineageOS, the hardware choice is much wider. A Motorola or a global Xiaomi device works perfectly because their bootloaders are easy to unlock, and they have massive developer community support on GitHub. So, picture this. You just spent the last hour flashing this clean, beautiful new operating system. You boot it up, everything feels fast, and you feel like a tech god. Then, you open your banking app to check your balance, and boom. Red screen of death. The app crashes or hits you with a "Security Violation: Device Modified" error. Here is exactly what is happening under the hood. The bank is running a silent check using Google's Play Integrity API. Think of it like a digital bouncer checking IDs. It looks at your phone and instantly spots that your bootloader is wide open and the factory operating system is gone. It flags you as a security risk and locks you out.But don't panic, we can outsmart the bouncer.If you chose the LineageOS route, we fight fire with fire using root access. First, you flash Magisk, which gives you administrative control over the entire system. Once Magisk is running, you download an open-source tool called Play Integrity Fix. This genius little module feeds the bouncer a fake, certified device fingerprint from an old, official phone. Finally, you flip on Magisk's DenyList feature to completely blind your banking app to the fact that the phone is even rooted. To the bank, you look like a standard, boring retail device. Now, if you went with GrapheneOS, the game is totally different because we do not use root at all. Rooting actually creates security holes, and Graphene hates that. Instead, you use their built-in Sandboxed Google Play Services. This tricks the banking app by letting Google's security code run, but it traps it inside a restricted digital cage. The app gets the official security handshake it wants, but it has zero permission to spy on the rest of your hardened OS. Most global banks just work out of the box this way. To bypass banking app security on a custom ROM, you must trick the Google Play Integrity API into thinking your device is locked and official. Banks use this API to check if your bootloader is unlocked or if the system is modified.On LineageOS, you achieve this by flashing Magisk to gain root access. Once rooted, you install an open-source module called Play Integrity Fix, which spoofs a certified device fingerprint. You then use Magisk's DenyList feature to hide the root status directly from your banking apps. On GrapheneOS, the approach is completely different because the system does not use root access. GrapheneOS includes a built-in feature called Sandboxed Google Play Services. This allows the official Google code to run inside a restricted sandbox without system privileges, which successfully passes basic Integrity checks for most global banking apps right out of the box. Happy Coding!

• 
  BRute Logic (@BRuteLogic) reported 4 minutes ago

  Even CISA, the agency responsible for US cybersecurity, fell for it. A contractor left AWS GovCloud admin keys in a public GitHub repo named "importantAWStokens" for six months. Nine automated alerts ignored. Keys stayed valid 48 hours after the repo was taken down. hack2earn

• 
  BullBear.News (@bullbear_info) reported 8 minutes ago

  @vercel_dev @github @code Wake me up when these 30 platform skills can debug a broken Vercel edge function deployment at 2 AM without hallucinating the config schema.

• 
  A. Taha (@Purple_Pear_577) reported 10 minutes ago

  The new FlawCue will be a pre-launch code review for AI-built web apps. Connect a GitHub repo, then choose: • Security • Structure • One critical flow You get prioritized issues, exact code evidence, and fix prompts for your coding agent.

• 
  Grey G. 🇦🇶 (@gr3yg00) reported 11 minutes ago

  @cpt_mayhem Yes, but not yet. I'm planning to put the 3D files and instructions on how to build on github once it's completely done. Basically it's a 24V power supply I took from a broken 3D printer in the base and power converters that drive two stacked peltier elements of 90W on a CPU fan

• 
  Chris W (@Chris_Wozniczek) reported 11 minutes ago

  @simonsequedac i have a waitlist, that i wanted to deploy but ....github has an issue... so it ducked my plan, will do that tomorrow

• 
  Rahul kumar (@ats1999_er) reported 12 minutes ago

  @GithubProjects I can't, because GitHub is down.

• 
  Remco (@remcoros) reported 12 minutes ago

  @DavidFBailey @pastorcoin On my testnet 4 faucet (protected with X/github/discord login, min. 3 months account age, only 1 withdraw per account), I had a few very huge spikes. As if they used a bunch of fake accounts to get some testnet btc. Like why?!? It's worthless anyway :D

• 
  Lance (@LKRBuilds) reported 18 minutes ago

  @didier_lopes @github This is stupid. There is a huge problem with fake stars being used to make malicious repositories look legitimate on github and now there's no way to detect it. It was easy when you could just click on the star button and start looking through the accounts that starred the repo and realize most of the accounts are fake

• 
  Yasir Ai (@AiwithYasir) reported 18 minutes ago

  🚨 $276 A YEAR ADOBE'S SUBSCRIPTION IS DEAD: MEET PHOTO GIMP, THE FREE KILLER! A Brazilian YouTuber has just delivered a decisive blow to Adobe’s Photoshop subscription model. It is called PhotoGIMP: a free, open-source patch (GPL-3.0) that transforms GIMP into an almost identical copy of Photoshop. Same interface, same panels, same keyboard shortcuts, and significantly more canvas space. Your hands already know exactly how to use it — no new learning curve required. Why is it going viral? > $0 instead of $276 per year > No Adobe account or login required > Everything saved locally on your PC (nothing in the cloud) > Fully compatible with Windows, macOS, and Linux > Complete uninstall by simply deleting one folder (no traces left behind) Installation is ridiculously simple: copy nine files and you’re done. It already has over 8.8k stars on GitHub and community translations. 100% free for both personal and commercial use. (Link in comments)

• 
  chronark (@chronark) reported 26 minutes ago

  @dominikkoch @jacobmparis @vercel This is GitHub We have built the same widget and GitHub’s api is really slow even if it’s working

• 
  user (@user1508123) reported 30 minutes ago

  Github API down, AGAIN. Are they serious?

• 
  Dan (@aidaniil) reported 33 minutes ago

  another github outage time for someone to build a better one

• 
  Andrew Bills (@EvilSpyBoy) reported 36 minutes ago

  @julesagent hey soooo.... is the Jules web agent connect to github functionality down because I was having a very productive week until just now with Jules and it no longer wants to connect to github so it can no longer find my repos (that it was and has been working with)

• 
  Sahaj (@iamsahaj_xyz) reported 37 minutes ago

  @gauravmandall @github fyi you can submit a support ticket. there's a "can't sign in" button on the login page but it's not obvious

• 
  Joey Chang (@iwhaleocean) reported 40 minutes ago

  Another failure: the first plausible root cause won. For a GitHub OAuth 400, one path blamed the proxy; later evidence pointed to Supabase configuration. Now separate agents test code, config, upstream, and environment hypotheses before anyone proposes a fix.

• 
  Harley Lewis Foote (@harleyfoote_) reported 41 minutes ago

  @ptdbugs @sasi2103 @NomaSecurity For issue-driven agents, the token should be repo-local from the trigger; the issue body can steer triage, not expand the GitHub graph.

• 
  Parth Patel (@parthmern) reported 44 minutes ago

  @Hiteshdotcom @subhra8640 yeh 100% agree but i did the same went to temp mail made new github ac and did login with it kind of same thing but agree that it can help with multiple dummy logins btw: new CN course on youtube is good one, i always watch while going to work on subway

• 
  Parth Sinha (@parth_sinha18) reported 45 minutes ago

  GitHub API is down @github My deployment it stalled. AAAAAAaaaaaaaaaaaaa...!!!

• 
  HalxDocs (@HalxDocs) reported 45 minutes ago

  Reqit crossed 300 downloads this week. No ads, no VC, no launch hype just people who wanted an API client that doesn't need a login. We also just shipped v1.0.1 — the biggest hardening release yet. Here's what changed: Security & stability • AI API keys now stored in your OS keychain (never plaintext on disk) • Script execution gets a 10s timeout (no more runaway Goja VMs) • Request body reads capped at 10MB • Collection runner cancellation actually works now 40+ error handling fixes across the Go backend Silent failures in GraphQL, registry, MQTT, mock recording, interceptor — all caught and surfaced now. If something breaks, you'll know about it instead of getting a mysterious empty response. Frontend improvements • Focus trap on all modals (Tab/Shift+Tab cycles properly) • Escape key closes every open modal • Confirm dialogs on destructive actions (delete collection, clear history, etc.) • Error boundary wraps the entire app The updater just works v1.0.1 auto-updates from the dashboard. Build binaries → upload to GitHub release with latest.json → users get the update. No manual downloads needed. 📦 Full changelog: ✓ 300 downloads milestone banner ✓ OS keychain for AI keys ✓ 40+ Go error handling fixes ✓ Modal focus traps ✓ Collection runner cancellation ✓ Script timeout safety ✓ Frontend error boundary Link in the CS What feature do you want next? 👇

• 
  Gustavo Alessandri (@webgus) reported 45 minutes ago

  If you find an error, have an idea, or want to propose an improvement, just open an issue or fork it on Codeberg or GitHub. Contributions are welcome. That’s exactly the point.

• 
  RyDawgE @ Halfapps (@RyDawgE_) reported 46 minutes ago

  @gregceltiano Training was done by already public repos.. and is now done with people who agree to the terms and services of said hosting platforms. There will be a github migration soon. Ive already begun moving my private repos to my own *** server. I have faith people are smarter than this.

• 
  Parthajeet Sarmah (@pthsarmah) reported 49 minutes ago

  So I am onward to create a portfolio website in 14KB! I am not the most experienced in this so feel free to correct me or suggest alternatives. For the first step, I tried to recreate the github contribution graph as an SVG directly injected to the HTML. My train of thought is that as long as I can generate static assets or markup in a regular interval in the server and just inject the markup to my index.html, I might be able to keep the size down after compression. Lmk if you know of any better way to do this (P.S: The github graph is not from my actual github, it's just random colors, api calls shouldn't affect anyway since the js would never be sent over network)

• 
  Parthajeet Sarmah (@pthsarmah) reported 50 minutes ago

  So I am onward to create a portfolio website in 14KB! I am not the most experienced in this so feel free to correct me or suggest alternatives. For the first step, I tried to recreate the github contribution graph as an SVG directly injected to the HTML. My train of thought is that as long as I can generate static assets or markup in a regular interval in the server and just inject the markup to my index.html, I might be able to keep the size down after compression. Lmk if you know of any better way to do this

• 
  Stew1000 (Ø,G) 👾🛡️ (@Stew_SoFresh) reported 51 minutes ago

  @catebligh @OpenAI @sama No problem, yeah it can be frustrating at times it’s hard getting a certain output your looking for. Have you tried GitHub copilot can use that as a direct line to the code and attach the repo your working under and it generates the code or suggested prompt setup by the model it helps with prompt accuracy and context for the model

• 
  Crypto_statistics (@StatsChain) reported 51 minutes ago

  @HackQuest_ Hi, I received an error message for my submitted project. I have made the edits in github. Do i have to resubmit it?

• 
  Ali Çevik (@alihcevik) reported 53 minutes ago

  We are rapidly improving managed agents. With these updates you can now: 1. Try it for free 2. Set budget guard rails to stay in control of costs 3. Have it run on schedule on the background; so you can automate things like monitoring GitHub issues, reproducing them, sending you notifications for anything worth your attention.

• 
  Jérémie Dumont (@NoLife141) reported 56 minutes ago

  @technologytard @thsottiaux Yeah, I'm already doing that. I have GitHub on my other screen and just ask Codex to fetch the issue ID and do the task. It's just a convenience to have it in the app.

• 
  Tumusiime Alaphati (@alaphati_t) reported 59 minutes ago

  "Your GitHub contribution graph doesn't measure your impact. The problems you solve do."