1. Home
  2. Companies
  3. GitHub
  4. Outage Map
GitHub

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

Loading map, please wait...

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:

Less
More
Check Current Status

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
Paris, Île-de-France 6
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
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
Check Current Status

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:

  • francdetank
    franks 🇦🇷 (@francdetank) reported

    @rmansueli thanks Rodrigo! I cant create one because I got a problem . My account is pegged to Github and github has flagged me. That way I am blocked to enter the dashboard. I would like to connect my account to my email instead of github.

  • minnelli
    Kevin Minnelli (@minnelli) reported

    WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

  • yeemio
    Yeemio (@yeemio) reported

    owlrunkit is on github now. public corresponding source for the npm package. issues go here.

  • AbdallahSh07
    Abdallah Shaban (@AbdallahSh07) reported

    @rashed_sahaji @FlutterDev Got it - did you perhaps submit a GitHub issue to help us triage this? It would be tremendously helpful if you can please do that!

  • jothantranston
    joithan (@jothantranston) reported

    THIS 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.

  • thesaloninarang
    ѕaℓoηι ηαяαηg (@thesaloninarang) reported

    I review resumes for DevOps beginners at meetups, and the same fixable problem shows up every time: bullets that describe the tool instead of what YOU did with it. Let me show you the difference with real rewrites. BEFORE: "Worked with Docker and Kubernetes" AFTER: "Containerized a 3-service Node app and deployed it to a local Kubernetes cluster with health checks and resource limits" BEFORE: "Knowledge of CI/CD" AFTER: "Built a GitHub Actions pipeline that tests, builds and pushes images on every merge to main" BEFORE: "Familiar with Linux" AFTER: "Debugged container startup failures using logs, exec and inspect on Ubuntu servers" See the pattern? Verb, artifact, specifics. A hiring manager can picture the AFTER versions. The BEFORE versions could be copied from any job description, and that is exactly how they read. You do not need production experience to write bullets like this. Personal projects count when you describe them concretely.

  • BrunoRJ33
    Bruno (@BrunoRJ33) reported

    @openclaw @github Endless codex and claude code tokens to fix it from time to time… and to improve its harness. I currently run around 10 claws 🦞. 24/7 for several purposes.

  • GustavoNenesk
    Nenesk.ron (@GustavoNenesk) reported

    What if there's a way to save hacked Ronin Wallets? A member of the community @YutsuKito found a way to save assets from drained wallets The issue is you need ronin:native to transfer assets, but whenver you deposit RON you get auto drained Need RON to revoke the malicious draining contract -> send RON -> gets drained -> can't revoke He found a solution for the keyless wallets where you can pay the gas fee with a safe wallet, allowing you to save lost axies or NFTs that have not been drained Interesting stuff. He sent the code for SM to review as an open-source project. Github link below

  • Linus_Shyu
    🦄Linus Shyu许发鑫高考去了不在 (@Linus_Shyu) reported

    Stop treating token rotation as a success path. x_bot: OAuth refresh token rotated, cache save failed, GitHub secret stayed old. Next cron died on invalid refresh token. Fix: save to secret BEFORE confirming with X, or write-after-rotation with retry. #DevTools #AI

  • sanereverie
    shifan (@sanereverie) reported

    building something that races coding agents on the same GitHub issue and scores the PRs. coming soon.

  • IshankDev
    Ishank (@IshankDev) reported

    7/ 16k+ GitHub stars. Built for people who want control, not another marketing-suite login.

  • Anime0t4ku
    Anime0t4ku (@Anime0t4ku) reported

    @c_hri_s Github issues are not closed. Mahbe refresh your webbrowser.

  • PatelVatsalp732
    Curious Explorer (@PatelVatsalp732) reported

    I burned 14B Codex tokens. The official usage UI still cannot tell me what actually ate the weekly cap. So I shipped a Codex-only board: GitHub login, local-first sync, private by default, optional public rank + shipping proof. Roast the metric or join it.

  • vietroadie
    阮添福-ThiênPhúc (@vietroadie) reported

    Feature 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? 🙋

  • paulrodturner
    paulrodturner (@paulrodturner) reported

    @supabase Is anyone else having issues logging in via Github?

Check Current Status