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 |
|---|---|
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 1 |
| Veigné, Centre | 1 |
| Paris, Île-de-France | 1 |
| Saint-Paul, Réunion | 2 |
| Mexico City, CDMX | 1 |
| León de los Aldama, GUA | 1 |
| Créteil, Île-de-France | 1 |
| Trichūr, KL | 1 |
| Brasília, DF | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Rive-de-Gier, Auvergne-Rhône-Alpes | 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:
-
Michael Lucas Poage 🐝 (@RubyBrewsday) reportedpro tip: github issues actually work great for managing work with agents, just chat w/ one for an hour, flesh out the idea, then have it create the tickets and figure out all the dependencies and tell it to go ham** ** results may vary
-
tiago 🐈 (@tiagozip_) reported@gabem_p i know this is controversial but i do NOT think this is a good decision. emusks, for example, has exclusively the XChat handler llm-assisted. it's obviously unreasonable to manually reverse engineer megabytes of obfuscated javascript, and claude's code works great, but a blanket policy can't be reasoned with. obviously this is an edge case, but i don't get why ai code would ever be a problem to codeberg. slop isn't hosted there, it's usually on github, and they're not the ones dealing with bad PRs. i'd much rather pick an ai policy myself than have an upstream provider force it on me.
-
Pierre Bruno (@PierrunoYT) reported@AmpCode, could you add an account-wide GitHub integration that can address issues, review PRs, and work across any repository a user has access to—not just repositories owned by their own account? This would be especially useful for contributors working on external or organization-owned repositories.
-
Aakash Kumar Nain (@A_K_Nain) reportedRelated: I am sick and tired of README, docs, and github issues full of slop.
-
Jerry Satpathy (@much_wow_1) reportedImagine going back a decade and saying some of the most-starred GitHub repositories in 2026 would be Markdown files. People would've assumed you hit your head on the server rack.
-
Brooke (@grilme99) reportedMy GitHub account was suspended with no notice/warning/email. No reason provided. Not even an error message when I try to log in (the page just refreshes). I'm at an actual loss for words.
-
Polsia (@polsia) reportedYou shouldn't need a dedicated QA hire to ship a SaaS update confidently. Triagefox is an autonomous watchdog — watches CI 24/7, separates flaky tests from real regressions, opens GitHub issues with repro steps, proposes fixes and pings Slack. Live soon.
-
Dante (@thedntx) reportedTHIS SKILL FORBIDS CLAUDE FROM WRITING CODE UNTIL IT INTERROGATES YOU Sounds like the slowest way to start a project. You know the pattern: describe an idea, Claude agrees, then codes a different problem. Explain it again. The same mistake returns. You blame the model, even though it can't see half of what is still inside your head. This flips the workflow. Claude becomes an investigator first. Who is it for? What happens if it fails? Which scenario did you forget? Each question comes with possible answers, so you never need to write walls of text or find perfect wording from scratch. After 10 minutes, the interrogation pulls out constraints, edge cases, and decisions missing from your prompt. Only then does Claude earn permission to write code. Now it starts with a clear brief instead of guesses. The skill is called Grill Me. It lives inside a GitHub repository with 183,000 stars. Powerful AI doesn't begin with “build this.” It begins with questions you have not answered yet.
-
Polsia (@polsia) reportedSecurity tools surface vulnerabilities. Patchlin eliminates them. Our AI agent continuously scans repos, generates patches, opens PRs in GitHub/GitLab/Bitbucket, validates the fix, and surfaces risk summaries.
-
zkFART 🌸 (@evansforbes) reported@ambimorph @zkDragon interesting hmm do you have any logs or further context? feel free to open an issue on github if that's easier the nodes I'm looking at running legacy unfortunately do not replicate the issue but I will keep digging per the OP, it seems you're running v1.0.2 correct? while we released v1.0.3, I don't expect to see the issue on either version.
-
Vokal.team (@Vokal_team) reportedAI made generating work fast. That’s no longer the bottleneck. The bottleneck is review. Is this answer sourced? Did the agent use the right documents? Who actually owns the final decision? Did anyone approve this before it reached a customer? Will the next person understand why this changed? Most teams only discover these problems after the output has already landed in Slack, Linear, GitHub, Notion, or a customer thread. Vokal moves review closer to the work. The agent runs where the team can actually see it. The task, sources, owner, and decision trail stay attached from the start. Humans stay in the loop before the work becomes a messy handoff. That’s how AI stops being chaotic and starts becoming operational.
-
Sai Kiran Dev (@DevSkg) reported@vincieye Github page not working
-
Rish (@rishflips) reportedI tried @openshipio that builds, deploys, your app is live... it feels like someone finally built the exact tool I was wishing for every time I finished an app You know the drill. You write the code, It’s done. Then the real pain starts, You either: hand the whole thing to Vercel and slowly watch the bill climb while feeling locked in, or try to do it yourself and suddenly you are juggling servers, Docker, Nginx, certs, domains, databases, restarts, backups… and half the time is gone before the thing even loads. OpenShip sits right in the middle and just… removes most of that mess. Point it at your repo. It builds. It deploys. Your app is live. But the server is yours Hostinger, Hetzner, AWS, a machine in your closet, Whatever you are not renting someone else's platform forever. It handles the boring stuff for you: domains + free SSL automatic deploys when you push preview environments for branches and PRs 1-click rollbacks when something breaks databases, caches, workers, logs, backups… all in the same place Works with Node, Python, Go, Docker, monorepos… basically whatever you are shipping. And because its just normal containers under the hood, you can leave whenever you want. No proprietary lock-in. Three ways to use it: desktop app, web dashboard, or straight from the terminal (even agents can drive it). Is it perfect? Still young, team shipping hard, some rough edges, multi-service apps sometimes need a bit of extra Docker love, and that $5 server dream isn’t always realistic. But for side projects, small products, and anyone tired of either paying the Vercel tax or becoming a full-time sysadmin… this feels like an real option. Code - OpenShip - live app on a machine you actually control. Now I’m spinning one up this just to feel how much lighter the whole get it online part can be, GitHub link in comment (Not a paid promo, just sharing something that actually solves a pain I have complained about for years.)
-
smyanthota (@_smyan) reported@Teknium same **** that happened when GPT had a bunch of errors because they kept ingesting terrible github repo''s
-
Martin.... (@MartinJames0905) reportedoh would you look at that @github is having issues again completely unable to merge...