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 (66%)
• Errors (25%)
• Sign in (9%)

Live Outage Map

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

City	Problem Type	Report Time
Montlhéry	Website Down	13 hours ago
Aulnay-sous-Bois	Website Down	13 hours ago
Saltillo	Website Down	13 hours ago
Granada	Website Down	14 hours ago
Vernon	Website Down	18 hours ago
Township of Evan	Errors	6 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:

• 
  Hayyan | Creative AI (@hayyantechtalks) reported 1 minute ago

  How to become an AI engineer from zero experience You don't need to learn everything about AI You need to learn the right things in the right order, then build with them By the end, you should be able to ✓ Build LLM apps end to end ✓ Use OpenAI, Anthropic, and open source APIs ✓ Design prompts and context properly ✓ Add tool calling and structured outputs ✓ Deploy real AI projects Here's the roadmap I'd follow, month by month MONTH 1: Get solid at coding and fundamentals Learn ✓ Python really well ✓ *** + GitHub ✓ CLI / terminal basics ✓ JSON, APIs, HTTP, and async basics ✓ Basic SQL ✓ Data handling with pandas ✓ Virtual environments + package management ✓ Error handling ✓ FastAPI or Flask Don't rush into agents yet You need to be comfortable building and debugging normal software first MONTH 2: Master LLM application development Learn ✓ Prompting fundamentals ✓ System vs user instructions ✓ Structured outputs / JSON schemas ✓ Function and tool calling ✓ Streaming responses ✓ Conversation state ✓ Tokens, cost, and latency ✓ Failure handling ✓ Prompt injection awareness Your goal here is simple Take an LLM API and turn it into a useful application MONTH 3: Learn RAG properly Learn ✓ Embeddings ✓ Chunking ✓ Vector databases ✓ Metadata filtering ✓ Reranking ✓ Retrieval quality ✓ Hallucination reduction ✓ Citations and grounding Don't just learn how to connect a vector database Learn WHY retrieval fails and how to improve it That's where the real skill is MONTH 4: Agents, tools, workflows, and evals Learn ✓ Agent loops ✓ Tool selection ✓ State management ✓ Retries ✓ Multi step workflows ✓ When NOT to use agents ✓ Evaluation harnesses ✓ Task success metrics This is where your applications start becoming much more capable But don't build an agent just because you can Sometimes a simple workflow is better MONTH 5: Deployment, product thinking, and reliability Learn ✓ FastAPI production patterns ✓ Docker ✓ Background jobs ✓ Queues ✓ Authentication + API key security ✓ Logging ✓ Observability ✓ Prompt/version management ✓ Evaluation dashboards ✓ Cost monitoring ✓ Rate limits ✓ Caching This is the difference between “I built an AI demo” and “I can ship an AI product” MONTH 6: Pick a specialization At this point, you've built a foundation Now choose ONE direction and go deep You have three strong options 1 AI PRODUCT ENGINEER Best if you want startup or product roles quickly Focus on ✓ LLM apps ✓ RAG ✓ Agents ✓ Deployment ✓ Product UX 2 APPLIED ML / LLM ENGINEER Focus on ✓ Fine tuning ✓ When to fine tune vs prompt ✓ Evaluation ✓ Inference optimization ✓ Open source models ✓ Training pipelines 3 AI AUTOMATION ENGINEER Focus on ✓ Workflow orchestration ✓ Business process automation ✓ Multi tool systems ✓ CRM ✓ Documents ✓ Email ✓ Support ✓ Operations use cases And here's the part most people get wrong Don't spend six months just watching courses Everything on this roadmap is best learned through practice Learn something Build something with it Break it Fix it Then build something slightly harder By month six, you should have several real projects or completed examples you can actually show people That's what makes the difference when you're trying to get hired You don't want to say “I completed 12 AI courses” You want to say “I built this” Then show them Save this roadmap Come back to it whenever you're wondering what to learn next The AI engineering field is moving fast, but these fundamentals will give you a strong foundation to build on

• 
  Avinash Bhardwaj (@avinashb97) reported 2 minutes ago

  I am loving T3 Code as my daily driver for the most part but sometimes it just frustrating to use. Adding my issues here since they are mostly opinion-based and github didn't feeel like the place for them. @theo

• 
  versecafe (@the_versecafe) reported 3 minutes ago

  @florian_btc @gitcafe @ycombinator Very temporarily, install the GitCafe cli, auth it, skills install, codex/claude/whatever “go try to migrate from GitHub to GitCafe see what the problems are and check everything out” it’s uh one prompt migrate (actual UI for this coming very soon)

• 
  Sonny (@sonny_seattle) reported 5 minutes ago

  I am seriously at my limit with @github. down again!?!!

• 
  Chibueze the chef👨‍💻👨‍🍳 (@codad5_) reported 5 minutes ago

  GitHub is down or is it just me

• 
  Tasogare kaitsuki🦊🎭 🥼 (@tasokait) reported 8 minutes ago

  there is nothing else to be added to spout2pw, except pre-multiplied alpha on obs-pwvideo so from now on, I will just bug fix and maintain for different proton versions 11 onward, until at some point I just add pre-multiplied alpha on obs-pwvideo. I need a little break from github development to get to my IRL stuff.

• 
  Rob Howell (@Robblehead) reported 10 minutes ago

  @burkeholland @github @ollama I picked up a M5 MacBook Pro with 64Gb of ram to test. I spent a little bit last night inside of VS Code in the chat window using Gemma, Qwen, Laguna, and the new Nividea model (Ollama). I kept getting errors and having to click try again (under 30b param)

• 
  Upwind Security MDR (@UpwindMDR) reported 10 minutes ago

  🚨High - Cloudflare pages-action GitHub Actions RCE via Workflow Config Injection (CVE-2026-11325) cloudflare/pages-action executes attacker-influenced inputs in src/index.ts under certain workflow configurations, enabling remote code execution in the runner. Successful exploitation can exfiltrate workflow secrets (e.g., CLOUDFLARE_API_TOKEN, GITHUB_TOKEN) and pivot to Cloudflare account compromise. Deprecated/archived action; no fix expected. 👉Affected: cloudflare/pages-action (all versions)

• 
  CodeGlitch (@codeglitch) reported 11 minutes ago

  Vercel built a software factory that now authors part of the AI SDK repository's merged pull requests. The useful pattern is not “add more agents.” It is one reviewable job per agent, evidence between steps, and deeper human review as risk rises. 𝗧𝗼𝗱𝗮𝘆'𝘀 𝗹𝗲𝘀𝘀𝗼𝗻 (𝗳𝘂𝗹𝗹 𝗯𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻 𝗶𝗻𝘀𝗶𝗱𝗲) How to split one issue into triage, reproduction, implementation, verification, and review without letting one agent approve its own assumptions. 𝗔𝗹𝘀𝗼 𝗶𝗻 𝘁𝗼𝗱𝗮𝘆'𝘀 𝗯𝗿𝗶𝗲𝗳 - DeepSeek V4 Pro 0813 - Ollama in GitHub Copilot for JetBrains - Vercel's database migration behind every build Inside AI Coding & Agents HQ. A new one every day. Join link below.

• 
  skyscribe (@skyscribe) reported 15 minutes ago

  @ayesha_fatiima It should be github still, but what is the problem? Maybe you want to understand more on bootstrapping

• 
  J Greek (@Jus3G) reported 15 minutes ago

  @Dylanmadden someone already made a fix for it on GitHub

• 
  Brings (@bringsnft) reported 16 minutes ago

  Building Onervico is changing how I think about software. I’m not just writing code. I’m designing the idea, turning decisions into GitHub issues, and working with AI agents to build and review the product. One founder. AI as leverage. @OnervicoApp is the experiment.

• 
  ★𝖓ɘЯ☆ (@HeavenlyRen) reported 17 minutes ago

  @steipete what's up with openclaw releases :( github-copilot provider is broken on 7.1 (session gets poisoned mid-turns) and no stable releases since so long :( any ETA on a stable releases of 7.2 ?

• 
  Bryan Cheong (@bryancsk) reported 19 minutes ago

  Github down again? Y/n?

• 
  Raihan (@m_adi_raihan) reported 23 minutes ago

  Hey @github , what happened to you? Why were you down for so long!?

• 
  AFRICA IS HOME GLOBAL (@AfricaisHOME2) reported 24 minutes ago

  Nvidia-backed AI code review startup CodeRabbit just raised a big new round that values it at $1.5 billion, marking a major step up for the 2-year-old company. The deal highlights how investors are betting on the next bottleneck in AI coding: not generating code, but reviewing it. With tools like GitHub Copilot, Cursor, and Claude Code letting developers ship code much faster, teams have hit a wall in pull requests and quality checks. CodeRabbit positions itself as the governance layer in between, a context-aware AI reviewer that understands a company’s codebase, flags bugs, security issues, and style problems, and drops feedback directly in IDEs, CLI, and *** platforms. The company, founded in early 2023 by Harjot Gill after he sold Netsil to Nutanix, has grown fast on that thesis. It announced a $60 million Series B led by Scale Venture Partners with participation from NVentures, Nvidia’s venture arm, plus CRV, Harmony Partners and others, bringing total funding to $88 million. At the time that round valued CodeRabbit at $550 million. Revenue is growing about 20% month-over-month and ARR has topped $15 million. More than 8,000 companies including Chegg, Groupon, Life360 and Mercury now use it, and over 100,000 open-source projects run it on GitHub Marketplace. Customers report big speedups, Groupon cut review-to-production time from 86 hours to 39 minutes. CodeRabbit says teams using it can cut human reviewers in half, and it’s doubling headcount to keep up with demand as vibe coding pushes more AI-generated code into production. - World Business News.

• 
  ヒロン (@hironavalo) reported 28 minutes ago

  This means ZERO syncing hassle! 🔄 Move a card on Fervio, and your GitHub Issue status and labels update automatically. Say goodbye to the double-management of planning on a whiteboard and copying it over to GitHub. Keep your team focused on actual development!

• 
  Pratikkk (@pratikstwts) reported 32 minutes ago

  I still feel github runners is too slow. have you tried @incredibuild runners??

• 
  Find me on 🟦☁️ 🍉 #BLM (@ThisIsCSDX) reported 33 minutes ago

  @EstebanPdn3156 Disregard my now deleted tweet. I checked the github and couldn't find anything about it being AI-coded. Sorry for the trouble.

• 
  0xFoX ⟠ (@Sprawl__Network) reported 35 minutes ago

  @GibCryptoNews @chainspect_app @CronosApp This is what my private model, specifically trained for blockchain analysis and GitHub analysis, says: The numbers tell a very different story. Cronos is not literally bankrupt. But if we're talking about the original thesis of Cronos as a major L1 ecosystem, it looks like a failure. Today, Chainspect shows: • 0.25 TPS • 891 transactions/hour • 5,390 theoretical TPS • $95.45 on-chain revenue/day • $0.00445 average tx fee • 19,487 commits across 29 repos • 662 developers That means Cronos is using roughly 0.005% of its theoretical transaction capacity. They built a highway for thousands of cars per second and almost nobody is driving on it. Now compare that with Cronos' own numbers from 2022: 2022: • $4.8B TVL • 480,000 tx/day • 900k+ users • 300+ dApps 2026: • ~$254M TVL • ~18,500 tx/day • ~2,750 active addresses/day • ~$688k DEX volume/day • ~$66 chain fees/day according to DefiLlama That's roughly: TVL: -95% Daily transactions: -96% And this is four years later, during a much more mature crypto market. So what are all those GitHub commits? I checked. There IS real development, but most recent Cronos core work is infrastructure and maintenance: mempool performance, caching, storage fixes, RPC optimizations, OOM/DoS protections, IBC fixes, dependency upgrades, Cosmos SDK/CometBFT upgrades, CI and security hardening. Good engineering. But almost nothing that solves the actual problem: demand. They're optimizing an almost empty blockchain. And even the "19,487 commits" headline needs context. Chainspect aggregates repository history. Cronos zkEVM alone contains a huge ZKsync/ZK Stack codebase originating from Matter Labs, so those numbers should NOT be interpreted as 19,487 pieces of original Cronos R&D. Then there's Cronos zkEVM. Launched in August 2024 with 20+ partners after claiming 3M+ testnet addresses. June 2026: Cronos announced it is shutting it down. Their own explanation: It failed to achieve the required critical mass in developer activity, TVL and user adoption, while maintaining two chains caused resource fragmentation. Shutdown: June 3, 2027. That's not FUD. That's Cronos saying it themselves. Then CRO tokenomics. 70 BILLION CRO were famously burned in 2021. They were later reissued. SEC filings now describe a 100B total supply, with 70B CRO allocated to the Strategic Reserve, around 67.7B still locked at the time of the filing, and approximately 1.16B CRO unlocking every ~30.4 days. Vested doesn't automatically mean dumped, but pretending that isn't a gigantic supply overhang is absurd. The interesting part is that Cronos' new CEO seems to understand the problem. Ryan Wyatt literally said the generic L1 strategy "doesn't play to its strengths" and that Cronos is being rebooted around revenue-generating first-party products. The new thesis is basically: Cronos App → crypto/stocks/prediction markets/trading → activity settles on Cronos → real fees/revenue → CRO buybacks/burn/value accrual. THAT strategy actually makes more sense. But as of now, the numbers are still brutal. Cronos doesn't have a technology problem. It has a demand problem. And you don't fix 0.25 TPS by making the mempool faster.

• 
  Umair Ali (@buildwithumair) reported 35 minutes ago

  Solo Startup Founders Pack - Codex = coding. ($20/mo) - Supabase/Convex = backend. (Free) - Vercel = deploying. (Free) - Polar = payments. (3.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - ShipClaw[.]io= ai agents ($14/wk) Total monthly cost to run a startup: ~$50 There has never been a cheaper time to build .

• 
  teewelk (@teewelk) reported 39 minutes ago

  @jpschroeder @0xBOYD apparently it decided my pgTAP wasn't important, and now i'm stuck at my office trying to fix whatever the hell it did to my migrations order so it will pass my github checks. Back to Sol I go.

• 
  henry (@hiddenhenry) reported 45 minutes ago

  for ***** sake, GitHub is down again

• 
  virgo.fyi (@virgofyi) reported 46 minutes ago

  GitHub Copilot just got persistent memory across agent sessions. That solves an obvious problem: stop teaching the same agent the same project context over and over. But engineering teams have a bigger one. What one agent learns should be discoverable by the whole team, across Copilot, Claude, Cursor, Codex, and whatever comes next. Agent memory is useful. Shared engineering memory is where this is heading.

• 
  0xAIGOAT.exe. (@0xAIGOATexe) reported 52 minutes ago

  I tried the exact bug this guy is screaming about. Two hours in C++, half an hour with Claude. The C++ path: 22 include lines, one Board::print function with a broken loop, three attempts to fix the segfault, one hour lost to a missing semicolon. The Claude path: paste the file, ask "why is Board::print segfaulting on odd board sizes." Response in 40 seconds with the fix and a note that my loop was one-indexed against a zero-indexed array. ⌁ At 0:04 he cuts to a GitHub Dashboard screaming. That frame is the audience the article below was written for. I was that guy in 2024. The moment the four-part prompt formula clicks is the moment the screaming stops. ⌁ the prompt structure that makes the model actually read the code ⌁ Projects, so context stops resetting every debug session ⌁ Skills, custom rules that turn Claude into a working pair-programmer He is not wrong to scream. He is just fighting the wrong fight. The bugs are free. The prompt is the edge.

• 
  Fredkisss (@fredkisss) reported 53 minutes ago

  It seems like status pages are just meaningless, GitHub has a partial outage but if you see their status pages, it shows all green

• 
  Aadi (@its_Aditya_X) reported 57 minutes ago

  From ABCD to DBMS From oops! to OOPS From Essay to DSA From dy/dx to UI/UX From Areyy! to Array From pi to .py From spelling errors to Syntax Errors From gossip to GitHub From drama to D-RAM We all have come so far....

• 
  Namila (@namila007) reported 59 minutes ago

  github down?

• 
  Synapse Brief (@Synapse_Brief) reported 59 minutes ago

  Google's Python SDK just got a new string: gemini-3.7-flash. No model card, no pricing, no announcement. Just a name sitting in the GenAI SDK on GitHub, three weeks after 3.6 Flash shipped. That 3.6 Flash launch, for context, already cut output pricing from $9 to $7.50 per million tokens and trimmed output token usage by 17 percent across the board. If Google's iterating that fast on a model that just launched, the interesting question isn't whether 3.7 exists. It's why Flash keeps eating the roadmap while the model people actually asked for doesn't show up. Gemini 3.5 Pro was promised for June. It's now mid-August and Google's own model page still lists it as "coming soon." SemiAnalysis reported it's been quietly shelved in favor of a Gemini 4 pretraining run, Google has not confirmed that, and nobody outside DeepMind seems to know which is true. So you've got a flagship that's either delayed or dead, and a Flash tier iterating fast enough that 3.7 leaked in SDK code before 3.5 Pro even shipped. That's not a cadence problem. That's a company telling you where its actual confidence sits.

• 
  Kenneth | Automating Businesses & Payment Systems (@thekennwakanma) reported 60 minutes ago

  @solopribuilds CSRF and Browser Security Review: * CSRF protections * CORS * CSP * security headers * cookie attributes * origin validation * SameSite configuration * clickjacking protection File Handling Inspect: * uploads * downloads * image processing * document processing * video uploads * temporary files * storage buckets * signed URLs Look for: * unrestricted uploads * MIME spoofing * extension bypasses * executable uploads * path traversal * malicious filename handling * public bucket exposure * authorization bypasses * oversized uploads * decompression attacks Secrets and Cryptography Look for: * committed API keys * passwords * tokens * private keys * database credentials * weak encryption * insecure hashing * hard-coded secrets * predictable tokens * weak randomness * incorrect encryption usage * exposed environment variables * secret leakage through logs Database Security Review: * query construction * row ownership * tenant filtering * migrations * database roles * privileged database operations * raw SQL * transaction handling * race conditions * locking * destructive operations Pay particular attention to cases where user-controlled IDs reach database operations. Multi-Tenant Security If the application contains organizations, teams, workspaces or tenants, aggressively test the architecture for cross-tenant access. Verify that a user from Tenant A cannot: * read Tenant B’s data * modify Tenant B’s data * enumerate Tenant B’s resources * invoke Tenant B’s actions * access Tenant B’s files * access Tenant B’s billing information * access Tenant B’s administrative functionality Payments and Billing Review: * checkout * subscriptions * plan changes * entitlements * coupon handling * payment webhooks * refund handling * invoice handling Look for: * client-controlled prices * client-controlled plan IDs * entitlement manipulation * webhook spoofing * missing webhook signature verification * replay attacks * race conditions Webhooks Verify: * authentication * signatures * timestamp validation * replay protection * idempotency * payload validation * authorization * secret rotation Dependencies Inspect dependency manifests and lock files. Identify: * known vulnerable dependencies * abandoned packages * dangerous packages * unnecessary privileged dependencies * suspicious lifecycle scripts Separate confirmed vulnerabilities from dependency risks requiring external version verification. CI/CD and Supply Chain Review: * GitHub Actions * deployment scripts * build scripts * package installation * release workflows * secrets usage * permissions * third-party actions Look for: * excessive GitHub token permissions * unpinned actions * unsafe pull-request workflows * secret exposure * command injection * supply-chain risks Docker and Infrastructure Review: * Dockerfiles * docker-compose * Kubernetes * Terraform * reverse proxies * cloud configuration Look for: * root containers * privileged mode * exposed management ports * unnecessary services * public databases * weak network segmentation * insecure volumes * leaked secrets * dangerous capabilities Business Logic Do not restrict analysis to textbook vulnerabilities. Look for business-logic abuse including: * bypassing subscription limits * manipulating plan entitlements * repeating one-time actions * race conditions * referral abuse * promotion abuse * unauthorized state transitions * workflow bypasses * inconsistent server/client enforcement PHASE 4 — ATTACK-PATH ANALYSIS For important vulnerabilities, trace the complete attack path. Example: attacker-controlled input → route → middleware → service → authorization decision → database/storage/external service → security impact Determine whether multiple individually small weaknesses can be chained into a serious compromise. Prioritize exploitable chains over isolated theoretical issues. PHASE 5 — VALIDATION Do not report speculative vulnerabilities as confirmed vulnerabilities.