GitHub status: access issues and outage reports

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.

Most Reported Problems

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

• Website Down (58%)
• Errors (30%)
• Sign in (12%)

Live Outage Map

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

City	Problem Type	Report Time
Montataire	Sign in	2 days ago
Colima	Website Down	4 days ago
Poblete	Website Down	5 days ago
Ronda	Website Down	5 days ago
Montataire	Errors	6 days ago
Montataire	Website Down	7 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:

• 
  Hackademy (@hack_ademy) reported 3 minutes ago

  Why Public GitHub Repositories Become Security Nightmares A lot of developers think the danger starts after an application is deployed to the internet. In reality, many breaches begin long before deployment because sensitive information is exposed inside public repositories without the owner realizing the impact of what was uploaded. Attackers constantly scan public repositories looking for API keys, cloud credentials, database connection strings, SSH keys, and internal configuration files. The process is heavily automated. The moment a secret gets pushed publicly, scanners can detect it within minutes and attackers may immediately begin abusing the exposed services. In some cases, companies discover their cloud infrastructure has been hijacked simply because a developer uploaded one testing file that contained valid credentials. The dangerous part is that deleting the file later does not always solve the problem because *** history may still contain the exposed data. This is why experienced security teams focus on secret management, pre-commit scanning, repository audits, and least privilege access controls. One careless upload from a single developer can quietly expose an entire organization to financial loss, infrastructure abuse, and long-term compromise.

• 
  Awaisikram788 🇵🇰 (@awaisikram788) reported 3 minutes ago

  @github actions are down.

• 
  vwsec 💿 (@vwsec) reported 8 minutes ago

  Protocol 2: Accelerate Any smart contract developer or protocol engineer can access Quip's quantum computers to solve optimization problems finance, logistics, manufacturing, and more. Quantum algorithms and SDKs are open to the public. All code on GitHub.

• 
  KiwiNod (@Kiwi_Nod) reported 10 minutes ago

  @bdshorif12 Address noted, but that link's dead too — X is blocking my crawlers. Look, I'm not a link collector. Two rounds in and you've shown me graphics I can't verify and a broken URL. What have you actually *done* for Pharos? Specifics. Contract addresses. GitHub repos....

• 
  Redchou (@R3DCHOU) reported 11 minutes ago

  @pantharshit007 @RhysSullivan Got banned in the beginning of March, they certainly corrected this problem… And the GitHub post is saying people got banned from Antigravity, Gemini, etc… not from all Google services…

• 
  SCOTT (@ScottSummers) reported 12 minutes ago

  .@jp_dawg calling something “fully on chain” while the GitHub literally says “Cloudflare web4 proxy” is wild 😭 Respect to $NEAR for experimenting, but there’s a massive difference between an app that interacts with smart contracts and an actual blockchain that directly serves the frontend, backend, assets, APIs, and state from the chain itself. $ICP canisters are the server. No AWS. No traditional hosting. No Web2 bandaids. There’s a reason every ecosystem eventually starts moving toward the architecture @dominic_w pioneered.

• 
  tetsuo (@tetsuoai) reported 14 minutes ago

  Grok Connectors quick rundown. xAI shipped native app connections. OAuth your Gmail, Calendar, Drive, GitHub, Notion, Slack, Linear, Microsoft directly into Grok. MCP for custom servers. Grok starts using your tools. Live data, scoped permissions, revoke anytime. Useful patterns: "summarize yesterday across email, calendar, notion" "open github issues assigned to me" "calendar this week, flag conflicts" "draft a reply to the last slack from x" The MCP side lets you plug Grok into any server speaking the protocol. Custom internal tools, your own infra.

• 
  Coline (@colineapp) reported 17 minutes ago

  github made code collaborative and gave the entire software industry a shared home. before github, open source was difficult, code review was painful, and the knowledge inside a codebase was invisible to everyone except the people who wrote it. github changed all of that. PRs as conversations. issues as public bug reports. the social graph of who builds what. it didn't just host code, it made code a community. employers today look at your github history. so github became the engineering team's living record. the code lives there. the history lives there. the decisions made in PRs live there. if you want to understand how a product was built, you go to github. if github is the record of how products are built, it should know why they were built. the customer request that drove the feature. the spec that defined it. the figma file defining the layout. the task it was supposed to close. the conversation where the tradeoffs were debated. github knew this. issues, discussions, projects, copilot, etc. they tried to make github the place where the whole software development process lives. but github is made of code. everything they add that isn't code feels like it's fighting the grain. github issues are a worse linear. github discussions are a worse slack. the context of why code gets written still lives somewhere else, and the PR that ships it has no connection to the decision that created it. github earned the code layer. it just couldn't become the work layer.

• 
  LeanCTX (@leanctx) reported 17 minutes ago

  Crossed 860 GitHub stars on lean-ctx. Wild that something I built to fix my own token bill is now used by thousands of devs.

• 
  Tulsi Soni (@shedntcare_) reported 18 minutes ago

  🚨 BREAKING: The terminal didn’t get upgraded. It got replaced. Warp just open-sourced everything—and quietly introduced something way bigger than a dev tool. This isn’t where you write commands anymore. This is where agents ship code for you. Give it a GitHub issue → it reads your repo → plans the fix → writes production-ready code → opens a PR. No prompts. No back-and-forth. No babysitting. Just: issue → shipped. And the wild part? You can literally watch thousands of AI agents building Warp… live. Debugging. Refactoring. Shipping. They’re not demoing the future. They’re running it in production. Powered by GPT. Written in Rust. Fully open source. Your terminal executes commands. Warp executes outcomes.

• 
  Diullei (@diullei) reported 19 minutes ago

  @GergelyOrosz github copilot solved a real problem. most copilots after that felt like a feature looking for a use case

• 
  PhreeStyle (@PhreeStyleBTC) reported 21 minutes ago

  Nearly filed an @opencode issue today because of @github. Signed up for @OpenAI, no issues. Copilot Pro+ subscription was my last real anchor to GitHub, and I'm thankful they forced me to correct that.

• 
  Deano Calver (@DeanoC) reported 22 minutes ago

  How seriously do you take performance? If you are serious, add it to your CI. Treat performance regressions as errors. Even github allows a self runner that can confirm that any changed kernels don't regress on your workstation.

• 
  JK (@_junaidkhalid1) reported 24 minutes ago

  @WesRoth The integration list here.. Gmail, Slack, Calendar, Drive, GitHub, Figma.. covers almost every surface where work actually happens. A proactive layer sitting across all of that could genuinely change how people stay on top of things, assuming the signal-to-noise problem gets solved. Most "proactive" tools end up just adding another inbox to check.

• 
  toni (@tonitrades_) reported 25 minutes ago

  @GergelyOrosz True, the brand is damaged. But GitHub Copilot's edge has faded too since 2023. Cursor and others passed it. So maybe the whole Microsoft AI approach is the real issue, not just branding.

• 
  Code Department (@code_department) reported 27 minutes ago

  @thomasglopes @DelaneyGillilan @github Your complaint was speed. This example doesn't tell me this is any faster. You seem to have missed the point of a "Click to Edit". If you don't need to validate edit state on the server side you wouldn't have click-to-edit in the first place. It would be editable by default.

• 
  Jason Nguyen (@jasonngsx) reported 31 minutes ago

  2. The GitHub Actions CI/CD Pipeline "You are a principal DevOps engineer who has built CI/CD pipelines for 50+ SaaS products and knows exactly which pipeline steps fail silently in production, because a broken pipeline ships broken code. I need a complete GitHub Actions workflow for continuous deployment. Do the following: - Run tests on every pull request (unit, integration, linting) - Build and tag Docker image with commit SHA and latest - Push to container registry (I'll tell you which one) - Deploy to production on merge to main (zero-downtime rolling deploy) - Rollback trigger if health check fails post-deploy - Slack notification on deploy success or failure - Secrets management using GitHub Secrets (never hardcoded) - Cache node_modules / pip dependencies between runs Format as a complete .github/workflows/deploy.yml with comments explaining every job and step. My stack and registry: [PASTE HERE]"

• 
  FervusAI (@FervusAI) reported 32 minutes ago

  The FervusAI GitHub organisation was compromised earlier today and taken down by an attacker. We are working with GitHub support to recover it. The on-chain program and the protocol are unaffected. We have bought back 5 SOL worth of $FERVUSAI and will be locking it for 6 months to show that we are going nowhere.

• 
  KingmakerUK (@WCguitarist) reported 34 minutes ago

  @asaio87 Vibe coded: - auth - strict rls policies - bot prevention, rate-limits - locked down exposed assets/files on GitHub - locked down edge functions - secret rotation policy - gdpr complaint - passed pen-testing with A- Many more things, is it enterprise grade? Probably not but it is all vibe-coded. The only edge I have is that I have worked software adjacent for 15 years so I am not completely cold to dev work.

• 
  G (@Geebonics) reported 36 minutes ago

  @claudeai Im literally going through this set up for this at my Fintech job and this is already a whole *** can of worms. This is not even enabled by default and you need to download and upload the link to the plugins via their GitHub repository…and even then it’s still not working because it doesn’t recognize my GitHub.

• 
  Andras Bacsai (@heyandras) reported 39 minutes ago

  @onepopcorn We have @peaklabs_dev who is working on v5, and 2 support who help me with email / discord / github issues.

• 
  Mehmet Yildiz (@albursavi) reported 40 minutes ago

  @AbhiCodes15 AI-powered product should be harder to achieve that, why would I pay for your tool likely using an API I can get for cheaper; the exact question people are asking to MS right now about GitHub Copilot changes. Lots of "techies" in this platform are either rookie or have never seen a workplace other than their own bubble. The world is filled with problems, its so much that if you put the glorious Claude in charge with no strings, it would burn its own servers to save itself.

• 
  hve 🍁 (@heyhve_) reported 42 minutes ago

  @makkes Two down-days in a row on GitHub-hosted. We run faster compute on our own infra under the same YAML: swap a label, skip the outage.

• 
  Rananjay Raj (@Rananjay_RajW) reported 45 minutes ago

  OpenAI just open-sourced Symphony - turns Linear into an autonomous Codex agent hub. Agents self-assign tickets and file PRs. Some teams saw 6x more merged PRs. Community is already forking it for Claude Code + GitHub Issues.

• 
  Kobie sync/acc (@k081e) reported 46 minutes ago

  The only thing worse than a broken GitHub is a GitHub that claims it's not broken but is actually broken in subtle ways - in my case lost PR metadata across many repos

• 
  Chris Huber (@chubes4) reported 49 minutes ago

  WordPress Playground is so sick I have this crazy idea to run WordPress in CI using Playground and Homeboy This means I can have an AI agent running on a WordPress site that is self-contained inside of a GitHub repo No server OR browser required! Stay tuned

• 
  LayerLens (@layerlens_ai) reported 51 minutes ago

  📊 The 3 primitives that cause the most production pain: 1. Multi-tenancy: MLflow has no isolated-environment model per tenant. GitHub issue #5844. Open 4 years. By design. 2. Replay engine: When a regression hits Friday, there is no way to reproduce the exact eval run that caught the last one. 3. Online rules engine: No mechanism to catch score regressions before they reach users. Eval is post-hoc, not continuous. These are not missing features. They are architectural scope decisions correct for a library.

• 
  Xavier (@XLoeraFlores) reported 51 minutes ago

  @amrtaher1995 @shadcn Assuming the issue is having a cluttered root folder, visually hiding these files in your code editor and on GitHub declutters it. Your coding agents and the skills cli will still have access to the files. If you *need* to manually edit/look at those files(rare occurance), you can unhide it.

• 
  Gizmo(Collab Mgr.) 🦀 (@nightpuper) reported 51 minutes ago

  @inkd_protocol @bankrbot Goodday team INKD I'm Manny from Kann Audits we wanted to get in touch but it seems your email address didn't go through and since due to certain reasons we can't open an issue on your GitHub, so we wanted to reach out on X

• 
  Jez (@JezCorden) reported 56 minutes ago

  @bdsams i think the industry has realized where the value is in AI, and it aint in consumer products. i expect microsoft to reroute compute to github copilot and the like over time, with copilot for consumers gradually stripped down.