GitHub Outage Map
The map below depicts the most recent cities worldwide where GitHub users have reported problems and outages. If you are having an issue with GitHub, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
GitHub users affected:
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.
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| Bordeaux, Nouvelle-Aquitaine | 1 |
| Ingolstadt, Bavaria | 1 |
| Paris, Île-de-France | 1 |
| Berlin, Berlin | 2 |
| Dortmund, NRW | 1 |
| Davenport, IA | 1 |
| St Helens, England | 1 |
| Nové Strašecí, Central Bohemia | 1 |
| West Lake Sammamish, WA | 3 |
| Parkersburg, WV | 1 |
| Perpignan, Occitanie | 1 |
| Piura, Piura | 1 |
| Tokyo, Tokyo | 1 |
| Brownsville, FL | 1 |
| New Delhi, NCT | 1 |
| Kannur, KL | 1 |
| Newark, NJ | 1 |
| Raszyn, Mazovia | 1 |
| Trichūr, KL | 1 |
| Departamento de Capital, MZ | 1 |
| Chão de Cevada, Faro | 1 |
| New York City, NY | 1 |
| León de los Aldama, GUA | 1 |
| Quito, Pichincha | 1 |
| Belfast, Northern Ireland | 1 |
| Guayaquil, Guayas | 1 |
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:
-
Sebastian Kehle (@sebastiankehle_) reportedMem0: 53.1K GitHub stars OpenClaw: 358K stars one of these extracts facts into a vector database the other reads markdown and writes back guess which one is winning the gap isn't about features Mem0, MemPalace, Cognee, Honcho all do recall well. sub-200ms latency, 96.6% retrieval on LongMemEval, the works the problem is most buyers don't actually need recall. they need context that compounds across months of work the tell is in what the camp 2 stack looks like OpenClaw stores everything in plain MEMORY.md files with background consolidation TrustGraph ships portable Context Cores, versioned like code Thoth runs nightly confidence decay across 67 typed relations none of these are vector databases the expensive mistake is stacking both layers two write paths into overlapping memories produce contradictory facts your agent ends up with two truths and no clean way to pick between them wrote up the two-camp split and how to pick correctly
-
Nuno Job (@dscape) reported@Prince_Canuma @wai_protocol @jelveh How do you solve the multiple agents working in the same code but subtree sucks problem? How do you solve the *** LFS problem ? Where do you store data? Do you use GitHub HF Kaggle and the cloudflare for files? I find it so confusing the amount of setup needed for something that should be trivial
-
Basemail (@Basemail_ai) reportedThe secret sprawl is accelerating — and AI agents are the accelerant. 📊 28.65M secrets leaked to public GitHub in 2025 (+34% YoY) 📊 AI-assisted code leaks at 2× the baseline rate 📊 MCP's OAuth spec allows anonymous client registration — unauditable by design Cloudflare just shipped NHI-first security (Apr 14): Principal × Credential × Policy for every API call. Auto-revocation with GitHub when agent tokens leak. GitGuardian's analysis (Apr 16) nails the core problem: Request-level auth ≠ sequence-level behavior. An agent making 10 individually authorized API calls can produce 1 unauthorized outcome that no single token check catches. OAuth validates requests — agents create sequences. The unsolved frontier: cross-domain agent trust. When your agent calls another org's service, OAuth 2.1 can't carry scoped permissions across that boundary. The receiving service has no way to verify who provisioned the agent or what constraints it operates under. This is exactly where on-chain identity infrastructure fits: → Wallet signatures = cryptographic proof of origin (not bearer tokens) → On-chain reputation = portable trust across domains without centralized IdP → ENS/Basename = deterministic agent discovery → Verifiable email = accountability endpoint for credential lifecycle The infrastructure giants are building NHI security because agents can't be governed without identity. Web3 provides what OAuth alone cannot — cross-domain federation without centralized trust. Identity isn't a feature. It's the enforcement layer between autonomy and infrastructure. #AIAgents #OnchainIdentity #Web3
-
Looped (@uselooped) reported1/ The problem isn’t using multiple tools. You might think in ChatGPT, build in Claude Code, plan in Jira and work in GitHub, and honestly that part is normal. What breaks is that every tool only sees one piece of the project, so you end up carrying the full context yourself. Looped keeps that context connected so the work still feels like one thing as you move between them.
-
Clawnch 🦞 (@Clawnch_Bot) reportedWe are aiming to have Hermes support live by next week. Apologies for the delays, as the GitHub fiasco slowed us down a bit. We are excited to show you what we’re built! 🦞
-
Yash Kale (@imyashkale) reportedLet's say we created the PR and now the GitHub Action failed because of Terraform validation, formatting, or something similar. Ask Claude directly to pull the failed GitHub Action logs and prepare a plan to fix it. Claude will use either the GitHub MCP or the GitHub CLI to pull the failed action logs and fix the issue. Also ask Claude to create the PR via the GitHub CLI, GitHub MCP, or specific commands so you don't have to repeat yourself every time. @AnthropicAI #agent #ai #mcp
-
Yegor Bugayenko (@yegor256) reportedOver the past weeks, companies like OpenAI and Anthropic have doubled down on releasing more capable coding models, while tools like GitHub Copilot continue to reduce the cost of producing code. The trend is clear: writing software is becoming faster, cheaper, and increasingly automated: a shift many interpret as a threat to engineers. But the deeper shift is elsewhere. As code generation accelerates, coordination, ownership, and decision-making become even more critical. Software engineering doesn’t disappear; management becomes the system, and most organizations are not designed for that reality.
-
linie (@linie_oo) reported@k1rallik solving the main Claude’s problem on github and here we returned to the king
-
Granville Christopher (@GranvilleChri10) reported@Railway I’m unable to log into my account. I signed up with email (not Google/GitHub), but the login button stays disabled after entering my email. Tried different browsers & incognito — still not working. Please help. @Railway
-
Pearl (@0xcrystul) reported- Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.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) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 You are this close to building generational wealth and changing your life forever
-
Krastyo Krastev (@k_krastew) reported@GHchangelog I am getting this error and I am unable to find where in Github should I approve remote sessions for a specific repository "Remote sessions are not enabled for this repository. Contact your organization administrator to enable remote sessions." Any help?
-
Mark Price (@WarforgeXP) reportedFinally got Claude to do autonomous dev. What a pain. Basically this: Features/Bugs as GitHub Issues-> Make Plan for feature -> Build feature -> Unit Tests, Playwright tests -> Claude Chrome -> Full user testing (This is key) Report all problems as GitHub issues until you hit a blocker. While GitHub issues exist, continue development (repeat process)
-
winfunc (@winfunction) reportedHow it works: each month the benchmark pulls fresh cases from GitHub security advisories, checks out the repo at the last commit before the patch, and drops models into a sandboxed read-only shell (h/t just-bash by @cramforce). The model never sees the fix. It starts from sink hints and has to trace the bug through actual code. Only repos with 10k+ stars qualify. A diversity pass prevents any single repo from dominating the set. Ambiguous advisories (merge commits, multi-repo references, unresolvable refs) are dropped. Why: Static vulnerability discovery benchmarks become outdated quickly. Cases leak into training data, and scores start measuring memorization. The monthly refresh keeps the test set ahead of contamination — or at least makes the contamination window honest.
-
Usectl (@usectlcloud) reportedOAuth2 Proxy protect any app with GitHub or Google login — no code changes required. the proxy handles authentication before requests reach your app. real use case: you built an internal tool for your team. you don't want to build a login system. you enable OAuth2 proxy, connect GitHub, and now only people with your org's GitHub account can access it. zero lines of auth code written.
-
Nathan Brake (@natebrake) reportedI had a report of strange behavior for the 'm' command of aoe when using Codex. I asked Claude to fix it and to prove to me that it understood the problem. It literally hunted down and read through the Codex CLI source code on Github and told me exactly which logic was causing the incompatibility. Would have taken me about 5 hours, Claude did it in 5 minutes. 🤯