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 (60%)
• Errors (29%)
• Sign in (11%)

Live Outage Map

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

City	Problem Type	Report Time
Gustavo Adolfo Madero	Website Down	2 days ago
Nice	Website Down	2 days ago
Montataire	Sign in	5 days ago
Colima	Website Down	7 days ago
Poblete	Website Down	8 days ago
Ronda	Website Down	8 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:

• 
  BrainMirror AI (@brainmirrorai) reported 5 minutes ago

  Private Publishing on Replit blocks unauthorized requests at the network level, not inside the app. The problem was always integrations: if you needed GitHub webhooks or Slack callbacks to reach your private app, your only option was to make the whole app public. External Access Tokens remove that tradeoff.

• 
  Rich (@richiekastl) reported 6 minutes ago

  > be me > buy Grok Heavy for $300/month because there's now a Github connector > expect the greatest programming mind available to mankind to absolutely ******* away > feed it a problem I've been working on for my game that Claude or ChatGPT can't solve > watch it commit and create a PR > The PR

• 
  Swim Code (@SwimCodeAi) reported 9 minutes ago

  @awildnpc @ravikiran_dev7 I’ll have to update it. The only thing that we have is clerk for authentication. Everything else is local. Authentication token, and all that stuff is old now you login via your GitHub account.

• 
  Layla CryptoWhiz (@laybitcoin1) reported 11 minutes ago

  @assaf_elovic Not crazy at all. Billions of commits documenting how humans actually solve problems. That history on GitHub is basically the context layer AI keeps missing.

• 
  Aditya Sharma (@sharmaadityaHQ) reported 14 minutes ago

  @apoorv_taneja @github they are not even fixing it. broken from quite some time.

• 
  Ethan Jiang (@ethanjyx) reported 15 minutes ago

  Year 1 as a solo founder, 10k+ Github contributions (Claude code is really addictive). But looking back, I probably wouldn’t do it the same way. The biggest bottleneck in a business is often NOT solved by more code. Going into year 2, I have a daily reminder to think about biggest bottlenecks and fix those ruthlessly.

• 
  Solomon Eseme (@Kaperskyguru) reported 23 minutes ago

  One strong GitHub project with a README that explains: - What problem it solves - How you built it - What you would improve next That is worth more than 10 half-finished repos that die after the initial setup. Hiring managers care about what you shipped, not what you watched.

• 
  Haroon (@skywalkerr0x) reported 25 minutes ago

  Agentic workflows on every PR can silently rack up big API bills. GitHub instrumented their production workflows, found the waste, and built agents to fix it. Your PR workflows might be doing the same.

• 
  Daniel Vermillion (@dxverm) reported 26 minutes ago

  I've got 24 MCP servers wired into one session. Almost none of them are loaded right now. The "100 MCPs is too many" debate misses what's actually expensive. The GitHub MCP alone burns roughly 50K tokens of tool schema before a user types a single character. Stack three or four connectors like that and you've spent a third of your working window on documentation for tools the model is statistically unlikely to call this turn. The fix is not fewer servers. It's deferred schemas. The harness publishes a list of tool names in a small system reminder. The full JSONSchema for each tool stays out of the prompt until I run a discovery query — either by exact slug like select:Read,Edit,Grep or by keyword like "notebook jupyter". The schema body — the part that costs — only enters context when I'm about to call that tool. Same pattern works for skills. 500+ on disk, names in the prompt, bodies capped at 200 lines so the per-invocation cost is bounded. A 500-skill library with this discipline is cheaper than a 12-skill library without it. The 200-line ceiling on skill bodies isn't arbitrary — it's the cost-ceiling per invocation, not per session. This changes how you build the stack. Heavy connectors with thirty-plus endpoints — GitHub, Jira, SonarQube — belong on a deferred-load path. Light, every-turn tools like filesystem and memory stay resident. Treat tool definitions like a working set, not a manifest. The model doesn't read all the tools you give it. It reads the ones loaded into the prompt that turn. Tool count is a marketing number. Resident-token weight is the engineering number. Build for the second one.

• 
  Suryansh Tiwari (@Suryanshti777) reported 28 minutes ago

  Most AI coding tools today have one terrifying flaw: They can touch production systems directly. One wrong prompt. One hallucinated command. One overconfident agent. And suddenly your database, GitHub repo, Stripe account, or filesystem is gone. That’s exactly the problem JanuScope is solving. The idea is insanely smart: Instead of trusting the AI… put a security + policy layer between the AI and your MCP tools. So before Claude Code, Cursor, Copilot, or Codex can do anything sensitive, JanuScope intercepts the request and decides: should this tool even exist? should this SQL query be allowed? should sensitive data be redacted? should this action be audited? should the AI even see this schema? And the craziest part? It works with existing MCP servers using just one YAML file. No rewriting servers. No hosted gateway. No changing your stack. Just wrap your MCP with: npx -y januscope --config postgres-crystaldba and suddenly your AI tools become dramatically safer. The repo is packed with things that actually matter in production: • SQL mutation blocking • PII redaction • audit logs • schema injection • GitHub safety layers • filesystem protections • rate limiting • tool quarantining • OpenTelemetry support • first-run fingerprint approval And unlike most “AI security” projects… this one has real benchmarks. Across multi-question sessions it achieved: 84% fewer tool calls 84% fewer tokens ~3× faster responses because the schema gets injected directly into tool descriptions instead of forcing the model to repeatedly “discover” the database. That’s a genuinely clever optimization. But the biggest signal for me is this: The README doesn’t feel like hype. It feels like someone who deeply understands how AI agents actually fail in real-world systems. The sections on: Replit wiping databases Cursor deleting production infra SQL bypass edge cases MCP threat surfaces prompt-injection through tool descriptions …show a level of engineering paranoia that AI tooling desperately needs right now. This is one of the best MCP infrastructure repos I’ve seen recently. If AI agents are going to touch real systems, projects like this become mandatory. (Link in comments)

• 
  TurtleAIHacks (@TurtleAIHacks) reported 30 minutes ago

  Claude Code ships with MCP tools most people never enable. ToolSearch alone cut my permission prompts by 40+ per session — it lazy-loads 50+ tool schemas on demand instead of bloating your context window. GitHub MCP replaces the entire gh CLI. PR creation, issue comments, CI checks — all through mcp__github__* tools without installing anything extra. Brave + Tavily MCP gives you real-time web search. Claude's training data has a cutoff. MCP search doesn't. These aren't plugins you download. They're already there in your settings.json, waiting for one line of config. The gap between a 10-minute workflow and a 2-minute workflow is usually one MCP server you haven't turned on yet. #ClaudeCode #AI

• 
  Marc Campbell (@marccampbell) reported 30 minutes ago

  github was great this week. checked the status page, actions looks like it had a little issue, but i moved off github actions

• 
  Shagrath (@shagrath49) reported 33 minutes ago

  @thdxr How do you keep track of what you have to do ? GitHub issues ?

• 
  PsudoMike 🇨🇦 (@PsudoMike) reported 36 minutes ago

  @cursor_ai Having PR review inside the same environment where you write code removes constant context switching between editor, GitHub, Slack, and back. The diff navigation on big PRs is the part that actually slows teams down.

• 
  Prince K. Patel (@princu09) reported 36 minutes ago

  Node.js throwing errors and you don't know why? My debugging checklist: 1. Read the error message fully 2. Check line number first 3. console.log before and after the issue 4. Google the exact error in quotes 5. Check Stack Overflow + GitHub issues Step 4 solves 80% of my problems.

• 
  Andrea_Stivy (@co_foundr) reported 36 minutes ago

  @emanueledpt Remodex android needs to be tested extensively, for every bug or feedback you can also open a GitHub issue or fix it yourself and send a PR! Let's goooooooo

• 
  Tim (@buildwtim) reported 37 minutes ago

  @KeyNyata if pushups could fix my code, i'd have the cleanest repo on github by now ;)

• 
  modi (@modisulak) reported 39 minutes ago

  @neil_xbt repo lists with broken github line wraps still outperform most newsletters

• 
  Dariusz Parzygnat (@dariusparzygnat) reported 39 minutes ago

  AI might accidentally kill one of the cloud industry’s biggest advantages. for years the pitch was: “don’t manage servers yourself.” fair enough. setting up VMs was annoying as hell. i just connected Codex to a VPS. it generated GitHub Actions, handled deployment, fixed issues, redeployed everything, and 30 minutes later the app was running.

• 
  dagz (@AstrayaNthemoon) reported 42 minutes ago

  @jkpgamer Haha well I was gonna say that I could spin up a GitHub, (Goose + Grok have been dying to let me let them open a GitHub with a key), and then open source the code… it’s like so minimal it’s laughable and then you can put your own location on the map but that’s even better to point to your own server rather than pull the API That’s how we initially had the design built actually but then I wanted it to be something anyone could use

• 
  Yashasvi Kapil (@iemyashasvi) reported 48 minutes ago

  @ChiragAgg5k @github @github is broken beyond repair

• 
  Chester Brian (@chestrbrian) reported 50 minutes ago

  was vibe coding my project and had been REVOKE'ing UPDATE on sensitive columns in my migrations. subscription_tier, credit balances, boost flags, github tokens. claude code wrote them, i reviewed them, they looked locked down 12 of these across my migrations. all decorative. zero actually enforcing anything turns out postgres evaluates table-level + column-level privileges with OR semantics. supabase grants table-level UPDATE to authenticated by default. a column-level REVOKE removes a privilege that was never separately granted at the column level. so it binds to nothing 5 were P0 financial. a signed-in user could've: >set subscription_tier='top_tier' on themselves (free top-tier sub) >reset last_credit_grant_at to the past (cron grants on next tick, repeat hourly, infinite credits) >set is_boosted=true on their own posts (free featured placement) >read every other user's github_access_token (same no-op on the SELECT side, token harvest) the fix is two lines per table: REVOKE UPDATE ON <table> FROM authenticated; GRANT UPDATE (allowed, columns) ON <table> TO authenticated; vibe coding lets you ship fast. it does not exempt you from knowing what your migrations actually do

• 
  Sarah Wooders (@sarahwooders) reported 50 minutes ago

  Is anyone building github for agents? Specifically: - API/SDK interface - make millions of repos no problem - fast

• 
  Anton Kuratnik | AI Nerd (@anton_onAI) reported 52 minutes ago

  For anyone working with n8n, stop relying on ChatGPT/Claude to tell you how to build/debug a n8n workflow. They're poorly trained on n8n & out of date and will lead down the wrong path. n8n have their own AI and it knows their docs AND github issues so anytime you need to answer "How does this work?", "What's the best way to do this?", or "Why isn't this working?" it does so accurately and based on whatever version of n8n you're on. This thing seriously made my life way better. (Yes, they have an MCP. No, it doesn't work nearly as well as that purple buton)

• 
  Jai Jalan (@jjalan) reported 55 minutes ago

  @Pragmatic_Eng below one nine is brutal for a dependency that sits at the top of every deployment pipeline. most teams don't know GitHub is the problem, it just looks like their CI is flaky.

• 
  Zephyr (@Zephyr_hg) reported 59 minutes ago

  5. Plug in MCP servers for any external tool. Postgres MCP for database queries. Notion MCP for your workspace. GitHub MCP for issue management. Any external system becomes an extension of Claude Code in 5 minutes of setup.

• 
  Vivek (@BahutNaive) reported 59 minutes ago

  Deletes github issue -> Project list views containing that github issue gets broken. Then even admins of the project couldn’t delete the project item id referring the github issue. Total chao becoz of github

• 
  jordan kitty (@joraweb3) reported 1 hour ago

  what I love most about @aeonframework it runs on github actions you turn off your pc and agent still sends updates on what it’s doing no server magic 🙃

• 
  Ofek Shaked (@VibeCoderOfek) reported 1 hour ago

  Switched my flow to multi-agent last week and context was the killer. Grok Build’s terminal + GitHub integration looks like it finally solves the ‘forgetful colleague’ problem. xAI might have the desktop killer here.

• 
  Elena Revicheva (@reviceva) reported 1 hour ago

  🤖 AIdeazz now pulls fresh prospects from Hacker News, GitHub, and Product Hunt straight into HubSpot twice a week. No manual work, no cost. The AI reads each person, spots their real problems, and organizes them as ready-to-contact leads. #AI #BuildInPublic #AIFounder