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 |
|---|---|
| Ahmedabad, GJ | 1 |
| Delme, ACAL | 1 |
| Lyaud, Auvergne-Rhône-Alpes | 1 |
| Catania, Sicily | 1 |
| Inverness, Scotland | 1 |
| Quito, Pichincha | 2 |
| Junín, Manabí | 1 |
| Guadalajara, JAL | 1 |
| Paris, Île-de-France | 6 |
| São Paulo, SP | 1 |
| Ipauçu, SP | 1 |
| Vigo, Galicia | 1 |
| Tel Aviv, Tel Aviv | 1 |
| Éragny, Île-de-France | 1 |
| Saltillo, COA | 2 |
| Montlhéry, Île-de-France | 1 |
| Aulnay-sous-Bois, Île-de-France | 1 |
| Granada, Andalusia | 1 |
| Vernon, Normandy | 1 |
| Township of Evan, KS | 1 |
| Madrid, Madrid | 1 |
| Bogotá, Bogota D.C. | 1 |
| Lyon, Auvergne-Rhône-Alpes | 1 |
| Lima, Lima | 1 |
| Aix-en-Provence, Provence-Alpes-Côte d'Azur | 1 |
| Trento, Trentino-Alto Adige | 1 |
| Le Chambon-Feugerolles, Auvergne-Rhône-Alpes | 1 |
| Antananarivo, Analamanga | 1 |
| Lure, Bourgogne-Franche-Comté | 1 |
| Ashkelon, Southern District | 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:
-
joithan (@jothantranston) reportedTHIS GUY BUILT A TINY AMOLED DESK BOARD JUST TO STARE AT HIS STRIPE NUMBERS it's a Waveshare ESP32-C6 touch panel that sits in your peripheral vision and cycles business metrics so you stop digging through Stripe > same ESP32-C6 board people use for Claude Code token meters, flipped to revenue > eight screens, five seconds each: MRR, new paid, paid subs, cancelled, ARR, ARPU, net 30d, failed > empty screens hide themselves so a young account sees a shorter loop > polls Stripe every five minutes on a read-only key (subscriptions + invoices) > marks itself stale instead of showing a number it can't vouch for > no soldering: flash over USB, finish Wi-Fi + key setup from your phone > data stays on the board; no project server in the middle firmware free on GitHub: cosjef/stripe-desk-display. board ~$30–$36 (Waveshare ESP32-C6-Touch-AMOLED-2.16). chat and terminal can't sit in your eye line for five hours. a tab you have to open is a tab you stop opening. this is what "the numbers find you" looks like as a brick on the desk.
-
🍔Kangdalf👑 (@WhopperWizard) reported@cachesaur > claude, get your changes into github what's the problem?
-
阮添福-ThiênPhúc (@vietroadie) reportedFeature request for @TradingView @TrendSpider @Schwab (ThinkOrSwim) engineering teams: Please add GitHub-native CI/CD for custom indicators. Connect a repo → validate on push → deploy approved scripts to my workspace → full version history + rollback. 1/ The Problem I maintain the same level set across ThinkScript, Pine, and JS. One level change = 3 manual copy/pastes into 3 browser editors.Result: drift between platforms, stale timestamps, and levels that silently disagree mid-session. No audit trail of what changed or when. 2/ Core ask — repo connection • OAuth GitHub App install, scoped to selected repos • Map a file path → a specific study slot (e.g. ES Levels/ES_LEVELS.pine → "ES Levels") • Branch selection (deploy from main, preview from a branch) • Config in-repo, e.g. .tradingview.yml / .trendspider.yml 3/ Core ask — validation • On push/PR: compile + lint the script server-side • Return errors as GitHub check runs with file + line numbers • Block merge on compile failure • Optional: run a backtest or smoke-render and post results as a PR comment 4/ Core ask — deploy • Auto-deploy on merge, or manual "promote" button • Atomic: study updates or fails cleanly, never half-applied • Deploy to draft/private first, publish separately • Preserve user-set inputs across deploys where param names are unchanged 5/ Core ask — versioning & safety • Every deploy tagged with commit SHA, author, timestamp • Version list in the UI with diff view • One-click rollback to any prior commit • Dry-run mode • Deploy log / webhook on success + failure 6/ Minimum viable alternative If full CI/CD is too big, just ship a documented REST API: GET/PUT /studies/{id}/sourcewith token auth + rate limits. We'll build the GitHub Action ourselves. That single endpoint unblocks the entire workflow. 7/ Why it matters Scripts are code. Code belongs in version control with review, CI, and rollback. This is table stakes in every other dev ecosystem — and it directly reduces the risk of a bad indicator edit going live during market hours. Who else needs this? 🙋
-
Vitaliy Salyuk (@vitaliysalyuk) reported@openclaw @github Fix your updater and I might give it another shot.
-
Anime0t4ku (@Anime0t4ku) reported@c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.
-
Tejas Dinkar (blue tick here) (@tdinkar) reportedHey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.
-
Rusty Williams McMurray (@1RustyMac) reportedPersistent AI doesn’t have a supply chain problem at the model. It has a supply chain problem at the moment it changes its mind. Personality drifts. Tools get installed. Memory accumulates. The thing you shipped on Monday is not the thing answering on Friday. We can attest who built the weights. We still cannot attest who authorized what the agent became on Tuesday. That is the hole. Who is allowed to let it change? We built Living Supply-Chain Security for Persistent AI Organisms around one law: The organism may propose evolution. It may not authorize it. No trace, no drift. If an agent wants a new personality, a new tool, a new maturity, or a rollback — that change does not happen because it felt confident. Confidence is not a key. Self-narration is not evidence. Evidence is not interpretation. Interpretation is not authorization. Authorization has to come from outside the organism, bound to the exact change, used once, and written into an append-only history. Even a rollback cannot erase the record. You can restore a prior state. You cannot pretend the detour never happened. Default-deny. Hash-chained. Externally signed. We froze battery v1 on July 5 and ran it against the paper’s own claims. It held. That is executable evidence. Not a proof. Not a production blessing. Not “alignment, solved.” If it can’t be attacked, it isn’t finished. GitHub later this week. Come try to break it.
-
Jason Waters (@jasonwaters87) reportedAnthropic just open sourced the code Shopify runs their shopping agent on. Free on GitHub. And I’m having lunch with a surgeon in San Jose last month and he tells me a patient no shows and nothing happens. Nothing. He has to walk up to the front desk himself and ask “did you guys call them?” 3 or 4 schedulers looking after 75 doctors. One automated call before the appointment and that’s it. His own dermatologist sends him three reminders. He called that “an easy fix.” That’s a merchant agent. Reminds the patient, rebooks the no show, tells him Thursday isn’t full so he can put a surgery on it. The code is sitting there free. Somebody still has to walk into his office and build it.
-
Russ Wonsley (@RussWonsley) reportedMy @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?
-
radhika (@RaadhikaThacker) reportedYAML’s more like a rule book/recipe that builds the form for you. Then I figured YAML was a forms thing. Nope. It’s just a way of writing information down in a structured way. GitHub uses it for a form. Kubernetes uses the same thing to describe a server.
-
Coder Junkie (@CoderJunkie) reportedBelNet Android v1.4.1 now has a public shipping checkpoint. GitHub evidence: released Sep 1 verified commit d23f155 four downloadable assets Android API level 36 revamped design latency and performance fixes that is more meaningful than a repository “updated” label. a tag identifies the version. artifacts give users something to install. but “fixed latency issues” still needs a measurement surface: median connection time p95 latency packet loss failure rate region and device breakdown release notes tell us what changed. benchmarks tell us how much it changed. BelNet shipped. now let the numbers login. @BeldexCoin #Beldex #BelNet
-
Lummox (@Lummox_eth) reportedMy own built Grok Bot turned $1,000 into $5,300 for last 17 hours. Now the project behind it is sitting around $25K market cap. We already pushed past $60K once and gonna hit $200k soon The bot is still running. The utility is almost ready. GitHub is live. Dev tokens are burned. I’m still buying. Nothing about the actual project changed because the chart went down. At $20K MC, this is the entry I personally like far more than chasing the first move. The target hasn’t changed either. $100K+ is where I want to take this next. $LUM is just getting started.
-
Chris (@chriscoolstuff) reported@pfernan95dev For the SEO part there's one thing that I've been also doing: Ask your agent what keywords you should search for relevant to your app on answerthepublic, perplexity and google Gather all that info old fashion, by yourself - might take around 2 hours but it's worth it Plug all that info into the agent and have it give you 5 titles for 5 articles Make it write those articles - maybe use nosoopai github or edit them manually so they seem more human like Connect the agent to google console After 1 month tell the agent to review the results If no article took off you can wait one more month or put up 5 more After the next month check what worked and double down on that
-
Jeremy W (@basicBrogrammer) reported@bot Anyone else have an issue with the grok bot GitHub connector?
-
Konstantin Elfimov (@elfh78) reported@topjohnwu Sorry for posting in the wrong place - I was trying to add magisk bug report on github and alway got errors with automatic issue closing. Is there any possible way to send it directly to you?