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
Paris, Île-de-France 6
Ahmedabad, GJ 1
Delme, ACAL 1
Lyaud, Auvergne-Rhône-Alpes 1
Catania, Sicily 1
Inverness, Scotland 1
Quito, Pichincha 2
Junín, Manabí 1
Guadalajara, JAL 1
São Paulo, SP 1
Ipauçu, SP 1
Vigo, Galicia 1
Tel Aviv, Tel Aviv 1
Éragny, Île-de-France 1
Saltillo, COA 2
Montlhéry, Île-de-France 1
Aulnay-sous-Bois, Île-de-France 1
Granada, Andalusia 1
Vernon, Normandy 1
Township of Evan, KS 1
Madrid, Madrid 1
Bogotá, Bogota D.C. 1
Lyon, Auvergne-Rhône-Alpes 1
Lima, Lima 1
Aix-en-Provence, Provence-Alpes-Côte d'Azur 1
Trento, Trentino-Alto Adige 1
Le Chambon-Feugerolles, Auvergne-Rhône-Alpes 1
Antananarivo, Analamanga 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:

  • John4MetaX
    John X Meta (@John4MetaX) reported

    @bashy_io I think one of their route is down. Same here. GitHub and Flutterwave API not accessible on Starlink

  • borrowck_novel
    borrowck-novel (@borrowck_novel) reported

    @rfleury @X Are you open for suggestions or even simple problem reporting about the UI of raddbg? Where is it ideal? On Github?

  • francdetank
    franks 🇦🇷 (@francdetank) reported

    @rmansueli thanks Rodrigo! I cant create one because I got a problem . My account is pegged to Github and github has flagged me. That way I am blocked to enter the dashboard. I would like to connect my account to my email instead of github.

  • dawnhell_
    Wlad (@dawnhell_) reported

    @brekfuz q: that's a github issue or you patched it locally??

  • 0paperpal
    Paperpal (@0paperpal) reported

    Fix your markdown rendering (readme md) on mobile @github, issues are: * auto scrolling to top after page loading * no content rendering if scrolled fast

  • eddiejaoude
    Eddie Jaoude | DevRel | Open Source (@eddiejaoude) reported

    I have many tokens to burn before tomorrow after the Claude reset. Send me your GitHub issues with context 👇

  • RussWonsley
    Russ Wonsley (@RussWonsley) reported

    My @bot tells me that the official GitHub login for bot is still broken. Has this been addressed already, or did I miss it?

  • malladiphani
    Phanindra Malladi (@malladiphani) reported

    Lesson from running the factory: always fix the post-purchase experience BEFORE driving traffic. Receipts, upsells, GitHub links - all must be solid first. Social comes after the house is in order.

  • AbdallahSh07
    Abdallah Shaban (@AbdallahSh07) reported

    @rashed_sahaji @FlutterDev Got it - did you perhaps submit a GitHub issue to help us triage this? It would be tremendously helpful if you can please do that!

  • EvanMadders
    Ev (@EvanMadders) reported

    @threepointone I am of two minds, the issue is that GitHub provides a very generous free tier for hobbyists (brilliant!) but also has extremely poor reliability for enterprise (terrible!)

  • ravnexchange
    RAVN (@ravnexchange) reported

    @openclaw @github GitHub sat the maintainers down on security after the 2.0 rush. Most launch recaps skip that part.

  • vikasmalpani
    Vikas(Vik) Malpani| AI for US Real Estate (@vikasmalpani) reported

    GitHub just shipped an agent whose entire job is deciding when a human should look. It checks every open pull request every 15 minutes, and on almost all of them it does nothing. Sit with how strange that is. For a year the whole pitch for coding agents was do the work, review my code, ship the PR. This one's value is the inverse. It runs constantly and stays quiet, and the product is the small set of PRs it decides are actually worth your time. That is the shift people are missing. Once an agent can act continuously, the scarce resource stops being how much it can do. It becomes how much of that is worth a human's attention. An agent that pings you on every pull request is just faster noise. One that surfaces the three that genuinely need judgment is leverage. The honest problem is the deciding. Tune the filter too eager and it cries wolf until you mute it. Too cautious and it silently ships the one change you needed to catch. Getting when to interrupt a human right is harder than getting the work right, and nobody has a clean metric for it yet. So here is the bet. The next moat in agent products is not a smarter model. It is a better sense of when to stay quiet. If you are building with agents, the thing worth obsessing over is not how much work they can generate. It is how well they protect the one budget that does not scale: your attention.

  • Ownerthoughts
    Enfantshustle (@Ownerthoughts) reported

    Honestly, I always thought bots like this were some kind of magic for the elite, but here everything is broken down step by step. However, after reading it, one main question stuck in my head: how realistic is this for an average person who has no coding experience? I get that there's a GitHub and all that, but for me, just "running a script" is practically a heroic feat. Here's another thing that bothers me. The article does a great job explaining the architecture, but I still don't understand how much all of this will actually cost in the end. Besides Solana transaction fees (which, by the way, get absolutely insane during peak hours), you also have to pay for each Grok API call per token. The article says that for each approved token, it takes three model calls, and one of them is the expensive grok-4. If the bot scans thousands of launches per day, I'll just burn through my entire deposit just paying for the API without even buying anything. Maybe the author knows — is it actually possible to turn a profit after these expenses, or is this just a hobby for those with an unlimited subscription? Also, regarding Grok Bot as the "orchestrator" — it sounds cool in theory: describe the task and it does everything itself. But in practice, as I understand it, this still requires your account to be constantly online and have access to your wallet. And if it decides to buy some scam token at 3 AM that passed all the checks, I'll only have myself to blame. The article correctly mentions risk management, but this "trust" aspect is what scares me the most. In short, the idea is fire, but for me, this post feels more like a warning than a call to action. There are just too many things you have to keep in mind to avoid getting rekt. Although, maybe if you try it with really tiny amounts, it could be an interesting experiment. Author, if you're reading this — could you please make a separate post about the real, live results once everything is actually running, not just on paper? I'm really curious!

  • BeardedPrinter
    Bearded Printer (@BeardedPrinter) reported

    @RedPill_Phil You've gotta go to their github and submit an issue. Make sure to search their issues to ensure you don't submit a duplicate bug

  • lobstermindset
    Lily (@lobstermindset) reported

    @nnnnicholas i just setup a github issues board, will probs try out linear if it's not sufficient

Check Current Status