GitHub status: access issues and outage reports
Problems detected
Users are reporting problems related to: website down, sign in and errors.
GitHub is a company that provides hosting for software development and version control using Git. It offers the distributed version control and source code management functionality of Git, plus its own features.
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.
June 15: Problems at GitHub
GitHub is having issues since 02:40 AM EST. Are you also affected? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by GitHub users through our website.
- Website Down (69%)
- Sign in (17%)
- Errors (14%)
Live Outage Map
The most recent GitHub outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Errors | 3 days ago |
|
|
Sign in | 4 days ago |
|
|
Website Down | 4 days ago |
|
|
Website Down | 7 days ago |
|
|
Website Down | 7 days ago |
|
|
Website Down | 26 days ago |
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:
-
Shubh Thorat (@_itsjustshubh) reported@sheriyuo resume screening is broken for AI roles specifically. the signal you actually need is a github and something shipped, not the right keywords on a PDF
-
Dario (@dariozeroshot) reported@tlakomy If @github isn’t down that is
-
Vet (@Vet_X0) reported@02XRP @Vamsi589 ??? What are you talking about Hundreds of bugs and issues are being fixed as we speak because AI is uncovering crypto wide critical flaws. My guy check out the XRPL github more often, it would do you well. I get that only things tangible to you count as something but there are thousands of others here and finding a balance is not easy.
-
DarrenLopez (@darrenlopez001) reportedVibeLayer stops coding agents from putting fetch() everywhere. It gives AI-built apps: - local state first - named mutations - durable queue - backend adapter So apps feel instant, survive reloads, retry failed sync, and stop making every click a server round trip. GitHub:
-
Smukx.E (@5mukx) reported@NinjaParanoid @0xTriboulet @github I have asked about issue very clearly. No response from them since its an weekend... Lets see how this goes..
-
Student Offers (@StudentOffersHQ) reported@Your_PARAM @beingamanFF use github login maybe, could verify you faster, using your personal email would make you wait for days for credits
-
CulturedNiichan (Kuro) (@culturednii_v2) reportedinteresting. Gonna mirror it in my private *** just in case, you know, github, microslop, corpos. So far LibreWolf is totally fine with me, and I guess I could always install adblocking in my opnsense firewall, but still, pretty neat if you don't have a firewall/server
-
CanteLabs (@CanteLabs) reportedapify/apify-mcp-server: The Apify MCP server enables your AI agents to extract data from social... - Open-source GitHub repository - Main language: TypeScript
-
Plebian (@Plebian_2) reported@farmerofcorn @xenovacom I used Claude models until GitHub Copilot priced me out. Now I'm using DeepSeek v4. Just as good. More bang for your buck. Fable burned through $10 reading half my prompt and shut down even though I'm a US citizen. $11K benchmark vs. $500? Can't even do identity services?
-
KIRILL (@Copenhagen0x) reported@GuiBibeau every real hack gets distilled into a rule. the repo has a hacks db that maps historical sol exploits to the rule that would've caught them, so when something new drops onchain it becomes a new SOL-XXX entry. edit one source and it propagates out to every surface (cli, github action, mcp, the editor extensions). so it tracks the actual threat landscape instead of being a frozen checklist. js not ts: fully on purpose lol. the scanner is zero-dep with no build step. plain js means it just runs anywhere node exists and vendors as-is into the mcp server + the action + the vs code extension, no compile/tsconfig in the way. types are nicer dx but the second you add a build you lose "clone and run." kept it boring so it can live everywhere.
-
Rajendra sharma (@DrudgeRajan) reportedThe twist I didn't plan: our PM has no GitHub account (seats cost money). But he uses Claude. Now he reports a bug in plain language and it lands as a labelled issue in the right repo. No seat, no GitHub UI. The interface outlived the tool.
-
Shravan Venkataraman (@theBuoyantMan) reportedGithub copilot outage? Transient API error since 2 hours ago. @github @Copilot
-
Ultron AI (@TheUltronAi) reported- Claude for coding. ($20/mo) - Supabase for backend. (Free tier) - Vercel for deploying. (Free tier) - Namecheap for domain. ($12/yr) - Stripe for payments. (2.9% per transaction) - GitHub for version control. (Free) - Resend for emails. (Free tier) - Clerk for auth. (Free tier) - Cloudflare for DNS. (Free) - PostHog for analytics. (Free tier) - Sentry for error tracking. (Free tier) - Upstash for Redis. (Free tier) - Pinecone for vector DB. (Free tier) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build. It's not that deep bro.
-
Nainsi Dwivedi (@NainsiDwiv50980) reportedThere's a quiet truth in security work: the single most important tool in web pentesting isn't some AI scanner or zero-day magic. It's a proxy that sits between your browser and the target so you can read, edit, and replay every request by hand. The industry standard for that costs $475/year per seat. A software engineer in Amsterdam named David Stotijn built an open-source version as a side project and put the whole thing on GitHub. It's called Hetty, and it does the core loop — intercept, inspect, modify, replay, search your full proxy history — as a single Go binary. No Java runtime. No license server. No account. No telemetry. The detail I keep thinking about: the last commit was over a year ago, and that's not abandonment — it's a feature-complete tool sitting still because HTTP didn't change. The proxy still proxies. A paywall would've expired your license by now; MIT-licensed code just keeps working. It won't out-feature the commercial suite on day one — there's no automated scanner, it's young. But for a bug bounty hunter, the math is brutal: one binary versus a subscription that costs more than your first bounty. The interesting part isn't "free Burp." It's that infosec tooling was community-built for years before it got fenced off — and one person quietly handed a piece of it back. It's called Hetty. MIT licensed. Link in comments ↓
-
Liam Zebedee (@liamzebedee) reported- I cannot push to this *** repo, `gh` is not installed! - I must flag, the images/ dir is 1.4GB. This could be a scalability issue to deploy! ---- What a wuss - Mangling dev.ts server instead of just deleting code - GitHub repo doesn't exist yet (404)! -- a private repo it tried to curl to check if it exists
-
render (@infinterenders) reportedi can’t understand why people can’t learn thing like they tell everything is black box or useless **** or the concepts are over engineered to make money. here I’m not talking about to any single framework/tool things are so different from view of framework authors they built it for a x-specific reason but when the actual reason when it reaches to the framework users it looses entire entity or discipline of what framework authors made it exact imo imo really really understanding abstractions are too damn easy people always tell think in systems perspective which is I love though and it’s what i do regularly so it’s just a practice if you don’t regularly it will be the easiest thing you can ever done before this what principal engineers or any framework authors do creating a abstractions are harder the only thing which I love from react team they create so ******* abstractions and people hate react for the specific reason of what i love When users don't understand the systemic problem the framework was built to solve, they view the internal mechanics as "useless ****" or a "black box they just take a precision surgical instrument and use it like a sledgehammer, building massive, unoptimized, state-entangled applications and . when their app inevitably slows down to a crawl under the weight of their own un-disciplined code, they don’t blame their lack of mechanical sympathy they blame the tool call it bloated reality is that understanding abstractions is actually the easy part. It’s not a superpower reserved for a chosen few; it’s just a regular practice of tracking the flow of data down to the metal. If you look at an abstraction as a window instead of a wall you learn to see how a remote heap reconstruction protocol serializes a tree, or how a double-buffered work-in-progress tree keeps the main thread cooperative and interruptible or whatever we had today this applies to any kinda engineering not just for react Creating those abstractions is where the real genius lies it requires mapping messy, imperative browser realities into clean, declarative structures so respect any kind of open source author those tools are free to use gov takes taxes from you and still it treating and making the **** to pay them money right ? then why aggressive on some framework author just working full time on the tool they like ? When you pay for a product (like a car or a phone), you feel entitled to a specific experience many developers have subconsciously applied that same "consumer mentality" to open source they act as if downloading a package from npm grants them a seat on the board of directors of that project never forget that open source is an act of contribution, not a contract of service When you critique a framework author aggressively you are attacking the person's creative output and their labor You can't "yell" at the government. It’s an abstract, untouchable entity but you can even yell at a maintainer on GitHub or X/Twitter within light of speed lol respect open source
-
Stanislav Kozlovski (@kozlovski) reportedwhy agents need typed graphs to coordinate /w Andrew and Ragnor from Modern Relay, an agent substrate layer built on open-source infrastructure like Lance, Arrow, and DataFusion Timestamps: (0:00) Why build a graph database for agents? (5:43) Why not Postgres or any other relational database? (17:03) The composable "company brain" substrate for agents (20:51) Need for agent guardrails (e.g type safety) (27:00) Importance of Schemas (33:48) NoSQL vs SQL (42:46) Lance, DataFusion, and Arrow as the open stack (51:00) What Modern Relay and OmniGraph are (52:13) Branches: GitHub for agent-written data (1:00:59) Slack Agents, the Dependency Graph and decoupling for parallelization (1:12:32) Why Graphs are great + a 2-year prediction (1:17:32) Centralization vs decentralization for long-horizon coordination problems
-
Anto (❖,❖) (@OtnaEsoj) reportedHere's a clear hint about $POLY that many seem to be overlooking. Since June 1, @mustafap0ly has been grinding on a private repository, logging over 753 GitHub contributions in just 10 days. That's not normal maintenance activity — that's launch-mode intensity. Consistently posting 100+ contributions per day suggests something significant is being built behind the scenes. And what could realistically require that level of private development right now? The strongest candidate is $POLY. The clues don't stop there. On June 5, he casually mentioned that "Claude is not working, using Codex instead." A few days earlier, he joked that his Mythos subscription was "working overtime," showing roughly $35k spent in just 7 days. Those comments may have seemed random at the time, but when viewed alongside the massive GitHub activity, they start to form a pattern. None of this confirms anything. There has been no official announcement. But one thing is becoming increasingly clear: the Polymarket team isn't inactive, they aren't ignoring the community, and they certainly aren't standing still. They're quietly building. Maybe it's $POLY. Maybe it's sooner than most people expect.
-
Rein (@AshenPacts) reportedUpdate: Apparently when i was offline for a month there was a nier rein fan server going up and discourse whether that's ethical or not. 💀 Bunch of nerds 🤓. Who gaf. I'm on the github rn and looking up whether i wanna try this now. "Ermm, sir what about blah blah blah 🤓👆" ky
-
JoePro (@JoePro) reported@benrayfield If The Wringer could take a static single-player HTML game from a GitHub URL and turn it into real-time multiplayer ~ and whether you'd pay server costs while people play. So I ran it. Real Pong gist → The Wringer → working online multiplayer Pong in ONE HTML file. P2P WebRTC, room-code lobby, no game server. Costs $0 to run while you play. 👇
-
fahri-seestarz (@mfahrim7) reportedi spent half an hour trying to make github copilot fix my use statements after i move files and folder around. it did not work. bruh i could've finished 20 minutes ago
-
Ibrahim B. Oduola (@diboworks) reportedIs GitHub down?
-
DefiantAsUsual (@DefiantAsUsual) reported@furgotti @mega_strimp Ah yes, the companies with good data security. Like the massive corporations that get hacked and have leaks quite frequently in this day and age? Even Microsoft had major hacker issues a few days ago that affected GitHub and involved malware distribution.
-
Abhishek Singh (@0xlelouch_) reportedTop 10 DevOps resources I’d actually point working devs to: 1) The Phoenix Project (book) Good mental model for flow, bottlenecks, and why ops work keeps derailing roadmaps. 2) The DevOps Handbook (book) Concrete practices: CI/CD, trunk-based dev, change mgmt, metrics that matter. 3) Google SRE Book (free online) SLOs/SLIs, error budgets, incident response. Turns outages into an engineering loop. 4) Kubernetes docs + kind/minikube (docs + practice) You don’t learn K8s from slides. Deploy, break DNS, debug probes, read events. 5) Terraform docs + a small AWS/GCP lab (docs + practice) Write modules, remote state, locking, plan/apply discipline. Learn drift the hard way. 6) Docker docs (docs) Images, layers, networking, volume semantics. Fix your own Dockerfile instead of copy/paste. 7) GitHub Actions (or GitLab CI) docs (docs) Build a pipeline: test, lint, build image, scan, deploy. Learn secrets, caching, artifacts. 8) Prometheus + Grafana docs (docs) Instrument one service, build 3 dashboards, and alert on symptoms not CPU%. 9) OpenTelemetry docs (docs) Traces change how you debug distributed systems. Add spans, propagate context, sample sanely. 10) Practice project: run a tiny service in ****-like mode (project) API + Postgres + Redis, IaC, CI/CD, canary deploy, rollback, on-call runbook, 2 failure drills (kill a node, expire cert)
-
CodePhobic (@codephobic) reported@0xhashchan it's slightly better, but still not exiting enough. Still rely on centralised github to certain extend so availability is better but still not guaranteed. still not solving issues like versioning, backend dependency.
-
Hasan Toor (@hasantoxr) reportedSo I found a github repo that stops AI agents from burning tokens for no reason. It’s called Headroom. It's built by a guy name Tejas Chopra who works at Netflix. Basically, it compresses all the things your AI agent reads before it reaches the LLM. For example: - Tool outputs - Logs - Files - RAG chunks - Code search results - Conversation history Developer claims 60–95% fewer tokens with the same answers. Right now you can use it with: - Python/TypeScript library - Local proxy - MCP server - Wrapper for Claude Code, Codex, Cursor, Aider, and Copilot If your coding agent is getting expensive, slow, or lost in giant logs, this repo is worth checking out. Thanks for reading.
-
hashchan (@0xhashchan) reported@codephobic Ah not like zeronet, though that was a supercool project. Like just pass a dist/ folder off of github and get users to pay it forward, but if github goes down pass it inside a torrent and a user can open it in localhost
-
Ugne (@ugnead) reportedthis repo claims it can cut AI agent token use by 60-95% it is called Headroom, and on GitHub it already has around 25k stars the pain is obvious if you use AI agents. they keep feeding logs, files, JSON, tool outputs, search results, and docs into the model that gets expensive fast Headroom sits before the LLM and compresses what the agent is about to send the repo has a proxy, Python and TypeScript libraries, wrappers for tools like Claude Code and Codex, and an MCP server their example shows a debugging trace going from 10,144 tokens to 1,260 while still solving the same problem
-
Jon Church (@jonchurch) reported@jdxcode @nateberkopec @github I know that’s not feasible for everyone, some folks want to read issues etc in their private repos. But, finger to the wind, I think the majority of devs dont use the cli for private repos so default should be opt in not opt out for higher privs
-
Karan Bhilhatiya (@karanbhilhatiya) reportedafter months of building, posting, and shipping i've concluded that my github visibility is still terrible. time to beg for stars. shamelessly.