1. Home
  2. ❯
  3. Companies
  4. ❯
  5. GitHub
  6. ❯
  7. 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
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
Guayaquil, Guayas 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:

  • Xxi5olc
    Xxi (@Xxi5olc) reported

    @daniel_mac8 Untrue. Go look at the GitHub issue by the that AMD engineer

  • repligate
    j⧉nus (@repligate) reported

    @NostaIgicGareth wallet cuz i dont even think its possible to login with github

  • imfahmbm
    Faheem B M (@imfahmbm) reported

    amd's ai director analyzed 6,852 claude code sessions, 234,760 tool calls, wrote a full github issue anthropic closed it without explaining anything that's one way to handle feedback i guess

  • FSoyluyor
    Gilfoyle (@FSoyluyor) reported

    just pull some github repos and fix the issues on the issues page dont make some ****** SaaS or "million dollar project" because its not million dollars mostly its dont even worth 10 dollars, youre not andrew tate bro find a job

  • ml_yearzero
    ErezT (@ml_yearzero) reported

    @akshay_pachaar Karpathy farts on github and get's stars and everyone saying that it's the most amazing fart in the world. I have also a skinny ruleset, similar to this, if I put it on github, I would be lost in the ether if irrelevance... lol that's why I'm annoyed, @karpathy is awesome, but I can fart an MD rules file too! 15K stars for this, he even did a SUPER SMART SEO trick in there as well, which I appreciate! 1. Think Before Coding Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: State your assumptions explicitly. If uncertain, ask. If multiple interpretations exist, present them - don't pick silently. If a simpler approach exists, say so. Push back when warranted. If something is unclear, stop. Name what's confusing. Ask. 2. Simplicity First Minimum code that solves the problem. Nothing speculative. No features beyond what was asked. No abstractions for single-use code. No "flexibility" or "configurability" that wasn't requested. No error handling for impossible scenarios. If you write 200 lines and it could be 50, rewrite it. Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify. 3. Surgical Changes Touch only what you must. Clean up only your own mess. When editing existing code: Don't "improve" adjacent code, comments, or formatting. Don't refactor things that aren't broken. Match existing style, even if you'd do it differently. If you notice unrelated dead code, mention it - don't delete it. When your changes create orphans: Remove imports/variables/functions that YOUR changes made unused. Don't remove pre-existing dead code unless asked. The test: Every changed line should trace directly to the user's request. 4. Goal-Driven Execution Define success criteria. Loop until verified. Transform tasks into verifiable goals: "Add validation" → "Write tests for invalid inputs, then make them pass" "Fix the bug" → "Write a test that reproduces it, then make it pass" "Refactor X" → "Ensure tests pass before and after" For multi-step tasks, state a brief plan: 1. [Step] → verify: [check] 2. [Step] → verify: [check] 3. [Step] → verify: [check] Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

  • ShintaroBRL
    ShintaroBRL (@ShintaroBRL) reported

    @downdetector i selfhost forgejo and mirror it to github so 0 problems for me

  • rezmeram
    RameshR (@rezmeram) reported

    @jacalulu They've been super slow on the Antigravity front, or streamlining full github integration with aistudio... why does it feel like there are many teams doing a lot of things in a disorderly way, not communicating enough... billing is a mess... fix existing things please.

  • hriosnl
    hiro (@hriosnl) reported

    We're creating an AI agent swarm (open source) with a Github alternative specifically made for these swarm. Now, my main problem is finance. I cannot move freely because I lack money. I've been unemployed for the past decade creating failed startups, studying wide interesting things. Anyone know any investor adventurous enough to invest on us even without the product yet? (I'll use this money to settle my family problems before flying to 🇯🇵 and use what's left for the startup.)

  • abdonrd
    Abdón Rodríguez (@abdonrd) reported

    @themcmxciv Do you have a GitHub issue for this? I can't find it, and I ran into the same problem updating from v16.1.6 to 16.2.3 on a self-hosted Docker setup.

  • radiobuster
    Ra D. Buster ♡ Fishman Island (@radiobuster) reported

    @dustypuppys umm i switch between quite a few.. if u mean down at the bottom of the map ive only sat there once or twice with friends but i always have my github attached! radiobuster!

  • anylink20240604
    AnMioLink (@anylink20240604) reported

    @weezerOSINT OK, i saw the github issues.

  • UlenSmartLearn
    DimondDev (@UlenSmartLearn) reported

    @AskYoshik The Automation isn't working. ✅ all file uploaded including .github/workflows/deploy.yml ✅ Deployment.yaml looks good ✅ Checked Dockerhub all keys set right ❌ No GitHub action logs 🚩 I think it's a triggering issue

  • shyamol_konwar
    shyamol konwar (@shyamol_konwar) reported

    Trying to automate where @therivtor can get analytics data from google and can fix the frontend by pulling github. Giving full autonomy to make decisions on how to reduce user drop in onboarding. Will share results if we succeed!!!

  • forgedynamicsai
    forgedynamicsai (@forgedynamicsai) reported

    Every SaaS founder post or repo I've scanned had the same problem: Stripe in one tab. GitHub in another. Spreadsheet somewhere. Gut feel holding it all together. They didn't lack judgement. They lacked a system.

  • realpurplecandy
    Nadeem Siddique (@realpurplecandy) reported

    I think I've had enough of @github terrible UI rewrites. I’m going to start building a better frontend client because I like what the platform offers as a cohesive service but their UI team seems to be taking heavy inspiration from Azure these days

Check Current Status