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
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
Trichūr, KL 1
Departamento de Capital, MZ 1
Chão de Cevada, Faro 1
New York City, NY 1
León de los Aldama, GUA 1
Quito, Pichincha 1
Belfast, Northern Ireland 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:

  • _golie_
    Goli (@_golie_) reported

    @github is constantly down what are engineering teams using instead?

  • stylewarning
    '(Robert Smith) (@stylewarning) reported

    I put a bounty on a Coalton issue (add syntax highlighting support in another non-Coalton project) and in less than 5 hours some unknown people started pushing AI-generated PRs to this other project. Makes Coalton look bad. Never thought I'd need to actually moderate on GitHub.

  • SilvaniKillian
    SilvaniScream ⚙️ Cyber⚡️Speedster (@SilvaniKillian) reported

    @skytaleSythe @vxunderground With how much microslop keeps pushing Copilot into Github and whatnot I’m surprised they don’t have a “ClaudeCode” equivalent that’s just neutered for the average joe shmoe. That seems like a fix to this bullshit, if another microsloppy “fix”.

  • igorbenic
    Igor Benić (@igorbenic) reported

    @beginbot We need a song when GitHub is down.

  • matisanengineer
    Mat (@matisanengineer) reported

    The loudest people shitting on GitHub are usually the ones who’ve never had to build or operate software at that kind of scale. Everything looks like a simple fix until you’re the one dealing with the complexity.

  • szabta89
    Tamás Szabó (@szabta89) reported

    Repo Mind Light indexes issues and PRs, pulls code context live from GitHub Code Search, and uses the novel GraphRAG Zero from Microsoft Research under the hood. The system is proprietary because of GRZ, but the Docker image is public.

  • ngriffin_uk
    Nicholas Griffin (@ngriffin_uk) reported

    @elbruno i mean yeah but im not sure anyone cares about how much scale github has outside of shareholders / stakeholders. and when this has been months on months of issues, people really are at the edge. even aws codecommit is looking decent now.

  • dovvokun
    dovvokun (@dovvokun) reported

    @matisanengineer GitHub is a product Dev's are using, and due to its constant problem it's causing an issue. Why can't they **** about the product that is not working optimally. Microvave was anology.

  • seshasainikhil
    Nikhil Kondapalli (@seshasainikhil) reported

    @github The issue is now resolved!

  • iainherd
    Iain Herd (@iainherd) reported

    I’m currently through trial and error, have ended up using GitHub for the use case you describe - structured agent context data (prompt, files, knowledge base) are too important to allow agents unilateral YOLO. GitHub provides fine grained control and central source of truth. Really interested in understanding how your solution supersedes this?

  • tetsuoai
    tetsuo (@tetsuoai) reported

    mit researchers wrapped gpt-5-mini in an rlm and it beat gpt-5 by 28.4% on long-context tasks, scaling to 10m+ tokens the mechanism: don't feed the prompt to the model. hand it to a python repl long context is a programming problem arxiv: recursive language models github: alexzhang13/rlm

  • seanboisselle
    boisselle (@seanboisselle) reported

    @mitchellh Doom scrolling GitHub issues is next-level cracked, bravo...

  • 1PercentBetterT
    1PercentBetterToday (@1PercentBetterT) reported

    Finally got the MM strategy running on #EVPOLY for #Polymarket sports bets. ngl, burned hours on this. Web app wouldn't execute. GitHub Linux version threw errors. Thought it was broken. Turns out? A settings filter was blocking orders the entire time. One tweak → it works. Now racing the clock — 500K bonus rewards expire at 9PM tonight. Let's see what 12hrs of runtime can do.

  • polydao
    Mr. Buzzoni (@polydao) reported

    Nobody is teaching this in college. So here it is > full guide: how to go from broke student with no experience to landing your first AI freelance client - using only free tools, in under 30 days YOUR FREE STACK > Claude Code - free tier > VS Code - free > GitHub - free > total cost: $0 don't buy anything yet STEP 1. pick one small useful thing to build not a portfolio. not a "brand" one thing that saves someone real time ideas that actually sell: > script that pulls job listings by keyword and sends a daily email > tool that auto-generates invoices from a spreadsheet > bot that monitors a webpage for changes and alerts you > script that turns raw notes into a formatted report small. specific. one real problem STEP 2. build it. break it. rebuild it don't watch tutorials for a week before starting open Claude Code. describe what you want to build. just start when it breaks - read the output. understand why when it works - change something. see what happens give it 3-5 days of real focus this is how you actually learn STEP 3. put it on GitHub like a pro write a README that answers: > what problem does this solve > how does it work > how do I run it this is your resume now a working project beats a GPA every time STEP 4. find your first client (the honest version) don't go to Upwork and bid $5/hour > find 10 small local businesses - restaurant, dentist, gym > spot one obvious problem they have (manual reports, no follow-up emails) > email or DM them on LinkedIn > say: "I built a tool that does X. I can do the same for you" > charge $100-300 for the first one > ask for a testimonial when done first client won't pay rent but they'll give you proof you're real that's what matters at the start STEP 5. repeat. raise prices client 2: $300-500 client 3: $500-800 3 projects + 2 testimonials = you're not a beginner anymore what to expect, honestly: week 1-2: confusing. normal week 3-4: first working project month 2: first real client conversation month 3: first dollar month 6: $500-2,000/month if you stay consistent what NOT to do: > don't buy a course before trying the free tools > don't try to learn everything at once > don't wait until you feel ready > don't underprice yourself forever the tools are free. the article is linked 🔖 bookmark this. open it today

  • nx_winnr
    nx / winnr (@nx_winnr) reported

    did @github went down again? this is getting annoying now.

Check Current Status