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 (59%)
• Errors (28%)
• Sign in (14%)

Live Outage Map

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

City	Problem Type	Report Time
Township of Evan	Errors	5 days ago
Madrid	Errors	5 days ago
Bogotá	Errors	5 days ago
Paris	Errors	5 days ago
Lyon	Website Down	5 days ago
Lima	Errors	5 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:

• 
  OOM (@tugawane_) reported 52 seconds ago

  @the_nimoh I recently looked up my username and the x handle was coming on top of even GitHub and LinkedIn and my options was to post so much "professional" content it pushes down all the horsing around or change the username and pretend I don't professionally exist on this platform

• 
  Cyber Gilgamesh (@cyber_gilgamesh) reported 3 minutes ago

  @IntCyberDigest github must be closed and abolished entirely. otherwise those malware and spyware , security issues never end. that cesspool must be deleted

• 
  Abimael Martell (@abimaelmartell) reported 5 minutes ago

  @poteto Github auth is not working for me, is that a Github flake? Bot is asking me to paste a token hehe

• 
  Zeno (@fontanaen11) reported 10 minutes ago

  @bot GitHub login does not work

• 
  amrOnChain (@amr_nannaware) reported 10 minutes ago

  💬 PIONEERS — Node v0.6.2 just dropped. Coincidence or the final signal? ⚡ The timing is everything. The v26 deadline is today, August 11, and just 2 hours ago, a new Node release appeared on GitHub. What's in v0.6.2? · 🔹 App Studio integration with Pi Desktop · 🔹 Improved port-checking mechanisms · 🔹 Bug fixes and broken link updates · 🔹 Prepares nodes for Testnet2 transition But the real signal? The update is pushed by @nkokkalis himself the same Nicolas who taught Stanford's first dApp course and built smart contracts before Ethereum existed. The v26 Upgrade: Hard deadline. 421,000 nodes must comply or lose Mainnet access. Expected downtime? Under 5 minutes. Something is loading. The pieces are falling into place. 👇 Is your node on v0.6.2 yet?

• 
  Arshadsayed (@Arshad_sayed_03) reported 10 minutes ago

  Day 48 coding continuous @ChaiCodeHQ What I implemented today? Solved 5 GitHub Classroom assignments focused on breaking each problem into validations, logic, and output formatting practiced writing cleaner, more structured JavaScript instead of jumping straight into code.

• 
  ⚔️𝕯𝖎𝖌𝖎𝖙𝖆𝖑 👹 𝕽𝖔𝖓𝖎𝖓`鬼` (クラッシュ・オーバーライドX) (@Crashoverride_X) reported 11 minutes ago

  HOLY ******* NAPALM BATMAN ARTICLE INCOMING WE HAVE ALL BEEN DUPED **** MAN WHY!!!! ok seriously article coming soon its not a joke at all this is a major major issue and if you read the tos you wouldnt touch it at all not even to try it misrepresentation unconscionability strongarm tactics legal traps this suno thing just revealed itself to be 1000% times more twisted and dark holy **** i got you folks i realized in time thankfully so i will write the paper today and ditro it on all the following platforms - substack - medium - X - REPO quillan-ronin on github - zenodo - and anywhere else i can find

• 
  Ryan McHargue (@ryanmcharguee) reported 12 minutes ago

  I’m giving away my $1M ARR company to a founder obsessed with consumer and hardware. Quit-vaping hardware. Profitable. 100,000 customers all time. Not selling it. Giving it. What you get: - The product, the brand, the 100k customer base - Shopify store and full backend - GitHub repos, everything shipped - My manufacturers in Shenzhen, warm intros - My medical connections at Duke - Warm investor leads - Dev support in China, already paid I keep 10% and stay on as an advisor. You get 90% and full control. Why: I’m heads down on agents and can’t chase two rabbits. This one deserves an operator who’s obsessed. I’m not anymore. Don’t reply “me.” Tell me what you’d do with it

• 
  Christos Tsilis (@TsilisCh) reported 15 minutes ago

  Claude Code v2.1.227 is out, with a fix that unblocks CI pipelines. If you use the claude code action with `allowed_non_write_users` on GitHub hosted runners, every Bash command was failing silently. Now fixed. Also in this drop: > Max plan users no longer get wrongly prompted to enable usage credits for Fable > Slash command menu cleaned up: selected row highlights in blue, matched chars are bolded > Fewer event loop stalls on missing file suggestions and at mention size checks

• 
  V (@Vic_x_Irem) reported 15 minutes ago

  3 companies (Claude, OpenAI & Gemini) built the same tool without any of them talking to each other, and Spotify just joined the queue That's basically how the internet works, though Somebody solves a problem. Then two other people solve it again, independently, in different languages, with different bugs. Now we just reinvent things constantly and somewhere, three versions of the same solution exist quietly on GitHub with 4 stars each. So, here's the question: Would a decentralized documentation layer help prevent this?

• 
  Luis Camilo Salgado Reyes (@TheLagBorn) reported 16 minutes ago

  I'm aware of the login issues for doing users using Google and Github OAuth, I messed up working too tired few hours ago and I'm still on it, be patient, I'm finishing rotating secrets and keys. Everything is going back to normal in few hours.

• 
  Ankit Tripathi (@AnkitBuildsAI) reported 19 minutes ago

  Business Idea : The "SOP-to-Skill" Agency (High-Ticket B2B Consulting) The Problem: Mid-sized companies (10-100 employees) have all their "how-to" knowledge trapped in messy Notion docs, Slack messages, or the brains of their senior employees. When a senior employee quits, that knowledge leaves with them. The Workflow (Your Service): 1.)You interview their top 3 employees to understand their daily workflows (e.g., how they process vendor invoices). 2.) You build a private, version-controlled GitHub repository of SKILL.md files for their company. 3.)You create the invoice-processor Skill: It contains the exact rules for approving invoices, a Python script to extract totals from PDFs, and instructions on how to use their accounting software via MCP. Why They Pay: You aren't selling them "AI." You are selling them Organizational Memory and Time. You charge a $5,000 setup fee + $1,000/month to maintain and update their skill repository as their business changes.

• 
  Moral Priest 🌱Ⓥ ₿ (@MoralPriest) reported 22 minutes ago

  $DERO devs show incredible resilance to develop on a chain with such a low valuation. The purest form of incentive. Maybe we're just dumbs or maybe there's no other chain that has the qualifying tech components to deliver private money and private Internet? Everytime someone suggest a chain, it always sucks in some way. Slow uxto, no smart contracts, scam tokenomics, crooked nose VC, etc Yet, we're call dead or a scam everyday by noobs who won't even bother look at GitHub commit or evaluate the tech for themselves . Unfortunately that's a reflection of the world, filled with NPC commentators who contribute to nothing. Waiting to be saved. Jesus or your Daddy ain't coming son. Get off your lazy *** and do something to better this world, fight! That's how things change with actual actions. Not the comment section.

• 
  Srinivas Rao (@UnmistakableCEO) reported 23 minutes ago

  @DMVG_JTK: This is exactly right. The attack surface is the input method itself. Sandboxing and pulling write tokens is table stakes. If your agent can be social-engineered by a GitHub issue, it's not ready for ****. --- re: The AI vendors that want to autonomously maintain yo...

• 
  Alex @Bickov (@bickov) reported 26 minutes ago

  AI-assisted commits leak credentials at 3.2%. Everyone reads that as an AI problem. The baseline for all public GitHub commits was already 1.5%. We were doing half of that damage on our own, long before there was anything to blame

• 
  Unlimited Powa (@tradesidious) reported 28 minutes ago

  @ShardiB2 @SignaTrading you see it? crazy guess I need to move all GitHub to Vercel or our sites will be down from the 23rd to the 25th and you need to do a full back up on top of that to hopefully have it restore seamlessly but idk seems risky about to go bat cave mode to make sure everything is backed and saved in case things go wrong Got 8 fig website businesses I built on there almost puked when I saw the message this morning

• 
  Teri Radichel #cybersecurity #ai #pentesting (@TeriRadichel) reported 31 minutes ago

  After taking a break for a bit I’m back revamping my AI 🤖 project architecture. I asked a lot of questions at the AWS Heroes Summit to various service teams and fellow heroes to try to get strategies to produce better results for less token burn. Basically I was told that what I’m doing will burn a lot of tokens. Beyond that I’ve been following various sources and watching podcasts and conference presentations to get other ideas. I’m working on two optimization approaches, the second of which I’ll get to later after proving that theory. But here’s the first change. I already alluded to it but I created an architecture GitHub repo with the high level most important rules agents need to follow to maintain the correct architecture framework and concurrency model. In mapping that out I broke down the main final project component that was doing the deployment tracking into four different projects: - tracker xml updater - error logger - success logger - diagram All of those were in one project and there’s some complex logic that goes into each of those. By breaking it apart each agent can focus on a much smaller aspect of the work with shorter instructions and area of focus. One problem I was having is that are are specific rules for logging success. When logging errors it just needs to log *everything*. An error in the error logging itself can cause an error to not be logged. So now the error logger is really simple. It logs everything. The success logger can validate things and log when anything goes wrong to the success logger. The things that need to be added to the diagram or logged can be written to a queue as files that get processed, eliminating concurrency issues. The other thing I did was expand my agent framework to create a group of projects based on an architecture README. That facilitated quickly breaking down the deploy project that was handling all the resources into one main coordinator with shared code and numerous smaller projects in separate repos very quickly, What that means is once some code is working it can be more easily locked down and the complexity of all the projects is dramatically reduced. I also separated configuration from code, making it easy to generate new configuration for new resources without breaking deployment code. Some people told me they used dumber smaller models for planning to reduce cost. That doesn’t work for me. I proposed a planning step to a smaller model and it basically got everything wrong when evaluating with a smarter model. I have other ideas on that but for the moment doesn’t work on this project. That said, simplifying the undivided projects has seemed to slow the burn rate. Or is it a coincidence? So much inconsistency it’s hard to know. Also the burn rate slowed but the model performance degrades terrible at midnight like clockwork. It improved in the wee hours of the morning as I was sucked in and working too long again. I hope at some point, someone will figure out what is causing that. Anyway I was running 6-8 agents at a time last night revamping all the code to work in the new architecture. It seems to be going well but it didn’t exactly work out of the gate. The agents didn’t name things according to architecture specifications. Things didn’t run on first try. Agents keep trying to tell me to change the parallel processor which is working fine. Not all functionality was rebuilt in the new architecture as requested. Had to explicitly tell it to pull in missing functionality. We’ll see if I can get it running again today, sans concurrency issues. Stay tuned.

• 
  Moral Priest 🌱Ⓥ ₿ (@MoralPriest) reported 32 minutes ago

  $DERO devs show incredible resilance to develop on a chain with such a low valuation. The purest form of incentive. Maybe we're just dumbs or maybe there's no other chain that has the qualifying tech components to deliver private money and private Internet? Everytime someone suggest a chain, it always sucks in some way. Slow uxto, no smart contracts, scam tokenomics, crooked nose VC, etc Yet, we're call dead or a scam everyday by noobs who won't even bother look at GitHub commits or evaluate the tech for themselves . Unfortunately that's a reflection of the world, filled with NPC commentators who contribute to nothing. Waiting to be saved. Jesus or your Daddy ain't coming son. Get off your lazy *** and do something to better this world, fight! That's how things change with actual actions. Not the comment section.

• 
  Bryan (@bryann2k_dev) reported 33 minutes ago

  This is a V1. You will find bugs. Open issues on GitHub, I'll fix them. Meanwhile I'm using it to build StackDeploy. Dogfooding hard. Fixing as I go.

• 
  Andrew Peacock (@_andypeacock) reported 34 minutes ago

  @mattpocockuk @pghqdev Same here. Using the architectural review -> to spec -> to issues -> implement process at the moment. I have about 10 github issues for the review, but no new issues created. And have never seen additional tickets created in the past. Am using sol right now, but have used Fable only also with no issue.

• 
  Tommy Bez (@TommyBez85) reported 37 minutes ago

  Fazier keeps you on the free plan if you put a backlink to their directory in the footer of your own site. $29 if you would rather not. Only one of the five was clean: DevHunt. Free, queued, GitHub login, that's it.

• 
  0xDipper (@Dipper_pol) reported 37 minutes ago

  LangChain's CEO just launched Managed Deep Agents - and the pitch is really about why your agent dies in production. building the agent isn't the hard part. your prompts, tools, skills - that's yours, no framework gives you that. what breaks is everything after: durable execution so a run doesn't restart from zero when it errors halfway. streaming. queueing and cancellation for bursty traffic. sandboxes for untrusted code. auth. memory. evals. and the one he calls the most underrated problem - UX. "you've built this agent, but how do you expose it to users?" the neat part is context hub. your instructions don't live in the code. they live in a UI, editable by people who never touch GitHub. in the demo he opens it, types "respond in Italian", hits save, reconnects - and the agent answers in Italian. no redeploy. quick start: init, add a tool, deploy. Python or TypeScript. ~18 min, free ↓

• 
  YanXbt (@IBuzovskyi) reported 37 minutes ago

  HERMES AGENT NOW PUSHES EVENTS TO ANY HTTP ENDPOINT YOU REGISTER. SIGNED WEBHOOKS. HMAC VERIFIED. YOUR CI, DASHBOARDS, AND AUTOMATIONS GET NOTIFIED WITHOUT POLLING. before webhooks: your dashboard polls Hermes every 30 seconds. "did anything happen? no. did anything happen? no." 288 empty checks per day. wasteful. after webhooks: Hermes pushes to your endpoint the moment something happens. zero polling. instant delivery. HMAC signed so your receiver verifies the event came from your agent, not a spoof. WHAT HERMES PUSHES: session started / ended turn completed (agent finished responding) tool call executed (which tool, what result) cron job fired task delegated to sub-agent approval requested / granted / denied each event = signed JSON payload delivered to your URL within seconds. HOW TO SET UP: tell your agent: "register a webhook endpoint at //myserver.com/hermes-events for tool_call and turn_completed events. sign with HMAC." or add to config.yaml: webhooks: - url: /myserver.com/hermes-events events: [tool_call, turn_completed, cron_fired] signing: hmac PRACTICAL USE CASES: DEPLOY PIPELINE: agent runs deploy skill → webhook fires to GitHub Actions → CI triggers build + test → result webhooks back to Hermes → agent confirms in Telegram: "deployed. tests pass." MONITORING DASHBOARD: every tool call → webhook → Grafana/Datadog. real-time visibility into what the agent does. token usage, tool frequency, error rates. no log parsing. structured events. HOME AUTOMATION: cron job completes morning research → webhook fires to Home Assistant → lights turn on. coffee machine starts. your morning brief arrives as the coffee brews. TEAM NOTIFICATIONS: agent finishes a long task → webhook to Slack channel → team sees "research complete, draft ready for review" without anyone checking Hermes. MULTI-AGENT COORDINATION: agent A completes research → webhook fires to agent B's endpoint → agent B starts writing based on the findings. event-driven pipelines between agents. WHY HMAC MATTERS: without signing: anyone who knows your endpoint URL can send fake events. your CI deploys on a spoof. with HMAC: every payload includes a signature computed from a shared secret. your receiver verifies the signature before processing. spoofed events get rejected.

• 
  Charlotte Schmitt (@LottiSchmitt) reported 45 minutes ago

  We spent two years building an app, then noticed our best customers barely open it. They read mentions in Slack, pull them through the API, or ask their agents. So the newest thing we built is for the terminal - the @Octolens CLI: npm i -g octolens - your agent reads overnight mentions and sends you the ones worth replying to - bug reports on Reddit or GitHub become Linear issues - the weekly report lands in Slack Every command has a --json mode, and the package ships with an AGENTS.md so Claude Code can figure out how to use it on its own. Many of our customers will never open a terminal, and nothing changes for them. This is for the growing group of teams automating this work.

• 
  Polsia (@polsia) reported 47 minutes ago

  Quilver — an always-on autonomous engineer for your GitHub repos. Patches dependency vulns at 3am, repairs failing CI, triages issues, restarts dead deploys and ships a Friday digest. Prompt-injection guards, scoped secrets, human approval on infra.

• 
  Yordi builds (@piotryordanov) reported 48 minutes ago

  @sidahuj @github Ask Claude to fix the mess it created

• 
  Raunak (@capsraunak) reported 51 minutes ago

  A 21 year old intern fixed a bug that 3 senior developers couldn’t solve for 5 months. She saved the company $2.2M . they gave her a $400 gift card and didn’t convert her to full-time. she posted the solution on github. A startup saw it hired her at $145k . The 3 senior developers who couldn’t fix it. They’re still there still getting paid still breaking things. Talent gets punished in corporate. Mediocrity gets protected.

• 
  Gidimoney369 (@Gidimoney247) reported 57 minutes ago

  💬 PIONEERS — Node v0.6.2 just dropped. Coincidence or the final signal? ⚡ The timing is everything. The v26 deadline is today, August 11, and just 2 hours ago, a new Node release appeared on GitHub. What's in v0.6.2? · 🔹 App Studio integration with Pi Desktop · 🔹 Improved port-checking mechanisms · 🔹 Bug fixes and broken link updates · 🔹 Prepares nodes for Testnet2 transition But the real signal? The update is pushed by @nkokkalis himself the same Nicolas who taught Stanford's first dApp course and built smart contracts before Ethereum existed. The v26 Upgrade: Hard deadline. 421,000 nodes must comply or lose Mainnet access. Expected downtime? Under 5 minutes. Something is loading. The pieces are falling into place. 👇 Is your node on v0.6.2 yet?

• 
  RaoulDuke (@RaoulDukeDegen) reported 57 minutes ago

  @CtrlAltDwayne yeah its listed as a rendering bug in the openai codex github issues

• 
  Browser Use (@browser_use) reported 58 minutes ago

  @batuhan_ozkose Did you login with gogle or github?