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
Itapema, SC 1
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 1
Dortmund, NRW 1
Davenport, IA 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:

  • IBreakData
    Alexander Zbiciak (@IBreakData) reported

    @luce_libera @wodarg One issue with the data is the data entry permutations are these the same lots? EW172 EW0172 PFIZER EW0172 #EW0172 Some entries just say pfizer or worse. The data needs guided cleaning to really show hot vs not lots @grok please review the github data and find the potential permutations for the pfizer lot ewo172 as shown above. Are there othe potential entries and what are the totals for that lot.

  • mattoftheland
    mattoftheland (@mattoftheland) reported

    I really hope Microsoft is doing something to fix all these supply chain compromises on Github and NPM. It's ridiculous this is happening daily.

  • gcrtrd
    GCRtrd💊 (@gcrtrd) reported

    @Pumpfun To elaborate, this is what I would like to see happen: > Spawn/Bonding mcaps: Altered on SOL curves such that its similar to USDC levels. What really matters is spawn mcap, should be 5k minimum. > Creator Rewards: This is the biggest thing that needs a revamp. What I think: - Deployer should always get 10-25%, and the CTO process should be streamlined. This encourages devs to launch while not being quite lucrative enough to encourage the farming we initially saw. - Removal of Cashback and Agent modes. - The remaining % can be redirected to wallets, github, or used for Airdrops. Airdrops would rapidly become the default much like Cashback is now. - The Airdrop pool should be a CENTRAL pool across ALL Pumpfun coins. Holders of longer-term tokens receive a higher weighting for their airdrop rewards. This balances out the new pair vol churn with older tokens that have periods of low volume. > Terminal: Delete the multiwallet-bundling and anonymous funding features. Sure, many will still use Axiom for this, but what does it say about you as a platform when you are directly ENCOURAGING and ENABLING this behavior? > Anti-Sniping/Botting: There's gotta be some solution here. A possible one is to create a new wallet each time someone deploys, so the actual mint transaction and initial buy come from an unsnipable source, but leave the Creator field tag as the actual deployer. Another one is to gate Pumpfun launches to the site itself via a dual-wallet signing (where the central PF wallet only signs if a captcha is completed). There are workarounds, but they cost money and add a delay to the deployment. Right now, its far too easy for people to use tools like Uxento and J7 to bundle launch. > Mayhem Mode: delete this > PR: For the love of god, hire a real PR team. There have been so many instances this year where there was ZERO communication after major PF bugs or implementations (such as 0 announcement or discussion of Mayhem Mode for months, and ZERO announcements when the bonding curve was broken for hours). These are just the ideas off the top of my head.

  • navanchauhan
    Navan (@navanchauhan) reported

    @ibuildthecloud @soederpop @progrium kinda (?) or, maybe I need to start rephrasing I use a backend as a distinction between a static app you deploy on GitHub pages vs say something on vercel with an api server. But, then you get into the pedantic argument that technically when you are using say sqlite.js from unpkg then you are using a backend too. And, then I give up and cry myself to sleep because everything we do is meaningless and maybe we just need to just find happiness in our burden like Sisyphus. Wait, what were we talking about?

  • ChelmsDeep
    Chelm's Deep (@ChelmsDeep) reported

    @plainionist @PaulGugAI This actually works ridiculously well. Was having problems with recurring errors and debug loops. I harvested information from some github repos built in the same stack, added a skill to read the knowledge base and search the repos, fixed 12 issues on the first turn.

  • DmitryRybin1
    Dmitry Rybin (@DmitryRybin1) reported

    @MangQiuyang I really love BrokenArxiv and similar broken github repos benchmarks: task generation is automatic, real-time, and simple And yet the signal (find mistake in a long paper / proof / code) is really high! This must be something fundamentally related to generator - verifier gap

  • carverfomo
    Carver (@carverfomo) reported

    A Chinese livestreamer in Shenzhen makes $15,000 a day on TikTok. His channel is in the top 50 of its category. An AI agent runs it end to end. He posted his setup on Weibo last week. Two vertical TVs playing pre recorded battle footage. Three phones on stands aimed at the TVs. A wide monitor on the right. Shelves stocked with tactical gear behind him. Bro pause at 0:12. Look at the second monitor. The ultrawide on the right. That spreadsheet is not his sales tracker. That is an AI agent's decision log. The agent picks the battle scenes from a Chinese video model. It decides which tactical product to push every 90 seconds. It writes the script the host reads off the third phone. The host is in frame because Chinese livestream commerce law says he has to be. Someone zoomed the spreadsheet. The columns were not product SKUs. They were prompt IDs. Someone matched the timestamps to product push events. Every push lined up. He had let go his entire team in March. Eighteen people. The studio one floor below his apartment used to be theirs. They still rent it. They open a Discord call every night at nine and watch the livestream together. Six months ago a 14 year old in Shenzhen pushed an AI agent to GitHub. Judges said no real world application. 3,100 forks later. The host had been one of them. He took the post down four hours later. Too late. The clip hit Discord. Then Telegram. Then WeChat. He has been in frame at exactly 9 PM every night for 274 nights straight. He sleeps four hours a night. The agent runs while he sleeps. The law only requires him at 9. The original post had 200,000 views. The zoom on the spreadsheet has 2 million. The TVs are still playing battle footage. The agent is still picking products. The studio one floor below is still open at nine. He wanted to show people his five million dollar a year hustle. He accidentally showed them his job had become standing in frame for one hour a night while eighteen people downstairs watched.

  • davidpuplava
    David Puplava (@davidpuplava) reported

    Well, I undid the cancellation, so I still have my GitHub Copilot Pro account. I thought about it a lot, and one core reason for the low quality results might be because my long running session for my app ended up broken so I started a fresh one. After June 1st, my long running session was beyond the maximum context window size. And trying to compact the results wouldn't work. At the very least, I've decided to sleep on it first before making any permanent decisions.

  • VybeCodin
    VybeCoding (@VybeCodin) reported

    Everyone talks about building in public but nobody talks about the boring part. The week where nothing ships. The GitHub issues that sit untouched. The launch post that got 3 likes. That's the actual build process. The wins are just the highlight reel. What's the unglamorous part of your current project right now? Drop it below 👇 #buildinpublic #indiehackers #opensource

  • EXM7777
    Machina (@EXM7777) reported

    you should NEVER install skills from any source... and no, security isn't the main concern here the real issue is that a skill you didn't build is one you don't understand: you pull it off github, load the whole thing into your agent, and 90% of it is dead weight written for someone else's stack so here's the first move: > send the repo to your agent and ask how the skill is actually built > sit down and figure out which parts add leverage to YOUR setup specifically > have it strip the rest and rewrite that core piece so it's light, token efficient, and fits how you already work but the better move is to never start from one skill at all when i need something, say front-end design, i launch a deep research and find every version online (github, X, wherever) then i ask my agent: what do all these have in common, and what's the one smart approach in each worth stealing i take those, add my own angle, and run the same strip-and-tailor process on top now you've got a skill built on a dozen builders' experience... and you understand every line of it

  • jfschwarz
    Jan-Felix (@jfschwarz) reported

    @DevSwayam That GitHub issue is unrelated. #28 just asks Delay's `executeNextTx` to stop swallowing the revert reason of a failed inner tx, a debugging complaint. The exploit stemmed from a bug in an entirely different function (the `moduleOnly` modifier). Your claim is simply false.

  • Zephyr_hg
    Zephyr (@Zephyr_hg) reported

    i tested 9 claude connectors in june 2026. kept: 1. gmail (inbox triage + drafted replies) 2. google calendar (auto meeting prep) 3. slack (thread context + voice-matched replies) 4. github (repo state and pr diffs) deleted: 1. notion (read-only and slow) 2. asana (covered by cowork folder) 3. canva (output not there yet) 4. figma (read-only depth limit) 5. linear (duplicated state) 3-5 connectors picked deliberately wins. every-connector-on loses.

  • alphadegen69
    AlphaDegen (@alphadegen69) reported

    Hello Everyone. Thank u for visiting my profile. please read this pinned post fully. Kindly follow and turn on noti's if u want to recieve alerts for my reviews. it will mean a lot to me. i specialize in reviewing github, code, UI and if the website is matching with any other project. Whenever i post any review or anything i will try to post as many proofs as possible so it becomes simple for you all to verify them becauze these scammers take advantage of the innocence of the traders here becauze they know u all cant verify if it is larp or legit. I am Larp Slayer. if you are a scammer, i am your worst nightmare. My Gurus @imperooterxbt @MidCurveMortal has taught me just one thing, even if the world is against u for exposing these projects, never stop, but the problem i identified was- they all focus on big names, no one wants to eliminate this tumor from the ground so it never becomes big enough to reach them. i really need ur support to make this place more safe and clean.

  • NickSpisak_
    Nick Spisak (@NickSpisak_) reported

    This is so slept on - @mvanhorn's printing press library > Take your favorite API > Fire up claude code > Give the printing press github (link in first comment) as context > tell it to ingest the API > Convert to CLI & Skill... yes it does both Go back to being a lazy engineer with your voice Where am I using it right now? - I own a multi-seven figure Amazon business that does a lot of back office seller central and inventory planning - We use it for Amazon ads management - It has an integration for Meta ( I like the paid ads integration) and used it to write my own custom gohighlevel CLI because @gohighlevel MCP is not full parity and they need to fix that. Until then the API via CLI is great!

  • KTMudak
    KTMudak (@KTMudak) reported

    Collection for people who want to build their own AI tools without starting from scratch There’s a GitHub collection of 100 free open-source projects you can use as a base for AI tools, automations, internal dashboards, parsers, knowledge bases and local replacements for paid services. Inside are: >tools for AI agents > local alternatives to paid SaaS > LLM interfaces > automation tools > data/parsing projects > design/site/component templates > security/privacy stuff > content tools Give the repo to Claude Code, Codex, Cursor, Cowork or another agent and ask: “Explain how this project works, what I can reuse for my task, what I should delete, what needs adapting and how to build a simple version.” That’s the whole edge. You don’t start from a blank screen. You already have structure, logic, code examples and a map of how someone else solved a similar problem. Just check licenses and restrictions. Some need API keys, some have commercial use terms, some are only good as references rather than things you can ship directly Link below

Check Current Status