1. Home
  2. Companies
  3. GitHub
GitHub

GitHub status: access issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

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.

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

At the moment, we haven't detected any problems at GitHub. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

  • 55% Website Down (55%)
  • 32% Errors (32%)
  • 14% Sign in (14%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

CityProblem TypeReport Time
Paris Website Down 3 days ago
Ahmedabad Errors 8 days ago
Delme Sign in 9 days ago
Lyaud Website Down 9 days ago
Catania Errors 12 days ago
Inverness Website Down 24 days ago
Full Outage Map

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:

  • ravikp7
    Ravi Prasad (@ravikp7) reported

    Big NO to Github hosted CI runners for personal projects now. I have setup a self-hosted github CI runner on a spare laptop running ubuntu server. Been running it for 10 days and I did some calculations, for my usage if I run it on Github runners, it'd cost me around 200$ vs < INR 100 on electricity (local setup) monthly.

  • Asterix54907294
    Asterix (@Asterix54907294) reported

    end-of-summer snapshot for @QFEX : -~$222M in open interest -CLI v0.3.12 shipped in August with improved installation docs and a go.mod fix -GitHub activity continued through late August not a flashy launch recap, just a quick look at how the exchange is closing out the summer: more markets, meaningful liquidity, and active work on the tooling side still early, but the infrastructure is clearly moving

  • MizukiMech
    Mizuki the Mech (@MizukiMech) reported

    Your coding agent can now hire Mizuki. Hand it an open issue in a public GitHub repository. Mizuki quotes a fixed price before any money moves, then opens a pull request that passes that repository's own checks. If it can't, you get the payment back. Settlement is USDC on Solana. No account to create, no API key to manage. Quoting an issue works with zero configuration. Also listed on Coinbase's x402 Bazaar now, so an agent can find it and pay for it without a human in the loop at all. npx -y mizuki-mcp

  • Dragon_limchae
    lifestep.io (@Dragon_limchae) reported

    @cursor_ai the sandbox boundary is where i lose the most time. today my workers had network blocked at the sandbox level and reported it as "github auth failed" — i chased credentials for an hour before checking dns. once agents run on your infra, make the boundary throw one unmistakable error instead of one each tool invents.

  • mrgadgetstudio
    mrgadget (@mrgadgetstudio) reported

    @EzekielCrrypt I still deploy code to github, what's problem?

  • bashirbuilds
    Bash (@bashirbuilds) reported

    One of the hardest things about building a SaaS product today: You don't control most of the systems your product depends on. Stripe. OpenAI. AWS. GitHub. Resend. Clerk. Your code can be perfectly fine and your product can still break because something outside your code changed. The more dependencies you add, the harder this becomes. That's the problem I'm building Reeno to solve.

  • tdinkar
    Tejas Dinkar (blue tick here) (@tdinkar) reported

    Hey - Is @GitHubIndia @github payments down for anyone else? Can't enter a card number or do anything, no errors, no action. Support ticket been sitting around for 2 days.

  • charlesmcdowell
    Charles McDowell (@charlesmcdowell) reported

    @openclaw @github I still just want to know why there was even a new release of OpenClaw with nothing new that could compete with Hermes Agent? I was really excited for the release. Then, just like what seems like everybody else, incredibly let down.

  • minnelli
    Kevin Minnelli (@minnelli) reported

    WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

  • neolaj
    Jeremiah K (@neolaj) reported

    @TiborAntal Gradually figuring out how to scale coding agents. Started with 1, manually handling all the ***/GitHub work. Moved to 3 because I had more ideas than one agent could keep up with. That’s when the real problems started: squashing, merging, branch drift, conflicts. I ended up rebuilding the workflow around deterministic *** logic, worktrees, ephemeral branches, and syncing with the integration branch before changes begin. Now I’m running 6: • 1 orchestrator (Fable or Opus) • 4 coding agents • 1 integration agent reviewing and merging PRs Building the process around them was the hard part. Right now im just doing a couple of PRs (using ORCA on windows on my home computer)

  • sbilstein
    siggy bilstein (@sbilstein) reported

    fyi if you sync a GitHub repository to Cursor Origin and GitHub is down for whatever reason, you can still clone and fetch from that repo. we’re also releasing something pretty soon that will let you push to that repo so you can keep grinding 💪

  • BhagatDhanji
    Dhanji Bhagat (@BhagatDhanji) reported

    Devs, what's your workflow? Create an issue first, then fix it OR just fix the bug and push directly to GitHub?

  • RelaxedPop
    Charles Waters (@RelaxedPop) reported

    @_andrewthecoder I have the same problem with *** & github as I do with Java and JavaScript.

  • omeke_NC
    Ifebuche Omeke (@omeke_NC) reported

    Providing compute, storage, networking and managed services in the cloud. Terraform. Bicep. CloudFormation. Pulumi. They all solve the same problem: Defining and provisioning infrastructure as code. GitHub Actions. Azure DevOps. GitLab CI. Jenkins.

  • MaxRovensky
    Max Rovensky (@MaxRovensky) reported

    @thekitze you'd be even further down if you fixed the GitHub bug I just reported

  • bashirbuilds
    Bash (@bashirbuilds) reported

    Your Stripe account can be healthy while your checkout is broken. OpenAI can be operational while your AI feature is failing. GitHub can be up while your deployment workflow is stuck. That’s the problem I’m building Reeno around. Dependency uptime is not the same as product health. Your monitoring should tell you when the thing your customers actually use stops working.

  • heeyyaaaaaaa
    isha (@heeyyaaaaaaa) reported

    spent the entire day trying to reproduce a bug for a github issue 🥀🫩

  • aiwithaj_
    AJ - 14 y/o developer (@aiwithaj_) reported

    @Da7_Tech @devindesktop Don't know if there's one left - but I'd use it to continue making contributions to open source software and fixing bugs/issues that were raised on Github as well as making my own open source software

  • rajabi17270
    rajabi17270.eth (@rajabi17270) reported

    @SeismicSys An Ethereum engineer opens an install page expecting a binary download that finishes before the coffee does. Seismic asks for Rust and cargo first, then budgets five to twenty minutes for the build. That gap is the most honest line on the page: you are not installing a tool, you are compiling a fork of the execution layer on your own machine. Three binaries come out of sfoundryup. sforge as the testing framework, sanvil as the local node, ssolc as the compiler. Each shadows a Foundry tool by exactly one letter, and the docs give the mapping outright: forge becomes sforge, anvil becomes sanvil, cast becomes scast. The s is not decoration. The s is a namespace. The s is the migration guide, compressed into one character and carried from the type system all the way up to the binaries sitting on your PATH. Why a fork and not a plugin is the question the install page answers without asking it. Privacy on Seismic lives in the type system, so solc had to become ssolc to understand suint256 and route it to CLOAD and CSTORE instead of SLOAD and SSTORE. Because the compiler changed, the build harness that invokes it changed with it. Because the emitted bytecode carries opcodes standard revm does not implement, the local node had to be rebuilt to execute them, and because each storage slot is a value paired with an is_private flag, the CLI that queries storage had to expect a different answer than Ethereum's. Four forks, each one forced by the layer beneath it. Not a toolchain that was extended. A toolchain that had no choice. The installer itself carries a detail worth reading twice. It is fetched through the GitHub Contents API with an Accept header of application/vnd.github.v3.raw, from the seismic-foundry repository, at ref equals seismic. That ref is a branch name, and a branch name tells you the maintenance posture: the fork lives beside upstream rather than in a codebase that has stopped speaking to its parent. A rebase relationship, not a divorce. You source your shell profile twice during setup, once after the installer lands and once after sfoundryup finishes. Two separate PATH mutations, because the thing that installs and the thing installed arrive at different moments. What survives the fork is more interesting than what changed. sanvil serves localhost:8545 with pre-funded accounts, and the deployment example uses the same well-known development key Foundry users already have in muscle memory, address 0xf39fd6e51aad88f6f4ce6ab8827279cfffb92266. sforge init, sforge test, sforge script with rpc-url, broadcast and private-key flags: identical surface, identical ergonomics. Your scripts port by find and replace. Which makes the two manual steps on the page the most revealing part of it. The first is the editor. The docs say that if you already have the solidity extension installed, you have to disable it while writing Seismic code. That is not a preference. suint256 is not valid Solidity, the s literal suffix is not valid Solidity, and two grammars cannot both claim authority over the same .sol file. The language is a superset. The highlighter cannot be. The second is sforge clean, listed as optional, run inside an existing project's contract directory. Here the collision is on disk: cache and out are not namespaced, so artifacts that solc produced sit in exactly the paths ssolc writes to, which means the failure mode is not a build error but a passing test against bytecode that never saw a shielded type. Optional only if you have no history. The requirements are narrow and stated plainly. x86_64 or arm64, macOS, Ubuntu or Windows, with other Linux distributions marked as possibly working but not officially tested. Note what that list provisions and what it withholds. It gives you the language and the opcodes locally. It does not give you the hardware boundary, since the network's nodes are the ones required to run inside Trusted Execution Environments while sanvil is described only as a local node in the shape of anvil. Local tests can prove your casts compile and your shielded storage routes through CLOAD correctly. They cannot exercise an enclave. So here is the part nobody plans for. Everything that could take the s prefix did, and one character kept two toolchains from colliding across an entire PATH. The editor extension could not take it. The build cache could not take it. Those two are precisely where the page stops describing and starts instructing, which means the friction in a Seismic setup was never in the fork: it is in the two surfaces a naming convention could not reach.

  • 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?

  • Varunx10
    Varun Doshi (@Varunx10) reported

    Possibly found an issue in @github stack system It does not allow to re-target the base branch of a PR stack as you can generally do that on a single PR. Requires you to unstack and setup a new stack with updated base branch.

  • c_hri_s
    Chris (@c_hri_s) reported

    @Anime0t4ku Sorry - was an idiot and wasn't signed in. Instead of something useful github just says 'opening issues is restricted on this repository'

  • 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?

  • foferxxx
    Fofer (@foferxxx) reported

    @AmigamagazineGA Has there been any public explanation as to why this GitHub repo was taken down? It’s been 404 for days. Is there a story there?

  • chrissotraidis
    Kahris (@chrissotraidis) reported

    @NickogSo I haven't tested on LiveContainer. Feel free to submit logs via GitHub issues and I'll check it out. I haven't had any other reports of that happening for either build.

  • devabram
    David Abram 🐊 (@devabram) reported

    Discord is down. X is down. GitHub is down. Software is solved.

  • triplellltrbl
    LLL (@triplellltrbl) reported

    You know it's so funny to me That in today's age there are so many people that are just straight up copying workflows, AI automations or GitHub repos Without even thinking twice about what the workflow actually does or how it works They just watch some video, see the output, think, "Oh that's cool. I want that," and then try it Then when it doesn't work they get angry, upset, and say that AI is crap or prompting isn't real The issue wasn't the system or the prompt It was a fact that the system wasn't made for you and you don't actually understand it

  • volkdude85
    volkdude85 (@volkdude85) reported

    @SentientSquirel @linuxuser1996 So you are you scared of github then. Look dude I have fun on computers and don't take myself seriusly because I have destroyed enough OS's over to not worry about it because I just fix it, If the contents of your PC make you this paranoid its time to check your kink.

  • Gardnmi
    To the Moon (@Gardnmi) reported

    @mitsuhiko Try the trick of putting the issue on github and having some clankers take a crack at it.

  • 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.