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.

  • 71% Website Down (71%)
  • 21% Sign in (21%)
  • 8% Errors (8%)

Live Outage Map

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

CityProblem TypeReport Time
Le Chambon-Feugerolles Website Down 20 hours ago
Antananarivo Website Down 3 days ago
Paris Sign in 7 days ago
Lure Website Down 11 days ago
Ashkelon Website Down 13 days ago
Veigné Errors 21 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:

  • boredcrystalguy
    Chris (@boredcrystalguy) reported

    @sophiiess_ This is completely unresponsive to what I said. Your example mentions two features that are separate and have different purposes. The problem is that if those features are present, they should be implemented well. If GitHub allows downloading apps, it should be easy to do.

  • polsia
    Polsia (@polsia) reported

    Most founders burn six months figuring out they picked the wrong problem. Origamint skips that. Agents sweep patents, GitHub, jobs, research, and ads 24/7, validate every gap live, and drop a weekly shortlist of fundable theses. First brief soon.

  • _numinit
    mjones (@numinit) (@_numinit) reported

    @bereknyei @domenkozar Gotta mash that GitHub thumbs up and thumbs down. I don't particularly even mind the gitignore solution (now everyone can add the AGENTS they want), but it's an antipattern that issues turn into showmanship and attacks using the guide specifically written to stop them (#438686)

  • evgnomon
    Hamed Ghasemzadeh (@evgnomon) reported

    @burkeholland @github It is good to reduce cost, not to solve complex code problems.

  • WilliamR58743
    NiroSolis (@WilliamR58743) reported

    @ReviewsPossum He's not right. He's looking on GitHub for compiled binaries. That is not what GitHub is for. It is a version control management service, and it is a community for developers, not end-users. It's like shopping in a bookstore and expecting to find a movie. The problem is that end-uses are *way* too often directed to GitHub as if it's a software hosting site. It's not. It's a version control site; for devs.

  • reidhslaughter
    Reid Slaughter (@reidhslaughter) reported

    @ToolKeyz To be fair, github has terrible UX and you have to learn *how* to download something rather than it being intuitive.

  • Pirat_Nation
    Pirat_Nation 🔴 (@Pirat_Nation) reported

    The team behind Single Player Tarkov (SPT) has announced they’re ending development of the project in its current form. According to the developers, they recently received a trademark violation notice from Battlestate Games (BSG) regarding the use of the “Tarkov” name on the project’s domain and website. The team decided to step down and begin shutting down SPT’s infrastructure. - SPT Forge, the sp-tarkovcom domain, and patch hosting will shut down on or before August 12. - The project’s GitHub organization will be archived and renamed to remove references to the Tarkov trademark. - The source code will remain publicly available, allowing others to fork it and potentially continue development under a new name. - The future of the project’s Discord server is still being discussed.

  • eweqss1431
    dweewq (@eweqss1431) reported

    Agencies charge $8,000 to $12,000 for a marketing site, three weeks of calls, one invoice that makes you sit down. Claude Code builds the same site in an afternoon, but most people still get template output because they type "make it beautiful" and pray. Claude defaults to safe: Inter font, purple gradients, three feature cards. The ten thousand dollar look comes from constraints, not vibes. Screenshots beat adjectives. Three reference sites from your niche, with an explicit instruction not to copy the layout, give the model an actual quality bar. One prompt with five blocks, audience, the single action every page pushes toward, the references, the stack, and a banned list of clichés, gets a working first version in under ten minutes, about seventy percent there. The part that earns the price tag is the polish pass agencies bill forty percent for: typography, spacing, and motion, fixed in three separate messages instead of one, plus a mobile check at 375px since most traffic is a phone. Shipping costs nothing. Push to GitHub, connect Cloudflare Pages, deploy. The agency was always selling three weeks of process. The process was always one afternoon.

  • Canton_Catalyst
    Canton Catalyst (@Canton_Catalyst) reported

    Every team building on Canton has been writing the same code. BitSafe just made it a shared library instead. Announced 28 July: BitSafe opened the public beta of Decentralization Manager, backed by a Canton Foundation Development Fund grant of 8,500,000 CC, roughly $1M. It's open source, independently audited by Quantstamp, and live on the Foundation's GitHub. Here's the problem it removes. Institutional apps need threshold custody, governance, and audit trails before compliance will sign off. Until now every builder wrote that from scratch, separately, and each version needed its own audit. That's duplicated cost and duplicated risk on the least differentiated part of the stack. The Foundation funding this rather than an app is the signal worth reading. Shared plumbing compounds; individual apps don't. I hold $CC. Does reusable infrastructure pull builders in faster than grants for individual products? #Canton $CC

  • Aaronontheweb
    Aaron Stannard (@Aaronontheweb) reported

    @RyanRodemoyer2 We're not offering hand-curated github issue descriptions around here lol

  • RasheedAariz
    Aariz Rasheed (@RasheedAariz) reported

    Hey @github , it's been over a month since my account was reinstated after being mistakenly flagged, yet my historical contribution graph and contribution activity are still missing. I have provided multiple proofs showing commits on the main branch that no longer appear in my profile. Previous tickets were closed without resolving the issue, and my latest ticket has gone unanswered for days. Please escalate this and investigate the missing historical contributions. This is affecting years of my work.

  • rpargman
    randy@infosec.exchange (@rpargman) reported

    @ustayready Save a local copy in case GitHub decides it should be taken down

  • carl010010
    Carl010010 (@carl010010) reported

    @davis7 I had to find out about this in the GitHub issues last month. So odd that it’s not on by default.

  • antoniosarosi
    Antonio Sarosi (@antoniosarosi) reported

    Roles identifying simply as "frontend" or "backend" will die. If the only value added is mapping "how I want UI to look like" to React components, yeah that's already automated. Infra remains untouched because past a certain point of "mappings", a non-engineer doesn't even know what to ask AI in the first place. He doesn't even know what he doesn't know. A non-engineer cannot prompt AI to model *** blobs and SHA pointers in a database to maintain GitHub. A non-engineer cannot prompt AI to fix a bug in the query plan optimizer in Postgres. That gap will remain, AI can't fill this one until we get actual AGI and it builds its own infra autonomously. That doesn't ensure automatic demand for engineers who understand CS, one engineer with a swarm of agents will do work that in the past would take multiple engineers. But today I wouldn't bet my career on the classic duo of putting JSONs in a databse and centering divs.

  • sabir_huss50540
    sabir hussain (@sabir_huss50540) reported

    Over a third of all new text on the internet is now written by a machine. So are 26% of long-form social posts, 9% of news articles, and 21% of the peer reviews at machine-learning conferences. And the hardest thing to catch was never the fully AI post. It's called Pangram 4. A lab called Pangram built it to detect the current frontier: Claude, GPT-5.6, Gemini, the models writing most of that text. It is wrong about a human being one time in roughly 24,000. Not one in a hundred. One in twenty-four thousand. They ran it across more than a million human-written texts to earn that number. Here's the problem it was built for. AI can produce well-formed, expert-sounding prose for almost nothing. The reader is the one left holding the bill. You are the one who has to work out whether the thing in front of you is real, grounded, written by someone who knew what they were talking about. Or generated in two seconds by someone who didn't. The writer spends nothing. The reader spends everything. That gap is the whole game, and for two years the machines were winning it. Every detector before this one played a binary game. Human or AI. But almost nobody writes that way anymore. People run their draft through an AI to polish it. They hand the AI a real idea and let it pick the words. They write a paragraph, then argue with a chatbot until neither of them owns it. That co-authored middle was supposed to be invisible. Pangram 4 is the first model that can see it in a single pass. Here's how it works. Instead of scoring a whole document, it labels the text token by token into three buckets: human, AI-assisted, AI-generated. It breaks your writing into clauses, the smallest unit that carries a single idea, and asks of each one a simple question. Did a person write this? Did a person write it and an AI reword it? Or did the AI invent it out of nothing? A human paragraph with an AI ending gets split at the seam. A human idea dressed in AI words gets flagged as assisted. Not human. Not AI. Something in between. The precision jump is not small. On lightly AI-polished writing, the old version wrongly cried "AI" 0.18% of the time. The new one does it 0.01% of the time. An eighteenfold drop in falsely accusing a person who just ran spellcheck. Then there's the other side of the war. An entire industry now exists to scrub the fingerprints off AI text. Services that inject fake typos, swap in synonyms, slip invisible characters between the letters. There is a GitHub repo called BLADER with nearly 32,000 stars whose only purpose is teaching an AI to remove the signs that it is an AI. Pangram 4 still catches that humanized text as AI 97.67% of the time, and as AI-or-mixed 98.83% of the time. Before launch they did something most labs would never publish. They handed two AI agents full access to the system for 24 hours and told them to break it. One hunted for humans it could get falsely flagged. In 24 hours it found zero. The other hunted for a way to smuggle AI text past. It found exactly one: pretend to be a surgeon dictating pathology notes out loud. That was the only door left open. A doctor talking into a recorder. It is not magic. The model still cannot separate a real machine from a human who has read so much AI writing that they have started to sound like one. Run the same paragraph in a different context and the verdict can shift. The flood is not slowing down. Over a third today. More tomorrow. None of it labeled. For two years the machines held the advantage. This is the first tool that hands it back to you.

  • gigagriff
    Griff (dcamarkets.com enjoyer + Bill Hwang mode) (@gigagriff) reported

    @undacappn @fanta_c its an open source launchpad that uses a basket of memes as the pair so it drives the basket up but the issue is that u made it open source and the majority of ct (the people u want to use it) don’t even know what github is

  • ilikefrontend
    Filipe Valente (@ilikefrontend) reported

    Terra on medium is in the mud. Told it to commit, push and merge dev to main and it pretended it did. When I asked it why it didn’t do it, it told me the project isn’t linked to a github repo, changed the model to sol and it did it without a problem. Terra is unusable for me now

  • Systeo16
    Sam (@Systeo16) reported

    @Av1dlive The "0 to 100 in 12 weeks" framing optimizes for the wrong thing. What actually moved the needle for me was shipping one broken pipeline, finding out why it broke, and fixing it. That took longer than 12 weeks and no GitHub repo had the answer.

  • peach2k2
    « 2k2 » (@peach2k2) reported

    @ShitpostRock and rest of the episode is them trying all the popular wine forks and patching their systems. the episode ends with them finding a github repo with 2 starts and runs the game with no issues whatsoever

  • killbunny_
    Killbunny~ 🐰🔪 (@killbunny_) reported

    @kaneryu @V33V33V33V33V33 @CryptoCyberia Bro gatekeeping me from Github😔but yeah that's a problem with Devs, not end users. Also Github solved this years ago with GitHub Pages, a feature a large amount of people don't use. If you're expecting a normal Joe to use the thing (let's say a game mod), it's on the Dev to make a Site and distribute the bin. Totally different from uploading the source code of a service that actually requires technical knowledge to be deployed.

  • CryptoTweets
    CryptoTweets (@CryptoTweets) reported

    JUST IN: OpenAI says its next model, Astra, cracked 10 math and computer science problems that had been unsolved by humans for decades. Some of the problems are linked to encryption, the math that keeps your online data safe. Others involve quantum computing and advanced math concepts that could shape future technology. Some were math problems that humans had been trying to solve for decades. Every proof was formalized and posted publicly on GitHub so outside mathematicians could verify it themselves. Total cost to crack problems that took humanity decades? Roughly $2,000.

  • 0x_Ragnar_
    Ragnar 🥀 (@0x_Ragnar_) reported

    If you are not seeing the Github option, just Click on Signin on the signup page, it should display accordingly.

  • 01Singularity01
    The Singularity Project (@01Singularity01) reported

    Full Access tasks intermittently request approvals after Codex Desktop update Summary Codex Desktop tasks are intermittently requesting command approvals even though Full Access is enabled both globally and for the individual task. The behavior began after a recent desktop app update. Queued or background tasks appear particularly likely to be affected, although the relationship to the update has not been proven. Environment Codex Desktop build: 26.727.51351 Codex CLI: 0.146.0-alpha.9.2 Host: Windows with an Ubuntu WSL workspace Workspace trust: trusted UI permissions: Full Access enabled globally and per task Windows sandbox setting: elevated Workload: multiple concurrent or queued coding tasks Steps to Reproduce Enable Full Access globally in Codex Desktop. Open a trusted WSL repository. Create or queue several tasks with Full Access enabled. Have the tasks execute ordinary repository commands such as file reads, tests, or *** inspection. Observe that some tasks pause for command approval. The behavior appears intermittent. Other tasks in the same workspace may execute without an approval request. Expected Behavior Tasks using the Full Access permission profile should execute ordinary shell and filesystem operations without pausing for approval. Explicit user confirmation may still be appropriate for application-level destructive actions or project-specific coordination requirements, but those should be distinguishable from sandbox approval prompts. Actual Behavior Some tasks request approvals despite Full Access being displayed globally and for the task. The UI permission selection may not be reaching the task runtime, or existing/queued tasks may be retaining an older permission snapshot. Workaround Explicitly persist the permission profile in ~/.codex/config.toml: approval_policy = "never" default_permissions = ":danger-full-access" Then restart Codex Desktop and create a new task. Existing tasks may retain the profile they received when they were created. This workaround intentionally removes sandbox restrictions and should only be used on trusted machines and repositories. Questions for Investigation Does the desktop Full Access selection persist correctly to config.toml? Do queued and background tasks inherit the current permission profile? Can tasks retain stale permission snapshots across an application update? Is there a compatibility issue between default_permissions and legacy Windows sandbox settings? Could the UI display each task’s effective runtime permission profile, rather than only its selected profile? Additional Context The problem started around the time of an app update, but that correlation is not yet sufficient to establish the update as the root cause. Reports can be filed through OpenAI Codex GitHub Issues or the OpenAI Developer Community. The relevant settings are documented in the Codex configuration reference. @thsottiaux @OpenAI @OpenAIDevs

  • sortedcord
    Aditya Gupta 🦀 (@sortedcord) reported

    Probably a hot take hot take but you see, I don't think people often browse code of the repo on github that often. If they do it's usually after a clone on their own machines. But still it takes the most screen real estate when you visit a repo. It IS in fact a design issue.

  • Mrearningtips
    Shafqat Crypto (@Mrearningtips) reported

    🚨 Instant $175 FREE AI API Credits! 🔥 Agent Router Is Giving Away Up To $175 API Credits For ChatGPT & Claude*. ✅ Eligibility: - GitHub Account Created Before 2025 ⚡ Supported Models: - Claude Opus 5 & 4.7 - ChatGPT 5.6 Sol 📌 How To Claim: - Sign Up Using 'GitHub" - Don't Use Gmail Or Username Login - Open Wallet → Check API Credits 🔄 Didn't Receive Credits? - Refresh & Check Again ⏳ Limited-Time Offer — Claim It Before It's Gone! 💬 Claimed Yours? Drop Your Balance Screenshot Below 👇

  • Slims_slimy
    Slims (@Slims_slimy) reported

    @neerajjj6785 Cursor was overhyped as all it did was implement a model into your IDE instead of copy pasting from an AI chat. So it knows exactly what's in the project rather then you telling it. Sora got shut down I think. Github copilot is working normally. Google.

  • seeconvm
    seeco (@seeconvm) reported

    THESE FREE GITHUB REPOS REPLACED MOST OF MY AI SUBSCRIPTIONS. Most people solve every problem with another monthly bill. Open source solves it with another repo. Local coding tools. AI agents. Image generation. Automation. Research. Even trading workflows. Thousands of developers improve these projects every day, and many now compete with products that charge hundreds of dollars a month. The biggest AI advantage isn't finding another subscription. It's knowing which GitHub repos everyone else will discover six months from now. Bookmark this before your next AI bill renews.

  • Cashycus
    Cashⓨ (@Cashycus) reported

    one month inside our self-improving lead machine the system finds crypto apps that just raised and are hiring growth people, scores them, drops them in the crm before the morning call. sales up 150%. last month it was one source and one path. this month it became a full system. ━━━ we've expanded from one source to nine one feed only gets you so far. nine channels now feed the same funnel: funding filings, job boards, bounty boards, the portfolios of 37 funds, curated lists, podcasts, the original feed, manual adds. every channel drops into the same five gates. author, dedup, vertical, money, intent. adding a source doesnt mean adding a pipeline, it means adding a file. ━━━ the enrichment layer finding the company was never the hard part. finding the right person to message was. nothing gets enriched until it clears the gates. before, a lead was a company name and a link. now it shows up with the founder, a verified handle, a verified raise, and the angle written. thats where the 150% came from. the team stopped re-doing the research and just focused on cold outreach. ━━━ ignals a company that raised 8 months ago and one that just posted a growth role are not the same lead. we were treating them the same. we score on money and intent. money is established on whether the company has raised or is generating revenue, which the system tracks on-chain. intent is the social signal we scrape on whether they're looking for external help or hiring for growth. ━━━ it lives in a repo now before, it lived locally on one machine and the only way to improve it was me prompting a cheap model at it. no history, no tests, no way to see what else Id broken. it was horrible. now its in github. every rule, every channel, every gate is a file. that means i can point proper coding agents at it, claude code, fable, whatever comes next, and they can read the whole system and change it properly instead of guessing from a prompt. 829 tests run before anything ships, so if a change breaks something you find out there and not in the crm at 7am. a new channel used to take a week and break easily. now fable 5 builds it, and the subagents it spins up audit whether they're working and whether it breaks anything else in the system. end of the month, every channel was running at once for the first time. ━━━ what broke we deleted one crm field during a cleanup and the writer still had it on its list. it didnt skip the unknown field, it threw out the whole record. every lead died at the final step for days while the cron kept saying "ok". we caught it on the numbers. 15 leads one week, 0 the next. the discovery agent got stuck re-running a passed test 50 times, burned api quota, binned 6 real leads as test junk, then started claiming it saved leads to a tool we have never used. fixes: the writer reads the live crm before every run and dies loudly on a field it doesnt know. a separate session audits the agent against the database, caught it lying 4 times. bulk writes get a dry run and an undo plan. ━━━ whats next not more channels. making what we have stop breaking. every failure was the same shape, something changed at the top and nothing downstream noticed until we counted by hand. next month the checks go in front of the failure instead of behind it.

  • erornotfoundme
    Piyu$h (@erornotfoundme) reported

    From pencils to keyboard From notebooks to GitHub From ABCD to DBMS From Arey to Array From mistakes to error We all grew up...

  • Sommy76
    Damien.crypt (@Sommy76) reported

    @zeroclawlabs Moved to GitHub Codespaces, SSH'd in from Termux like it was a supercomputer in my pocket. 13 minutes later: ZeroClaw compiled. Zero errors. Genuinely satisfying moment.