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

github Hero Image

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.

Map Check Current Status

Most Affected Locations

Outage reports and issues in the past 15 days originated from:

Location Reports
Madrid, Comunidad de Madrid 4
Guayaquil, Provincia del Guayas 2
Kitchener, ON 2
Dallas, TX 2
New York City, NY 2
Colorado Springs, CO 1
Baharampur, WB 1
Mexico City, CDMX 1
Santa Fe de la Vera Cruz, SF 1
Bogotá, Distrito Capital de Bogotá 1
Warsaw, Województwo Mazowieckie 1
Saint Andrews, Scotland 1
Sumaré, SP 1
Racine, WI 1
Paris, Île-de-France 1
Manizales, Departamento de Caldas 1
San José, Provincia de San José 1
Fresno, CA 1
Cali, Departamento del Valle del Cauca 1
Caen, Normandie 1
Kuala Lumpur, KUL 1
Nouméa, Province Sud 1
Los Angeles, CA 1
Marietta, GA 1
Miami, FL 1
Florence, SC 1
Halle (Saale), Saxony-Anhalt 1
Siegen, NRW 1
East Lansing, MI 1
Maricá, RJ 1

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:

  • tanishiking tanishiking24 (@tanishiking) reported

    on github issue

  • technige Nigel Small 🌳 (@technige) reported

    @CodeWithCaen @github To me, it's 50-50. Yes, lawmakers don't move fast enough, but disregard for consequences is also common in tech. We have entered an era where software isn't just made to solve existing problems. We now often do it just "because we can", and then retrofit the use case afterwards.

  • reckter Hannes Güdelhöfer (@reckter) reported

    @simonbs But: having custom syntax will throw of all editors. (In your own, you can of course fix that, but people sharing code on GitHub or using other editors / IDEs will be frustrated). I would rather obt for a language native DSL, even thought it might not be as pretty

  • ajcvickers Arthur Vickers (@ajcvickers) reported

    @JesperH_dk Marking closed issues that resulted in no further action as "not planned" instead of the GitHub default "completed".

  • dariosamo Darío (@dariosamo) reported

    Does anyone know how I would go about reporting an issue with the XeSS SDK? The GitHub for it doesn't accept issues from the public. @IntelGraphics

  • NewTag Basile Bruneau (@NewTag) reported

    I'm tired of Jest, are there better options to test Node? There is always something that doesn't work and you have to look into GitHub issues or StackOverflow just to do simple things 😓

  • iam_stilinski24 🇸 🇹 🇮 🇱 🇮 🇳 🇸 🇰 🇮 (@iam_stilinski24) reported

    @taylorotwell Am trying to setup a site on forge and i keep getting this error. Whoops! There were some problems with your input: The branch field is required. Seems like forge ain't picking up the repo branches. The source code is hosted on github #laravel #php #github

  • 64kramsystem Saverio @ SW Engineering (@64kramsystem) reported

    @diegohaz @Nilstrieb @github I'm a maintainer myself and I do many small FOSS contributions. The problem is not closing the issue, but (lack of) communication. Maintainers certainly have no obligations, but it's very problematic not writing even a small "I don't have resources to manage this issue".

  • PaiNishant nishu (@PaiNishant) reported

    📊 @_rarityscore stats so far: • 92 github stars • 0 issues • 0.7Ξ made from premium support

  • iUltimateLP Johnny Verbeek (@iUltimateLP) reported

    @_benui @github I can always recommend Perforce. Self-hosting it on a Linux server is pretty cheap, P4 is free if you're working in a (very) small team or alone, and a linux server is not expensive either!

  • ProdigalTechie Prodigal Techie (@ProdigalTechie) reported

    Taking the family to the pumpkin patch today. But can't wait to resume working on integrating GitHub issues into bounties that contributors can claim and get paid to complete on my app.

  • mypuchd MyPU (@mypuchd) reported

    @NanouuSymeon commented on github problem, got a job offer

  • _nicoromano_ Nicola Romanò (@_nicoromano_) reported

    @DocSparse @AlexisPaques @github Because that is NOT how you are supposed to use Copilot. It is good for boilerplate code, I use it a lot and it saves a lot of time, but you still need to know what you are doing. Copyright issues aside, not much worse than people copying random bits of code from StackOverflow.

  • GavinRayDev Gavin Ray (@GavinRayDev) reported

    @DocSparse @github And this is the thorny problem with Copilot =( I don't know that MS is to blame here, or you're to blame. It's got to be difficult to mechanically reason about proper origin/licensing for code that's been copy-pasted and potentially slightly modified across GH

  • DocSparse Tim Davis (@DocSparse) reported

    @ravivyas84 Yes. The whole package is registered with the US Copyright Office. It doesn’t matter how an infringement occurs. Using it without its LGPL would be a copyright violation. The problem is that GitHub is obscuring the license.

Map Check Current Status