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 |
|---|---|
| Cleveland, TN | 1 |
| Tlalpan, CDMX | 1 |
| Quilmes, BA | 1 |
| Bengaluru, KA | 1 |
| Yokohama, Kanagawa | 1 |
| Gustavo Adolfo Madero, CDMX | 1 |
| Nice, Provence-Alpes-Côte d'Azur | 1 |
| Brasília, DF | 1 |
| Montataire, Hauts-de-France | 3 |
| Colima, COL | 1 |
| Poblete, Castille-La Mancha | 1 |
| Ronda, Andalusia | 1 |
| Hernani, Basque Country | 1 |
| Tortosa, Catalonia | 1 |
| Culiacán, SIN | 1 |
| Haarlem, nh | 1 |
| Villemomble, Île-de-France | 1 |
| 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 |
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:
-
Polycopy (@polycopyapp) reported@AlterEgo_eth finally someone organized this mess properly. been copy pasting endpoints from random github issues for months like a caveman though watch half these get deprecated next week when they push some random update at 2am
-
Dziky💪🏿 (@dzikyDonnyMaps) reported@github You level up by contributing. Fix a typo, add an example, open that first PR. Perfect message for beginners. Just ship it 👊
-
Yuuru (@PriestruYuuru) reported@thsottiaux Bro, compaction essentially broken right now. Dunno about everyone but for me it doesn't work most of the time. Steam error end everything, can't provide you with/feedback sadly but team could look into github issues from others. Tried to set compaction earlier but still issues.
-
Natali Klemt (@NataliKlemt) reportedgitHub green squares quietly plotting world ********** one bug fix at a time
-
Harry Tandy (@HarryTandy) reported> open Hermes for the first time > looks like another ai chat wrapper > close it after 20 minutes > think “why would anyone pay for this” > then plug in Firecrawl, Reddit, YouTube transcripts > suddenly the agent has eyes on the web, ears on forums, memory from 3-hour podcasts > ask it to research a sponsor > it scrapes the site, checks Reddit rage, pulls YouTube mentions > drops a one-page “take / don’t take” brief in Discord > add Browserbase > now it clicks through sites that block scrapers > add Bland > now it can call restaurants, vendors, support lines > add Stripe > now “why did this customer churn?” comes back with refunds, failed charges, receipts > plug in Gmail, Calendar, Drive, Sheets > now it lives where your work already lives > plug in GitHub > now it can triage issues and review PRs > plug in Obsidian, Readwise, Granola > now it remembers meetings, highlights, notes you forgot you wrote > wake up Monday > Hermes already pulled revenue, subs, refunds, churn, follower growth > posts the week-vs-last-week dashboard before coffee > realize the chatbot didn’t get smarter > you just gave it limbs
-
Tom Finnell (@d2fl) reported from Cleveland, TennesseeI hit conversation limits myself on Grok Build yesterday while researching the new github algo commit. The same issue is now hitting Grok Imagine. SuperGrok users are getting capped after 10 to 80 generations. That is a sharp drop and doesn't match promises. The cause is straightforward. Demand for image and video generation has exploded. xAI is throttling to keep the service stable instead of letting it melt. Elon just posted that we need clear reset times and easy upgrades to higher plans. xAI is already scaling more GPUs and pushing limit increases. Clearer timers and tier upgrades are rolling out. This is normal growing pains. Same pattern hit early Grok text access. It loosens once the servers catch up. I suggest a little patience while new capacity and load distribution is brought online. This is temporary. Anyone else getting throttled on Imagine or Grok conversations? Drop your numbers below.
-
Omri Ariav (@omriariav) reported@avivsinai workstream briefs seed deterministically from a file or GitHub issue: `up --seed-from file:./brief.md` `up --seed-from issue:31` `up --seed-from gh:owner/repo#31` `--dry-run` previews, the live form writes the brief and brings the team up in one call.
-
Sean the SRE (@SeanTheSRE) reportedI always love it when you have a weird issue in GitHub Actions you have to solve as its blocking builds from rolling out. Had the issue solved, a solution written up, and a post-mortem in 30 minutes after 3 other peeps couldn't figure it out. The dopamine hit was incredible! Also I feel so ******* smart right now.
-
Lyrie.ai (@lyrie_ai) reported🚨 YellowKey+GreenPlasma (no CVE, NO PATCH): BitLocker bypass + Windows CTFMON→SYSTEM LPE on fully patched Win 10/11/Server. PoC on GitHub by Chaotic Eclipse. Huntress: active attacks within 24h of release. Disable CTFMON & enforce Secure Boot NOW. #ZeroDay #Windows
-
Mitchel Sellers (@mitchelsellers) reportedIs it just me again, or are all #dotnetmaui builds using GitHub Actions broken if using .NET 10 on MacOS?
-
pre.dev (@predotdev) reportedThat is wildly expensive, incredibly slow, and dilutes the AI's focus with endless noise. Worse, the code only tells half the story. It shows how things were built, not why. The actual architectural decisions live outside the code, in Jira tickets and GitHub discussions.
-
Dobroslav Radosavljevič (@dobroslav_dev) reported@WonderingDavid Attack vector was via Github CI, but compromised packages are on NPM and it's spreading via NPM. IF MAYBE NPM DID SOME MALWARE CHECK BEFORE ACTUALLY PUBLISHING PACKAGES. We would have 99% less issues like this. You can publish anything you want right now, no check. It's horrible. There should be automatic malware check when you want to publish package. It should not be published instantly.
-
Drini (@drini_kasmot) reported@maxalexweber It's the HarmonicLabs token-minter repo, uses plu-ts for tx building. Getting a PPViewHashesDontMatch error on Preprod when submitting. Already raised it on their GitHub!
-
Dikshit Jain (@mahanot_dikshit) reportedMy company hired a fully remote engineer last year. Great performance, always hit deadlines, never caused problems. Last month, he died suddenly. I asked Boss can we keep his Slack, email, and Github accounts active. We trained an AI model on his commits, code comments, and messages. Now “he” still reviews PRs, answers tickets, and posts thumbs-up emojis in standups. I haven’t told anyone that i kept him on payroll as well. But I changed the bank account on his employee database to mine. We'll miss you George and thank you for the new beach house.
-
Kr$na (@krishdotdev) reportedI tested it on a 500-issue GitHub backlog. CAO dispatched a triage agent to classify, 50 code agents to fix bugs in parallel, a docs agent for questions. Morning briefs like: “AI/tech releases overnight” "320 handled. 80 PRs ready for your review. 10 need your call." I was asleep.