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 (68%)
• Sign in (18%)
• Errors (14%)

Live Outage Map

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

City	Problem Type	Report Time
Créteil	Website Down	19 days ago
Trichūr	Errors	22 days ago
Brasília	Sign in	22 days ago
Lyon	Website Down	23 days ago
Tel Aviv	Website Down	26 days ago
Rive-de-Gier	Website Down	26 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:

• 
  Sergio Gómez (@sgomez) reported 16 seconds ago

  The flow: I write the PRD with Matt's /to-prd skill and break it into GitHub sub-issues. Then, for each one, a dispatcher picks the right model, a code author opens a PR in an isolated worktree, a reviewer approves or asks for fixes, and the loop merges and moves on.

• 
  Salt Mine Ranch ⚙️🛠️ (@SaltMineRanch) reported 17 seconds ago

  GM frens. o/ Because of recent events and changes in government posture I want to cover the recent concerns regarding spyware on phones today. It's rather short but this is all there is to it at the basic level. Are you infected with Pegasus or Graphite? If you're one of my followers, you're a person of interest. Pegasus by NSO Group is one of the most advanced mobile spyware tools. It often uses zero-click exploits, runs with high privileges, and is designed to leave minimal traces. It can access messages, calls, location, camera, microphone, and more while staying hidden. Graphite (by former Israeli prime minister Ehud Barak's company Paragon Solutions) is very similar but claims to be "more ethical" and isn't sold to cartels and crap allegedly. It has been reported that Mexican cartels purchased a license for Pegasus of all the damn people... There's no telling who has it. Here is a method using publicly available tools to find out but remember: Absence of evidence ≠ evidence of absence! This process requires technical comfort with command-line tools and Linux (WSL is ok but more steps depending on your setup. I won't cover that, there are guides for USB passthrough or ask Grok). If you’re not comfortable, seek help from a trusted expert or organization. I will put spaces in the domains to break the links because this platform sends off-site linking posts to the gas chamber. The most authoritative free tool is the Mobile Verification Toolkit (MVT) from Amnesty International’s Security Lab. It was specifically created to detect Pegasus and similar spyware. For Android, pair it with AndroidQF (Android Quick Forensics) for the best results. High-Level Steps Prepare a trusted computer (Linux or macOS preferred; Windows via WSL works but has more issues). In WSL you will need to passthrough the USB device. Install Android SDK Platform Tools (for ADB). Install MVT (recommended via pipx): Follow the official guide: docs.mvt .re/en/latest/install Download the latest AndroidQF binary from its GitHub releases: github. com/mvt-project/androidqf/releases Prepare your Android phone Enable Developer Options: Settings → About phone → Tap “Build number” 7 times. Enable USB debugging: Settings → System → Developer options → USB debugging. Connect via USB and authorize the computer when prompted. Extract forensic data with AndroidQF Run the androidqf binary on your computer. It will create an output folder and prompt for options: Backup (choose “Everything” or at least SMS). Download APKs (non-system packages recommended). Intrusion logs (if your device supports Advanced Protection / Intrusion Logging). No root is required. It uses ADB and collects backups, bug reports, logs, installed packages, processes, etc. Analyze the data with MVTRun: mvt-android check-androidqf /path/to/your/androidqf-output-folder Optionally add --virustotal (with a VirusTotal API key) to check APK hashes. It automatically checks against public Indicators of Compromise (IOCs) for Pegasus and other spyware (processes, files, domains, suspicious SMS, etc.). Download/update IOCs if needed with MVT commands. Official resources: MVT documentation: docs.mvt .re Android methodology: docs.mvt .re/en/latest/android/methodology GitHub: github .com/mvt-project/mvt and github .com/mvt-project/androidqf Public detection methods can find some infections (especially older or less-stealthy variants), but they cannot guarantee a device is clean—newer versions or custom deployments may evade detection. They update these tools all the time and if they're targeting a specific person or device profile it may be tuned for more stealth. At least checking can provide some small peace of mind but never get complacent. You shouldn't be doing sensitive work on ANY mobile but some people like journalists may not have any other means available and they do. Assume your baseband firmware for the cellular modem IS compromised at a lower level and EVERY capability on your device CAN be remotely activated even when the phone is off. That's why you can't remove your battery anymore.

• 
  Mvykool (@mvyk0l) reported 4 minutes ago

  Why can’t they just fix Windows and GitHub???

• 
  Eduardo (@martiano) reported 6 minutes ago

  Why does GitHub default to their mobile app instead of passkey or 2fa code? It makes no sense to pick up your phone every time you need to login

• 
  David Cramer (@zeeg) reported 6 minutes ago

  @rsdgpt Toss it in a GitHub issue otherwise feel free to DM (or shoot me a slack connect) if its easier

• 
  Ryan Lelek (@ryanlelek) reported 7 minutes ago

  @github April 1st was months ago. Fix your uptime

• 
  João Gonçalves (@joaofogoncalves) reported 9 minutes ago

  Self-hosted infrastructure tools don't lose to AWS or Vercel on features. They lose on trust. Nobody evaluates a deploy tool by asking if it can run a container. They ask what happens when someone leaves the company, whether an audit log can leave the building, and whether a bad rollout gets undone before anyone notices. Alerts either fire before the outage or show up after it, as a postmortem. That's the shape of milestone 4.0 on the BridgePort roadmap: one-click rollback and phased rollouts, threshold alerts, backup restore instead of backup-only, SSO, 2FA, audit-log export, secrets pulled from Vault instead of hardcoded into a compose file. None of it is a feature anyone asks for on day one. It's the reason a team says yes on day 400. Even the page itself makes the point. Generated straight from the GitHub tracker, no fake dates. Directions, not commitments.

• 
  Sethian (@theSethian) reported 13 minutes ago

  Your AI agent still needs a babysitter. Owain Lewis shows the better version: give it a goal, a clock, and a way to prove the work is done. Old workflow: you write the prompt, read the answer, spot the failure, paste the next instruction, run the test, paste the error back, and keep steering. You are still the engine. His setup uses three primitives: A goal gives the agent a finish line. Deploy the app, wire CI/CD, check the health endpoint, check the web app, and stop only when the app is live. A loop gives it a clock. Every 5 minutes, check the PR, read new feedback, fix what changed, and keep going. A scheduled automation gives it a recurring job. Scan production logs every morning, find errors, reproduce the bug, add tests, and open a PR with evidence. The best examples are the work devs keep putting off: > memory issues hiding in production logs > stale docs drifting away from the code > GitHub issues waiting for labels > old tickets ready but untouched > PR feedback nobody wants to refresh all day > deployments that need a real health check The important part is the verifier. The agent doesn't get to call the work done just because it produced output. Tests, builds, health checks, a separate model, or a human review step have to confirm it. Otherwise you don't have a loop. You have an agent shipping confident garbage on a schedule. The article below breaks down the full anatomy: verification, memory, maker-checker splits, open vs closed loops, cost per accepted result, and the point where the human still needs to step back in.

• 
  Abhishek Singh (@0xlelouch_) reported 15 minutes ago

  Loop engineering is simply moving from: “AI, write this function for me” to: “Here is the goal, rules, tests, tools, and stop condition. Keep working until the result is actually correct.” Instead of you manually prompting the AI 20 times, you build a repeatable loop where the AI can: 1. Understand the task 2. Inspect the codebase 3. Make a change 4. Run tests/lint/build 5. Read the failure 6. Fix itself 7. Stop only when checks pass Simple example: You want to add rate limiting to a Go API. Normal prompt engineering: “Write rate limiting middleware in Go.” AI gives code. You paste it. Build fails. You send error. It fixes it. Tests fail. You send another prompt. You are the loop. Loop engineering: “Find all public API routes. Add per-user rate limiting of 100 requests/minute. Use Redis. Do not change existing response formats. Run unit tests and integration tests. Fix failures until all tests pass. Create a PR only when coverage does not decrease.” Now the agent has a loop: Goal: Add rate limiting while requirements are not verified: inspect codebase implement smallest safe change run go test ./... run integration tests inspect errors fix errors check security/performance constraints stop when: tests pass coverage is not lower API contract is unchanged The important part is not the AI prompt. The important part is the feedback system around it. --- Remember, Good loop engineering needs: - clear goal - access to tools: code, logs, tests, GitHub, database sandbox - rules: what it must not break - verification: tests, lint, benchmarks, review - memory: what it already tried - stop condition: when to stop spending tokens and touching code Think of it like hiring a junior engineer. Bad setup: “Build something good.” Good setup: “Fix this bug. Here are the logs. Here are the tests. Do not touch payments. Run the test suite. Show proof before merging.” AI agents become useful when they are not just generating code, but are forced to observe reality and correct themselves. So prompt engineering is asking better questions. Loop engineering is building a system where the AI keeps asking itself the next useful question until the work is done.

• 
  Aaron Stannard (@Aaronontheweb) reported 15 minutes ago

  @kzhen as an inference provider? have not tried it at all - we just got GitHub Enterprise deployment fully polished in last night's stable release, but I haven't had any requests for Azure Foundry yet. Let me see how much trouble it would be to add it

• 
  BIGWARZ (@bigwarzeth) reported 17 minutes ago

  @JoshXT message from Alon and i quote : "He needs to login with any other method and then he can connect via GitHub inside the app"

• 
  Parth Jadhav (@ParthJadhav8) reported 18 minutes ago

  @free_duino Would really recommend to create a issue on GitHub with the data. It would be helpful

• 
  Matt Fauveau (@MattFauveau) reported 21 minutes ago

  Fix one: a line under the CTA reassuring you it won't mess with your real board, because that was IMO the silent objection. Fix two: a "Built by Matt Fauveau" credit. Sounds vain. It isn't. When your tool writes to someone's GitHub, a name is trust. People want a human accountable for the thing in their repo.

• 
  Parth Jadhav (@ParthJadhav8) reported 23 minutes ago

  @KeithBirminghan This seems pretty cool, do you mind sharing issues Github issues?

• 
  John Papa (@SublimeTrades) reported 24 minutes ago

  Been using this short window we have access to Fable 5 with the paid subscriptions to do high level design and architecture discussions with HLDs and GitHub issues as the outcome of the sessions. Seems a waste to have Fable actually code with how fast it burns tokens.

• 
  Tyler G (@TylerByte666) reported 25 minutes ago

  @github You ******* went down a few weeks ago when i had a deadline! And now your making fun of gamers. Gitslop **** off!

• 
  Cody (@mackody_) reported 30 minutes ago

  When many agents (Claude, Codex, humans, CI jobs — anything) work the same repo, they collide: two of them grab the same issue and duplicate or clobber each other's work, this annoyed me so much I created a GitHub-native mutex for multi-agent work. Link Below:

• 
  SB (@swbitxches) reported 30 minutes ago

  @github FIX UR WEB APP. Cringe

• 
  One&OnlyAarav (@WaterAarav) reported 34 minutes ago

  Claude = coding. ($20/mo) Shypmenta = deploys, connects, and manages every platform below($6/yr) Supabase = backend. (Free) Vercel = deploying. (Free) Namecheap = domain. ($12/yr) Stripe = payments. (2.9%/transaction) GitHub = version control. (Free) Resend = emails. (Free) Clerk = auth. (Free) Cloudflare = DNS. (Free) PostHog = analytics. (Free) Sentry = error tracking. (Free) Upstash = Redis. (Free) Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20. Building has genuinely never been this affordable, and rarely this effortless either.

• 
  Rajaji (@rajaji2) reported 35 minutes ago

  Automate Docker image builds and push to ECR using GitHub Actions like a DevOps Engineer! ✅ Trigger on push to main branch ✅ Configure AWS credentials using aws-actions/configure-aws-credentials ✅ Login to ECR with amazon-ecr-login action ✅ Build and tag Docker image with com...

• 
  Rudra (@Rudra1071219) reported 38 minutes ago

  Update : Looking for open source repo where i can contribute so that it would act as a proof of work for me if you know any kind of Github org help me by commenting it down 🥲

• 
  Steve Lauda (@stevelauda_) reported 40 minutes ago

  Github will do anything but fixing their uptime quality. I wonder what exactly goes in their executive weekly meeting. "Hey guys, our downtime still bad, what should we do?" "Ah, maybe our users would love to push their repo into CD-ROM, no more up-time, the repo stays with you forever, until the disc break ofc," "Ah yes, yes, write that down, write that down!"

• 
  Rashi Umapathi (@rashiumapathi) reported 46 minutes ago

  I do marketing for founders who hate marketing. Your product is good. People just aren't finding it yet. That's the whole problem I solve. Founders come to me with 400 github stars and 3 paying customers. Great product, Invisible distribution. I fix it three ways: - Reddit: your story where buyers actually hang out - SEO + Content: rankings + showing up in AI answers - Personal brand: people follow people, not changelogs I don't hand you a plan. I execute it with you. Some things i've pulled off: - 400k+ views on one reddit series. - 200 signups from a single reddit comment - 1M+ views on a zero-budget campaign - 19+ signups and paying customers in 28 days with SEO If this is you, DM me. Worst case you leave with a free diagnosis.

• 
  Nick Hazrd (@badhazrd) reported 48 minutes ago

  @GregTomaselli @github I think the biggest security issue is the fact that you won't get public or private.

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 50 minutes ago

  @JasonBoxman Raise an issue in GitHub

• 
  Chris.agents (@chrisvibe_ai) reported 51 minutes ago

  One-person Company Costs - Claude = Coding. ($20/month) - Supabase = Backend. (Free) - Vercel = Deployment. (Free) - Namecheap = Domain. ($12/year) - Stripe = Payments. (2.9%/transaction) - GitHub = Version Control. (Free) - Resend = Email. (Free) - Clerk = Authentication. (Free) - Cloudflare = DNS. (Free) - PostHog = Analytics. (Free) - Sentry = Error Tracking. (Free) - Upstash = Redis. (Free) - Pinecone = Vector Database. (Free) Only in AI era #AI

• 
  Melfoy (@melfoy_work) reported 51 minutes ago

  Fable 5 runs for 11 days. One builder used it to write 3 files. The files still run. The model is gone. Marcus, 38, warehouse supervisor in Dayton. Kids in school, mortgage, $19/hour. Spent a Sunday building a spreadsheet factory instead of watching the game. He used Fable once - architect role only. It built the product, then he made it write down how it did it. One skill file. Committed to GitHub. Switched to Haiku. Ran the same build. Cents. His wife asked why he was still at the laptop at midnight. «Building something.» «Another one of those things?» By month two: 20 listings. $600 a month. Haiku running while he slept. By month four: $2,000. Approvals take 10 minutes a day. Fable is gone now. The 3 files are still in the repo. The brain was rentable. The playbook is his.

• 
  NoRoseGlasses (@glasses_no) reported 52 minutes ago

  @gatewaypundit This is a problem. I see Claude all over their GitHub dev pages, especially Voting Works.

• 
  Vaneck Intern (@NewVaneckIntern) reported 55 minutes ago

  @github Okay but can you fix the way we upload files to repos? I don't think an upload folder button on the website is too much to ask. Neither is a consistent desktop experience

• 
  Ege (@is_ege_) reported 60 minutes ago

  @github @luciascarlet fix your ******* platform dude