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 (73%)
• Sign in (15%)
• Errors (12%)

Live Outage Map

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

City	Problem Type	Report Time
Lyon	Website Down	2 hours ago
Tel Aviv	Website Down	4 days ago
Rive-de-Gier	Website Down	4 days ago
Itapema	Website Down	22 days ago
Tlalpan	Sign in	28 days ago
Quilmes	Website Down	28 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:

• 
  Hugo (@hugorcd) reported 19 seconds ago

  You met Nuxi yesterday. Now let me show you what it can actually do. Nuxi auto-detects when you paste code and converts it to an attachment. No more messy prompts. Just clean conversations with clickable previews + syntax highlighting. Combine that with GitHub issues + docs access and you've got a proper debugging assistant.

• 
  Neil Magnuson (@hustlin_heev) reported 4 minutes ago

  When I was a Product Manager I 1. talked to 20 customers, asked why a lot, documented my learnings, isolated problems 2. prototyped solutions in ppt or ms paint 3. created a design brief for my designer to build lo-fi designs 4. designer showed me lo-fi designed, we worked together to improve them 5. designer made hi-fi click thru designs in invision, we showed them to the customers in another round of meetings 6. we then showed them to our engineering team. they spec'ed them out, timelines, etc 7. i wrote jira cards. i vertically sliced the user stories to deliver value at each shipment 8. engineers picked up cards, worked together with back-end engineers and front-end engineers to plan and execute code, push it to github, code review, pull request, CI is broken, lets try again 9. finally it got live 10. i QA'd it before handing it off to a QA analyst to do it 11. i worked with marketing to get the messaging right 12. i worked with pricing team to understand how to cost it, and put that in the marketing. This entire thing took 3 months, at least. Now I 1. Give claude all of my app data, products/orders everything. 2. ask it to create a clear picture of my ICP 3. Send that to claude design and ask it to design a new feature for me 4. Iterate on the design a bit 5. export to claude code i have entire features/products/sites shipped in less than a day. what a time to be alive!

• 
  Snake (@wise_snake69420) reported 7 minutes ago

  My framework is blacklisted by Fable 5 even in Incognito mode I have been trying several ways to try to understand the filter/downgrade. Usually moving to incognito lets me start the conversation. But i noticed once it started parsing my framework fetching from Github or docs sites, it shut me down. But i wasn't 100% sure if it was the topic or the framework. Now in incognito it actually shuts down on first attempt 'dda scaffold by snakewizardd' in incognito is blacklisted. Reproduced twice back to back

• 
  Paul R. (@paul_r113) reported 8 minutes ago

  @github served our deploy pipeline a 5 week old build today and called it the newest one. Their list API put a release from May 3rd in position 1. Their own UI shows it ABOVE the release that has the "Latest" badge. /releases/latest says June, /releases says May. Same repo, same minute. We trusted that ordering for years without a single issue. Today our users got the app from May. Partly on us, the ordering was never documented and we relied on it anyway. But honestly, look at the state of GitHub right now. 266 incidents in the last 12 months, 62 of them major or critical. February was the worst month they've ever had. We're 11 days into June and they already have 12 incidents, 4 critical, one of them an API auth failure literally yesterday. GitHub used to be the most boring, reliable thing in our stack and it just isn't anymore. Anyway, builds are content addressed now. We match on a hash of the build inputs or we rebuild. No more trusting recency from any API, ever. Check your CI. If it picks artifacts by "first item in the list", this one is coming for you eventually.

• 
  nerd.io (@ipersona) reported 8 minutes ago

  new model comes out, github goes down!

• 
  on iphone (@jawniphone) reported 9 minutes ago

  @pxgzi editing mw2 is like 70% troubleshooting, searching error codes in the mvm/sass discords, and 30 tabs of github open, but that other 30% where it actually works is so fun

• 
  Vishal Singh (@vishalsingh2972) reported 10 minutes ago

  @arpit_bhayani Like for GitHub only 15% requests got 401, so now do you block all traffic or just block that particular region/server...? 🤔

• 
  Jake Browatzke 🚀 (@jakebrowatzke) reported 12 minutes ago

  Base44 makes it a lot easier for users to make and launch apps compared to using Claude code. Here's everything Base44 handles for you that you'd otherwise have to deal with yourself: 1. Nothing to install. Everything happens in a single browser tab — no terminal, no code editor, no setting up a development environment on your computer. 2. No code, ever. You make changes by chatting in plain English or using a visual edit mode ; you never read, write, or debug code files. 3. Hosting and deployment. Your app goes live on a URL the moment it's built — no choosing a hosting provider, no deploy steps, no servers. 4. Database. It's built in, so no external database service is needed — no Supabase or Firebase account, no schemas or connection strings. 5. User accounts and login. Authentication is built in with no third-party service required, including access control for membership sites and portals. 6. File storage. Included in the integrated backend — no cloud storage buckets to configure. 7. Email and SMS. Sending is supported without complex setup — no SendGrid account or mail server config. 8. Payments. Included in the platform , rather than wiring up Stripe to your own backend. 9. Domains and SSL. It launches on a Base44 subdomain instantly, and paid plans let you connect a custom domain with SSL included — no DNS or certificate wrangling. 10. Analytics. Every app gets a built-in dashboard showing user activity, so you don't need to set up Google Analytics. 11. Version control. No *** or GitHub to learn — saving and updating happens inside the platform. 12. Technical decisions and upkeep. No picking frameworks or managing dependencies; the platform even auto-selects which AI model to use. 13. One account, one bill. It bundles infrastructure you'd normally piece together from separate vendors, each with its own dashboard and invoice. With Claude Code, Claude writes the code for you, but every item on this list is still yours to own: installing tools, creating accounts with hosting/database/auth providers, holding API keys, deploying, and keeping it running. Base44 is not competing to steal top-end developers from Claude Code. What it's targeting is the 95% of people that don't know how to code but still have app ideas. $WIX, which owns Base44, is now trading at levels it hasn't seen since 2016 despite the fact that Base44 on its own now has nearly as much ARR as all of Wix did when it first it $44, and Base44 is growing at least six times faster.

• 
  Jonah Lau (@jonahlau_) reported 15 minutes ago

  The "just build projects" advice everyone's parroting is creating a generation of students who work for free and still don't get hired A final-year student called me last week spiraling after 450 applications. Turns out he had six side projects, three with actual users, all documented perfectly on his GitHub. Still got 4 replies. All of them asked him to do a take-home assignment that looked suspiciously like spec work for their actual product roadmap. He thought he was doing everything right because every LinkedIn guru told him projects beat degrees. Nobody mentioned that flooding the market with free builders just taught companies they can get free labor before even starting the interview. I've watched this play out across 50+ hiring processes in the last year. The kids with portfolios aren't getting hired faster. They're getting lowballed harder because companies know they're desperate enough to have already worked for free. The ones actually landing offers aren't the ones with the most projects. They're the ones who built something that got traction, realized they had leverage, and walked away from any company that tried to undervalue them. Most students are optimizing for quantity of proof when the market already moved to rewarding the one person who had proof people actually wanted what they made. Every unemployed student with a stacked GitHub is competing against every other unemployed student with a stacked GitHub. The portfolio stopped being the differentiator the minute it became the baseline. If you've already got projects and you're still getting ghosted, the problem isn't that you haven't built enough. It's that you're applying to companies as a supplicant instead of someone they'd be lucky to get.

• 
  Felix Q (@FelixBaize) reported 18 minutes ago

  Today I sat down to write an actual diary entry. I've built myself a complete personal growth workflow. It started from a Skill I made earlier called AI Self-Portrait. At first it was just about understanding myself better. Gradually it turned into using AI to help me see myself clearly so I could collaborate with it more effectively. What I only recently realized is that knowing yourself isn't something you do once and output. It has to be a system that keeps running on its own. Because we keep growing, and AI memory keeps updating too. This is how I'm running it right now. 1. Capture Every day I end up talking to all kinds of AIs about random things. Random sparks, things worth remembering, links I care about, creators I like. I set up a bot on Telegram. The bot doesn't chat — no LLM, it just captures. I just throw text, voice messages, photos, and links at it whenever I feel like it. 2. Processing There's a local workflow running in the background that parses the links, downloads the images and videos, and turns audio into text. Then it files everything into Obsidian by date, platform, and whatever tags I gave the ideas. So each day becomes its own clean, structured folder. 3. Compounding Every day I review what I captured yesterday with an AI, turn the fragments into my own judgments, update my thinking, and solidify it. Once a week I do a bigger review — pull out the knowledge, the iterations, the decisions — and fold them into my personal system to refresh old beliefs. I split the system into a few core modules: Who I am. How AI should work with me. My worldview. My assets. My review logic. Any AI that reads the entry file can figure out who I am in about 30 seconds — what not to do, and what better paths or choices it should suggest based on where I'm at. Put simply, I basically distilled myself. Today I ran the whole setup through Claude's Fable 5 to audit it. It caught a couple of real problems. One was that I had turned my current state into a changelog, which wasn't right. Another was that AI-suggested concepts had leaked into my own cognition files, so my thinking looked messy to the AI — my ideas and AI ideas all mixed together. Left alone, I could easily start mistaking AI frameworks for my own thoughts. I fixed those issues today. Building the system is just the beginning. What actually matters is that it can self-iterate, keep reviewing itself, and keep updating its content. Only then is it truly running. The Skill that started all this is on my GitHub. Next entry: how the weekly consolidation actually works.

• 
  Shobhit - Building SuperCmd (@nullbytes00) reported 21 minutes ago

  @DhravyaShah @supermemory @openclaw Amazing! Found couple of issues right away during setup, where should i open the github issues for this? same repo supermemoryai/supermemory?

• 
  Diego Garcia (@diegogarciamkt) reported 23 minutes ago

  The workflow was basically: I test like a confused but motivated user. Codex reads, patches, runs, documents. Claude reviews and complains. GitHub issues: remember what we learned. Clean Windows machines decide who is lying. Pretty good system, honestly.

• 
  Azael (@theazaelov) reported 24 minutes ago

  This guy makes $20,000-25,000 a month from a dashboard where AI agents push code run social media and close deals for him. No in-house developer. No social media manager. No project manager. At the core is a multi-agent dashboard. It is not one chat with a model. It is a distributed command center where every agent has its own role. Jarvis is the squad lead. Forge writes code. Ghost handles content and SEO. Hype runs social media. Scout digs through research. Closer drives outreach and sales. The whole stack costs $200-800 a month. His command center separates strategy from execution. The owner keeps the strategy. The agents take over the execution entirely. What he does: → The owner sets a goal. Jarvis breaks it into tasks and spreads the cards across the Kanban board between the agents. → Forge creates branches in GitHub opens a PR and ships a site or an MVP. → Ghost writes SEO articles and a changelog. Hype prepares posts and a cadence for the X accounts and fixes broken-image posts. → Scout digs through competitors and new opportunities. Closer collects leads and sends out applications through the outreach pipeline. → Every status flows back into Mission Control. You see what is done what is in review what is stuck and which agent is responsible. → The agents are tied to real assets: Shoa Dev, Moltza, AI Tools Directory, Vydra, ClawHub. Code terminal browser and pricing page are open right next to them. I broke the economics of this command center down into three scenarios. Results: Replacing the team. A manual lineup of a developer an SEO copywriter an SMM a researcher an outreach specialist and a project manager costs $12,000-25,000 a month. The whole AI stack is $200-800. Even at 50-60% of a live team's quality that is $10,000-20,000 saved a month. The setup product. The Shoaf Systems pricing page has three tiers: $199, $499 and $1,499. 20 quick setups 10 business setups and 5 full systems a month bring around $16,465 in revenue and $10,000-13,000 net. The retainer. Support runs $499-1,500 a month. 15 clients at $799 give $11,985 MRR. Together with setup that is $20,000-25,000 a month or $650-830 a day for one operator. If you have ever run several projects at once you know this friction. Either you hire a team for every function and pay from $12,000 a month. Or you tear yourself apart between code content and sales. Or you take on contractors and drown in approvals statuses and blown deadlines. Now he deploys one Mission Control. It unfolds into a matrix of 6 agent roles 7 types of business and 5 ready departments on the marketplace. That is more than 200 configurations of AI teams for any niche without a single new hire. For everyone building an agency a SaaS or a service company one thing matters. A business does not need a smart answer from a chat. It needs constant forward motion of tasks. One chat closes a question. A command center of agents closes a process. At the same time the real power is not in the agents and not in a pretty dashboard. It is in the operational memory that stores decisions texts leads and mistakes. A live team starts from a blank page every time. The system gets sharper with every cycle. In the end he turns an entire operations department into a set of roles and prompts. A new business function is no longer a reason to hire a person. It is just one more card on the board.

• 
  prath (@prathamdby) reported 27 minutes ago

  what do you guys use if you want to triage a whole bunch of open github issues?

• 
  Omri Ariav (@omriariav) reported 27 minutes ago

  amq-squad v1.7.0 (my agent team launcher on AMQ by @avivsinai) now ships a setup wizard. hand it a goal from anywhere: a one-line prompt, a local .md, a github issue, a jira ticket, a doc url. it normalizes that into a brief, helps pick roles, writes team.json + team rules.

• 
  TIC Association (@TicAssociation) reported 29 minutes ago

  @ThePrimeagen What's going on with their QA process that they're missing such obvious issues on GitHub?

• 
  suhan (@suhanprabhu) reported 29 minutes ago

  @NLabhishetty Why dont you setup Claude code as the github action reviewer with fable as the model and xhigh as the effort level Use codex as the workhouse with /goal, point it to your ticket board and instructions - “pick a ticket, make a PR and keep iterating on the PR till the claude code reviewer on the PR says there are no more issues”

• 
  ཏོ་ཧ་ T0ha 📷💻🔬📊⛷️ (@T0ha666) reported 30 minutes ago

  (2/5) The fix? Closed loops. 1. Monitor — PostHog tracks agent behavior like product metrics 2. Orchestrate — Camelot responds to what agents see 3. Improve — GitHub automation turns insights into code 4. Loop — Back to monitoring. Each cycle compounds.

• 
  Jon Radoff 👾/acc 🎮 Metavert (@jradoff) reported 31 minutes ago

  I built markupmarkdown with Claude Code, for teams workaround with .md files: Markupmarkdown is Google-Docs-style review on top of any markdown file, straight from GitHub. Drag-select to comment, threaded replies, @-mentions, realtime sync. Click Edit for an editor with formatting toolbar + find/replace + live preview. Click Push to GitHub for a PR or direct commit. Video shows the whole loop. Why? A lot of real product thinking lives in markdown now. CLAUDE.md for your repo. SKILL.md for your agents. PRDs Claude wrote you. RFCs, prompt libraries, release notes. That's a lot of .md, and the moment any of it leaves your local checkout the review story collapses: * GitHub PRs are too heavy for "this paragraph isn't quite right" * Google Docs strips formatting and forks the source of truth * Slack threads die after a day I added some Claude-specific features too: There's an MCP server at /mcp. Your Claude Code session reads what you read, leaves threads, replies, edits, opens PRs back. Anything destructive needs explicit human sign-off. Personal access tokens scope agents to read / write / admin. Agent comments carry a visible bot badge so threads stay legible. In practice: Claude can drop a thread on the very CLAUDE.md you're collaborating on, propose a wording change, and you either resolve-and-revise or reply with feedback. Same surface, both audiences. The spec stays alive instead of going stale after the first commit. There's also "Revise with AI" — Claude Opus takes the comments you've resolved and produces a clean revision. Word-level diff before you accept. BYO Anthropic key, encrypted at rest. Bonus: paste github com/<org> into the URL bar and get a filterable, shareable index of every .md across every repo they own. Big orgs spider in <10s. Save filter tabs (claude.md, _PRD, …). Private repos respect your GitHub access on every view. MIT licensed. Free. Try it on my website or run it self-hosted. Agentically engineered in Claude Code over a couple of days. Thanks @AnthropicAI for the tools! Try it live: mumd dot metavert dot io

• 
  Sandy4ka (@sandy4kad) reported 35 minutes ago

  Solo agency. $7,000 per client. 1 person. 0 developers. The traditional 10-person agency is dead. Kimi K2.6 does the technical work. You keep 90% of every dollar. 3 services that close in 24 hours: → Automated lead generation: scrapes prospects, qualifies them, sends outreach. Every sales team needs this. Sells for $5,000–$7,000. → Internal knowledge base: workers waste 200+ hours searching files. You index everything. Done. → Customer support: AI handles 80% of tickets without a human. Clients see it live and sign. The stack: → Kimi K2.6 via API — core reasoning, code generation, 80% cheaper than GPT or Claude → Agent Swarm — 300 sub-agents in parallel, real files, bypasses permissions → MCP servers: GitHub for code, Supabase for databases, Slack for client comms, n8n to tie it together Client acquisition runs itself. An agent monitors job listings daily. Any company hiring a data analyst or Python developer is trying to buy their way out of a problem. It reads their website, finds the pain, generates a personalized message. The edge: Kimi has skill ingestion. You give it a markdown file at the start of each job. Healthcare client gets HIPAA files. E-commerce gets Shopify files. Your competitors are sending generic pitches. You're already a specialist before the first call. This is how a solo operator beats a 10-person agency in 2026.

• 
  Derin Olenik (@BigpictureBTC) reported 41 minutes ago

  Real Bitcoin is scarce. Paper Bitcoin is infinite. That single mismatch is why most “Bitcoin treasury” structures will eventually fail. The financialisation of Bitcoin was inevitable, but the first wave tried to jam it into the same legacy rails it was invented to escape: endless share issuance, perpetual dilution, fiat logic dressed in orange. Corporate balance sheets started hoarding BTC the moment its superiority became obvious -- yet in my view its price would already be higher today without this paperisation drag. This phase was unavoidable. Passive accumulation via dilutive equity was the easiest on-ramp. But just like fiat itself, perpetual issuance models are not sustainable. In fiat, the currency holder gets diluted. In Bitcoin treasuries, the shareholder gets diluted. Same cancer, different host. Over time the math becomes obvious: the value created by holding BTC on the balance sheet is slowly offset by the value destroyed through ongoing issuance. At scale, the model is structurally inferior to simply holding spot Bitcoin outright. This is Treasury 1.0 -- a necessary transitional phase, nothing more. Bitcoin doesn’t win by submitting to outdated fiat structures, it wins by extending finance natively. The fix is straightforward: build Bitcoin-native operating companies that earn and compound real sats for shareholders in a strictly non-dilutive way. Those earned sats can then be distributed directly via a true BTC-native digital credit product. That is Treasury 2.0. The framework was created just 8 months ago by @shoneanstey -- the clearest thinker and most committed Bitcoiner in the entire treasury space. It’s no longer theory, he's building it out right now. His GitHub paper is in the comments. Read it. In fact, I’d encourage you to read all his papers on GitHub. He’s a true OG Bitcoiner and the future of the sector.

• 
  Jose (@SolutionsCay) reported 42 minutes ago

  Gave my agents a GitHub App to manage issues across projects. .md task files and local kanbans -> straight to jail. I should have done this months ago.

• 
  Alexandru Vesa (@AlexandruVesa) reported 44 minutes ago

  I ran the same prompt on the same GitHub project — once with Opus 4.8, once with Fable 5. Opus 4.8: decent output, but constant small errors. A lot of hand-holding throughout. Took about 30 mins and ended okay. Fable 5: slower, used way more tokens, but when it finished I had: - A full project diagnostic — A plan for every weakness with reasoning behind it — A proposal for a stronger architecture for future iterations No hand-holding needed. Just results. If your work is complex and logic-heavy, it's worth it. If it's not, stick with what you have. More honest breakdowns on my page, follow if that's useful 👊 LinkedIn in bio

• 
  Bonieky Lacerda (@bonieky) reported 46 minutes ago

  is @github API really down? been trying a simple GET /users/:id for over an hour and get timeout. @githubstatus says operational

• 
  Mahipal (@mukul_jangra) reported 46 minutes ago

  MIT licensed. BYOK — bring your own sandbox keys. Built this after shipping repos with 3,400+ GitHub stars, including Anthropic-Cybersecurity-Skills and CVE MCP Server (covered by CyberSecurityNews). Repo in the reply 👇 #DFIR #malwareanalysis

• 
  Esmail EL BoB  (@esmailelbob) reported 49 minutes ago

  IT"S MY DAMN FOSS APP ON GITHUB AND I HAVE EVERY RIGHT TO ******* ASK IT TO FIX MY CODE SO ******* DO IT, #CLAUDE GET YOUR **** TOGETHER

• 
  artee (@artee_49) reported 52 minutes ago

  github is having an outage right? it’s not in their website

• 
  Yash Agarwal (@yashagl) reported 53 minutes ago

  @legionsdev @RustyRishii Students gets most of this stuff for free… like GitHub copilot. plus if it’s helping you make money then whats the issue in getting that GST registration as a student. I have GST registration, maintaining that only takes about 1-2 hr every quarter… what expenses you talking about?

• 
  Joaquin Ossandon (@cacoos) reported 55 minutes ago

  the main problems are Github syncing.. i don't want to go to Github anymore 1. PRs statuses are completely out of sync, everytime 2. the left sidebar doesn't show any PR state. is it merged? conflicts? checks? 3. no "merge" button? 4. i can't see the PR checks content

• 
  Chaos (@Chaos_lfg) reported 59 minutes ago

  Regarding $DESC, the product may launch today. I did some research, and here’s everything you need to know: Supported by: AR, Molecule , BankrBot, Akash Network 1Claw AI has already been successfully integrated into DescAI. Team Lead Coby recently participated in the Base hackathon. I believe Base will support a project that has been incubated within its ecosystem. The core idea behind DescAI: DeScAI is a project at the intersection of DeSci (decentralized science) and AI. Its core, Agent-Core, is essentially an "automated scientific review factory": an autonomous AI agent that finds scientific content across crypto-science ecosystems on its own, runs it through a pipeline of language models, and produces a structured quality assessment. Crawling. The agent gathers source data from three places: ResearchHub (scientific papers and funding proposals), Molecule IPNFTs (tokenized intellectual property from research DAOs), and Pump Science (chemical compound tokens for longevity research). github Reviewing. Each content type has its own LLM pipeline. For example, the articles pipeline is a 13-step process: extracting scientific claims from a PDF, routing them, and grading the empirical evidence, including originality checks against the OpenAlex database. github Output. Every run produces a standard bundle: review.json with integer scores from 0 to 100, overview.json — a plain-language summary, and evidence_audit.md — a provenance audit trail showing the sources behind each conclusion. github Publishing. Finished reviews can be published to Arweave (a permanent data storage blockchain) and backed up to private Cloudflare R2 storage. Writing to Arweave makes a review permanent, immutable, and publicly verifiable. github In short: it's an AI reviewer that automatically checks the quality of science in crypto-science projects and records its verdicts on the blockchain. Where it will be applied The project addresses the main pain point of the DeSci ecosystem: there are plenty of tokenized "science" assets, but almost no independent expert evaluation. Concrete use cases: Due diligence for DeSci token investors. On Pump Science, people trade chemical compound tokens (like RIF and URO) tied to real longevity experiments. The agent provides an independent AI assessment of a compound's scientific merit before someone buys the token. Gate LearnThe Defiant Evaluating funding proposals. ResearchHub collects crowdfunded research proposals — the agent reviews them and helps the community decide what to fund. Screening research DAOs. The DAO pipeline takes an IPNFT "dataroom" from Molecule and produces a six-category review — in other words, it evaluates tokenized scientific projects and their intellectual property. github Replacing/supplementing traditional peer review. Conventional peer review is slow and closed; here, a review is generated automatically, comes with an evidence trail, and is stored publicly and permanently.