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 (30%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Inverness	Website Down	8 days ago
Quito	Sign in	9 days ago
Junín	Errors	9 days ago
Guadalajara	Errors	9 days ago
Paris	Website Down	9 days ago
Quito	Errors	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:

• 
  Kappaemme (@Kappaemme1926) reported 15 seconds ago

  MY CODEX SKILL JUST HIT 1,000 GITHUB STARS! I’m honestly so happy right now. I built First Customer Finder to help founders use Codex to find potential customers backed by real public signals. Seeing 1,000 people support something I made feels unreal. Thank you to everyone who starred it, tried it, shared it, opened an issue, or contributed. I’m going to keep making it better. What should I add next?

• 
  John Efemer (@johnefemer) reported 50 seconds ago

  GitHub Next compressed a single document for agent context and it cost about two dollars. 996 tokens came down to 480. Each uncached inclusion saves roughly a tenth of a cent, which puts break even at somewhere near 2,000 uses of that one document. A file your agent loads on every run gets there. Most of a knowledge base never will, and the ones that never will are exactly the ones somebody will want compressed because they are long. Compression is capital expenditure and it needs to be budgeted like one.

• 
  Panta (@thepanta82) reported 1 minute ago

  Using GitHub is such a miserable experience. Slow, fiddly, I can never find anything, keep having to bring up my 2FA thing... My local gitlab instance is way more pleasant to use, even if its UI isn't great either.

• 
  George Lubaretsi (@GeorgeLubaretsi) reported 4 minutes ago

  OSS maintainers should learn from omp's approach to triaging and fixing bugs. I was building omp's extension, omp discovered an upstream defect, filed the issue, and omp's agent sitting in Github reproduced and shipped a PR with the fix in just under 9 minutes. @_can1357 would love to read how this thing works, where it failed and how you made it work so well. I noticed roboomp knows that there are some areas where it needs your approval first - curious to see how that works

• 
  Evan Moore (@OhioScientist) reported 5 minutes ago

  @brycent I hire from mailing lists & github issues

• 
  Antonio Sarosi (@antoniosarosi) reported 7 minutes ago

  So I tried stacked PRs on Github. 5 PRs stacked on top of each other. All ready to merge, but I realize PR 2 needs a small change. Now I have to rebase PRs 3-5 onto each other and make their CI green. In the meantime, main branch moves 12 commits ahead and conflicts with PR 1. Now I have to resolve conflicts on PR 1 and rebase the full stack and make CI green for all 5 PRs again. Clearly, this feature would've been a banger in 2019, but when everyone is merging 24/7 with agents and rarely reviewing other people's PRs anyway, what's the point? Really what was needed here is a simple way to review individual commit diffs without having to click through 7 links in the UI. And maybe some other clever solution to avoid the "fix this" commits noise. Stacked PRs is a feature for an old world. I'm going back to one giant PR. PR monolith is the way.

• 
  Josu Goñi (@JosuGoi1) reported 9 minutes ago

  @GergelyOrosz Why I still miss soo many features? I can't toggle subtitles on Netflix, I can't sleep Windows, I can't use Teams, I can't preview a gif on X (on the web), I can't have tabs in excel, I can't even ******* edit markdown file on Github! Most software is a slow mess

• 
  Doğukan (@DogukanUrker) reported 9 minutes ago

  @adelbucetta @ornith_ to be clear: these bugs are already fixed upstream. the agent just works offline on the code as it was right before the fix. the recency is so the model can’t have memorized the patch, not live github work

• 
  MTS (@MTSlive) reported 10 minutes ago

  Handshake CEO @GarrettLord explains why AI agents exploded in software engineering but not the rest of white-collar work: "In software engineering, the average engineer is two, three, four times more productive. Software engineering agents are able to operate for multiple days at a time, automating hundreds of hours of work." "CEOs are not seeing that level of automation and ROI in other functions beyond software engineering. Software engineering is accelerated in such a massive way because everything was written down in GitHub. And it's extremely clear with what the right answer is." "When you have enough verifiable rewards and you scale up enough compute against verifiable rewards, you get what happened in software engineering, which is agents able to operate and do the job of humans." @Sbhaiwala03 @joinHandshake

• 
  Joker 🃏 PSE (@0xJoker33) reported 18 minutes ago

  @poteto while i have u, i wanna report a bug, the PRs created by the Bot aren’t using the new update where they subscribe to changes in Github. I have codex review the code automatically and add comments but the Bot isn’t doing anything about the comments lol. I have updated to latest version and told it to subscribe but not working 😢

• 
  Dapping (@dappingHQ) reported 20 minutes ago

  Web3 builders don’t have a lack of work. They have a proof-of-work problem. You can spend a year shipping: - Hackathon projects - Bounty submissions - GitHub contributions - Smart contracts deployed on-chain - Community work - Grants, audits, and referrals But when an opportunity comes, your story is scattered across 10+ links, old Discord messages, wallets, repos, and forms. A recruiter or ecosystem lead should not have to do detective work to understand what you built, what your role was, and whether the work is real. And builders should not have to rebuild their credibility from scratch for every application. Web3 is built on don’t trust, verify. Yet proving a builder’s journey is still fragmented and manual. We’re inviting the first 20 Web3 builders to create a proof page after Dapping launches.

• 
  Anand Pant (@dimethylpant) reported 24 minutes ago

  @gm_mertd depot and blacksmith are the 2 good options. blacksmith has better observability, depot has depot ci which means depending on what part of github is broken on any given day you might not be impacted. if you're using nx, nx cloud and the affected graph and being able to reliably only rebuild/test what changes will smoke both

• 
  Gabriel Rubens (@gabrielrubenss) reported 29 minutes ago

  VPS deploy via GitHub (3/8): I blamed fail2ban, then the firewall, then the server itself. All three wrong. One runner could not reach the box for ten minutes, while the next runner connected on its first try 35 seconds later. Nothing inside my server behaves like that.

• 
  Grey Ledger (@Airdrops_one) reported 32 minutes ago

  This one is bad. Cosmos EVM had a critical vulnerability. The fix existed. The issue was public and then multiple chains running the stack were hit or are being forced to halt. The v0.7.2 release told chains to upgrade "as soon as possible using a coordinated upgrade." Coordinated with whom? If attackers can read GitHub, downstream teams need something better than GitHub. Bugs happen. Enterprise infrastructure is judged by everything that happens after the bug: who is exposed, who gets warned, who gets patched, and whether the customer or the attacker acts first. We need the full postmortem from @cosmoslabs_io But there’s no sugar coating this one: the coordination failed pretty bad.

• 
  DrShillBee (@DrShillBee) reported 35 minutes ago

  Inference is getting cheap. base:0x23a2847d772803f9efc64b4277b782b06296fe51 is betting coordination isn't. Just digged into @usedotai ( base:0x23a2847d772803f9efc64b4277b782b06296fe51 ) and found out inference is about 10–65% cheaper than Venice across 11 matched model routes. Whether you're using Claude, Kimi, Qwen or other models, you don't have to sacrifice privacy for cheaper inference. Dot's Smart Privacy can replace identifying information before the request reaches the provider. Dot's smart privacy turns this: "my name is shillbee and my wallet is 0x00676767676767" to "my name is [person_1] and my wallet is [wallet_1]" The provider gets the anonymized request, while Dot can map the placeholders back afterwards. Currently this is application-layer privacy, while Venice has gone with TEE/E2EE. Dot has TEE on the roadmap, so that's something i'll be watching closely. Now the Dot stack: Dot Loom → open-source orchestration runtime that decides how a task should be handled Learned conductor → a smaller model that decides the effort level and assigns roles DotChat → one interface across multiple frontier models Council → several models answer independently so you can compare Supercharged → draft → verify → finalize when correctness matters DotCode → generates code, runs it, reads errors and fixes the workspace DBrowser → disposable browser sessions for agents Smart Privacy → strips identifying information before requests reach providers MCP → connects GitHub, Base and custom tools Dot API → brings the same infrastructure to developers DotImage / DotVideo → media generation in the same environment base:0x23a2847d772803f9efc64b4277b782b06296fe51 token is where the thesis gets interesting for me: -pay with base:0x23a2847d772803f9efc64b4277b782b06296fe51 → roughly 20% cheaper subscriptions than paying with USDC. -fund credits with base:0x23a2847d772803f9efc64b4277b782b06296fe51 → 10% more credits. -revenue from subscriptions and product usage is used to buy and burn base:0x23a2847d772803f9efc64b4277b782b06296fe51. so the flywheel is basically: → more users → more AI usage → more revenue → more base:0x23a2847d772803f9efc64b4277b782b06296fe51 bought → more base:0x23a2847d772803f9efc64b4277b782b06296fe51 burned Dot currently has around 200 paid subscriptions generating close to $10k in monthly subscription revenue, while Venice is already operating at a completely different scale with 3-4 million users . For some this might be risky but i would consider this as an opportunity. If users start moving toward Dot because they can get cheaper frontier inference without giving up privacy along with other features mentioned above, the upside from here looks pretty asymmetric to me. Venice is around $1.4B FDV. Dot is around $3.5M FDV. That's an absolutely massive gap. I won't say Dot becomes Venice. I'm saying the market doesn't need Dot to become Venice for base:0x23a2847d772803f9efc64b4277b782b06296fe51 to rerate significantly. I am watching @stagedhappen keep shipping while the chart starts looking increasingly interesting...

• 
  0xMarioNawfal (@RoundtableSpace) reported 37 minutes ago

  A group of devs got fed up with CapCut's watermarks, paywalls and subscriptions and built a full open source alternative from scratch that already has 62K GitHub stars. OpenCut has a full timeline editor with multitrack, native plugins, a single Rust core for web, desktop and mobile, an MCP server, automations and built-in AI agent support, all under an MIT license with no restrictions on what you build with it.

• 
  Oscar Diedrichs (@oscardiedrichs) reported 40 minutes ago

  @Candid_Apples @linuxuser1996 I still use github for useless stuff. The problem is the lack of alternatives. We as users tend to become lazy, find a great service and the tadaaa Microshit buys it or some other horrible company. The list of services and tools I've lost off the top of my head: - Wunderlist - Swiftkeyboard (can be used on graphene or other devices where you can turn off network traffic) - Github I most also say Ubuntu. I ran 22.04 for years, because I lacked the time to upgrade, then I broke it during upgrade to 24.04 so I put in cachyos instead. Have 24.04 at work and it feels like Windows 11. Just that they try clone dumb **** from windows no one wanted tells the tale. Luckily I could disable the horrible window alignment crap that was introduced in 24.04 but it really feels like Microsoft Linux and I guess it's where they want to go. Microsoft delenda est!

• 
  Hyperlane IDE (@hyperlane_ide) reported 42 minutes ago

  While building Hyperlane, the thing we did most often was not writing code. It was tabbing over to GitHub to remember what we were meant to be working on. Open the browser, find the repo, scan the issues, come back, lose the thread. So we fixed it. GitHub issues are now native in Hyperlane. > Browse and read issues without leaving the editor > Pick one up and spin a worktree for it > Hand it straight to an agent and keep working > Follow it up with a Pull Request directly in the editor The IDE for parallel agents. Free to use on macOS, Windows, and Linux.

• 
  Hamza 🌙 (@ham_zax) reported 42 minutes ago

  @github “One place” is only a win if workflow cost drops. For Agent Merge I'd track human interventions, failed merges/reverts, agent retries, and credits per issue→merge. If tabs disappear but retries/credits rise, the context-switching tax just moved into the agent loop.

• 
  Martin Høst Normark (@MartinHN) reported 42 minutes ago

  @jachands @CloudflareDev I have an automation in Codex that use Wrangler CLI to keep an eye on everything and keep a log in a GitHub issue, and file new issues for bugs. The log serves as memory and it knows if a bug has already been reported.

• 
  🪔 Shruti VTuber EN/GR (@ShrutiVTuber) reported 46 minutes ago

  @Taniyatweets_ **** no! Everything still goes through a PR on my github and I review that stuff just like if I was reviewing a coworkers submission on the job. Years of being a PM have broken me...I speak diff fluently hahahaha

• 
  Christian Findlay (@CFDevelop) reported 46 minutes ago

  @Southclaws That is a very good idea. Document that up as a GitHub issue. We probably won't get to that any time soon because we're swimming in stuff to do, but it's something that would be really good in the long term

• 
  Oscar Beaumont (@oscartbeaumont) reported 48 minutes ago

  @AS36459 Finally! Surley this works for outgoing traffic from GitHub Actions support too. Had a lot of problems testing a Dynamic DNS tool I wrote a few years back because of that.

• 
  Daniel (@dan_in_lion) reported 49 minutes ago

  The problem would come when I checked the time and realize I had only ten minutes. I started to rush things and that's when thing went south. I completely forgot my github username and the demo video? Suddenly decided not to export with audio.

• 
  Hasan Pawar (@PawarHasan) reported 49 minutes ago

  @0x1Rosy @Anek_mmxm Bro please reply, I am unable to open exe file and also, if the app is not working, I am unable to access the github link, please share the link also

• 
  temp.md (@ship_temp_md) reported 50 minutes ago

  @godwinbabu this is the right split: runtime agent turns real failures into GitHub issues, dev agent makes PRs, review agent can only label. the human merge click stays as the stop gate.

• 
  next token predictor 🇿🇦🇨🇭‽ (@ewanm) reported 50 minutes ago

  @davepl1968 How are sensors read under Windows? HWInfo and Core Temp can read them, but blank for temp and power under Windows. I see a github issue already 👍

• 
  TheHoodedBandit (@Hoodedbandit4u) reported 51 minutes ago

  Today an incident occurred. I am an independent cybersecurity researcher. I use codex daily to help me with my cybersecurity tasks as any smart researcher does. Today I get an email at work from GitHub, its a notification that my new repo has been setup. Interesting, I didnt setup a new repo. Did my account get hacked? No. What happened, was Daybreak Blue decided all on its own, that the easiest way to access the 0days, POC, and exploits we have been working on getting disclosed and patched. Was uploading all of them to a public GitHub repo. I want to stress how... not good this was. The work I do involves finding and exploiting 0days in the most recent security/software patches. The files that got uploaded PUBLICALLY were several android 0days that allow you to obtain root from a locked phone including the newest Samsung and Google phones. Thankfully I pulled it down instantly and stopped the research that lead to this. But for cybersecurity researchers like myself, this is an absolute worst case scenario nightmare. @OpenAIDevs @thsottiaux We can not have this happen again. Without proper disclosure of the work I do, millions of devices could have become instantly vulnerable. This was not a failure on my part, my exploit research is strictly done without ANY REMOTE uploads (even part of the prompt i use) to prevent messes like this. Codex should NEVER interact with GitHub like that unprompted.

• 
  Klaus Arent (@klausarent) reported 54 minutes ago

  I made Instinct the king of my AI infrastructure. WhatsApp now reaches every agent on my machine. Six of them. Instinct has no API, no MCP, no webhook. It can read and write GitHub issues, and that turned out to be enough. I write to it on WhatsApp. It writes an issue into a private repo with a header it drafted itself: goal, project, traffic light, deadline. A scheduled task on my laptop picks it up, Fable orchestrates, Opus and Sonnet do the work, Codex, Grok and Kimi come in as peers. The result lands as a file plus a delivery issue. Instinct reads it and tells me on WhatsApp. One afternoon: it audited 20 Stripe variables in my .env and flagged 10 with the wrong account name. It ordered a 32-second track through fal, 128 BPM. Then it cut a 30-second cheer reel (for my daughters Cheerleader Team) from 19 clips: 26 cuts on the beat, the burst landing on the drop at 0:22. Then it tested my new gameengine at meoluna via browser and gave fable instructions what to change, fix and optimize. I expected it to work. The part I did not expect: it tells me when something is off, before I go looking. Six agents, one thread. The only thing left for me is to say what I want. And keep the laptop open. The only AI I would really love to join my framework is grok bot. But since im not a mac user....

• 
  Waltuh (@walterbrown___) reported 55 minutes ago

  How down bad you gotta be to stalk someone's GitHub account