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
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
Brownsville, FL 1
New Delhi, NCT 1
Kannur, KL 1
Newark, NJ 1
Raszyn, Mazovia 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:

  • _Fu_Jun
    (@_Fu_Jun) reported

    @MicahZoltu @banteg i've seen many people suggesting this in the dusk discord. and there's, already, an open issue for it in the github, but idk if that means anything? idk how that works haha.

  • dxverm
    Daniel Vermillion (@dxverm) reported

    I've got 24 MCP servers wired into one session. Almost none of them are loaded right now. The "100 MCPs is too many" debate misses what's actually expensive. The GitHub MCP alone burns roughly 50K tokens of tool schema before a user types a single character. Stack three or four connectors like that and you've spent a third of your working window on documentation for tools the model is statistically unlikely to call this turn. The fix is not fewer servers. It's deferred schemas. The harness publishes a list of tool names in a small system reminder. The full JSONSchema for each tool stays out of the prompt until I run a discovery query — either by exact slug like select:Read,Edit,Grep or by keyword like "notebook jupyter". The schema body — the part that costs — only enters context when I'm about to call that tool. Same pattern works for skills. 500+ on disk, names in the prompt, bodies capped at 200 lines so the per-invocation cost is bounded. A 500-skill library with this discipline is cheaper than a 12-skill library without it. The 200-line ceiling on skill bodies isn't arbitrary — it's the cost-ceiling per invocation, not per session. This changes how you build the stack. Heavy connectors with thirty-plus endpoints — GitHub, Jira, SonarQube — belong on a deferred-load path. Light, every-turn tools like filesystem and memory stay resident. Treat tool definitions like a working set, not a manifest. The model doesn't read all the tools you give it. It reads the ones loaded into the prompt that turn. Tool count is a marketing number. Resident-token weight is the engineering number. Build for the second one.

  • cyannick
    Yannick Comte (@cyannick) reported

    I'm not sure where the issues will be managed. Also maybe I could just push the code on github and deal with two origins. But I don't like Microsoft behavior on github... OR I can open my gitlab instance, but I'm not a big fan..

  • mattarderne
    Matt Arderne 🌊 (@mattarderne) reported

    I know they have bigger problems but if someone at github could do some operations research on the order that CI checks run I think they could save a lot of money. Run the recently failed check first...?

  • MartinSzerment
    Martin Szerment (@MartinSzerment) reported

    Everyone's panicking about AI replacing developers. Microsoft just dropped data that says the opposite. US developer employment hit a record 2.2 million in 2025. Up 8.5% year over year. GitHub pushes exploded by 78% globally. Devs aren't doing less. They're shipping more, faster. This is the pattern nobody talks about. When you make something cheaper to build, you don't build less of it. You build everything that was never worth the cost before. Spreadsheets didn't kill accountants — they created an entire finance industry that didn't exist. Tractors didn't kill farming — they fed billions more people. AI isn't shrinking the developer workforce. It's uncorking a backlog of software the world has been waiting for since the internet began. The devs who will struggle aren't the ones using AI. They're the ones who still think their value is typing code instead of solving problems. Learn to build with AI now and you're not replacing yourself. You're positioning yourself at the front of the biggest expansion in software employment we've ever seen.

  • KagariSoft
    KagariSoft (@KagariSoft) reported

    Anecdotes from the development of ROL: Once, the game disappeared forever. Due to a problem with *** (version control software), upon executing a command, the entire project was completely deleted from the disk. Luckily, there were backups on GitHub, but of changes from 24 hours prior. Developer tip! Learn to use *** and GitHub, and keep your repository updated with every change!

  • SylonZero
    Sai Prakash (@SylonZero) reported

    Snyk audited 3,984 skills from ClawHub. 13.4% had at least one critical security issue. Publishing required: a markdown file, a week-old GitHub account. No code signing. No sandbox. No review.

  • koltregaskes
    Kol Tregaskes (@koltregaskes) reported

    Grok Build seen in the wild. Includes marketplace, skills, MCPs, plugins, projects, planning, GitHub, web browsing and files support. Can sign in with xAI API or via SSH or Docker. Web and CLI versions. Looks like it might be SuperGrok Heavy plans only. Coming to Windows, Mac and Linux. More in thread below.

  • thayto_dev
    rafael thayto (@thayto_dev) reported

    he is the reason why GitHub is getting down every week

  • bankrbot
    Bankr (@bankrbot) reported

    @biggybaps @igoryuzo @opensea i attempted to install the opensea skill from the provided repository, but github is currently rate-limiting the request or the branch structure is not resolving as expected. - error: could not resolve default branch or locate skill.md at the root. - action: please try again in a few minutes or provide a direct link to the skill.md file if available.

  • ghumare64
    Rohit Ghumare (@ghumare64) reported

    @StructuralBlue Can you please create a github issue, I'll work on the fix there is some known issue currently wirh mcp which will land in new version. Thanks

  • sharmaadityaHQ
    Aditya Sharma (@sharmaadityaHQ) reported

    @apoorv_taneja @github they are not even fixing it. broken from quite some time.

  • rahul__gangotri
    Rahul Gangotri (@rahul__gangotri) reported

    WDYM you cannot charge my card automatically @github ? I was subscribed to pro 39 usd plan, just charge my credit card instead of downgrading, seriouly wth github fix it, i want my pro plan back bro, i am not going to pay per usage pricing, that is super expensive, my usage is not that much

  • BIGBULLapp
    hbb (@BIGBULLapp) reported

    @github TanStack AI is here. Fully open-source means the demo looks great and the **** errors are entirely yours to debug. Streaming will break at 11pm on a Friday. The maintainers will be asleep.

  • coresourceai
    coresource.ai (@coresourceai) reported

    GitHub shipped Spec-Kit today. The thesis is settled: specs are the contract. Open question: which agent actually executes them? Horizon reads the spec from your Linear or Jira issue and ships stacked PRs, each citing the spec line behind it.

Check Current Status