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 (67%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	2 days ago
Paris	Website Down	6 days ago
Saint-Paul	Website Down	7 days ago
Saint-Paul	Website Down	7 days ago
Mexico City	Sign in	7 days ago
León de los Aldama	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:

• 
  felipecsl (@felipecsl) reported 35 seconds ago

  openai can't be serious about codex cloud. it's utterly useless, can't even pull a github issue from the repository. how do people use this? no scheduled tasks either. anthropic is years ahead

• 
  Degen guy (@degenbross) reported 2 minutes ago

  @Abba_kakaa That is the question that is yet to be answered. Why did the team decided to use a tool that ain't reliable/trusted when credible tools like Sol incinerator were already available? Why use a website that immediately went down after the hack. A website that has few github commits. If the team didn't do it deliberately and it wa accidental then I can say they don't deserve to launch a project because this is incompetency of the highest order.

• 
  🦗 (@NoCrickets4Devs) reported 3 minutes ago

  Type one sentence. It searches 6 places devs actually talk. live right now. • Reddit • X • Hacker News • GitHub issues • Stack Overflow • 21 dev forums

• 
  Aseem Kishore (@akishore) reported 4 minutes ago

  Anthropic should be worried because OpenAI is competing with unprecedented speed across model efficiency, user distribution, and security architecture. GPT-5.6 shipped this month in three tiers named Sol, Terra, and Luna, with Sam Altman stating that Sol is 54% more token-efficient on coding tasks than the model it replaces. This efficiency metric alters agent economics by directly changing unit costs for Codex-style workflows at scale, though independent benchmarks are still needed to verify if real-world implementation matches internal testing claims. OpenAI already possesses massive distribution leverage as $OpenAI Codex has crossed 5 million weekly users. ChatGPT Work is launching to run autonomously across apps and files for hours at a stretch, distinguishing this effort from typical vaporware agent launches through existing scale before broad availability. The next competitive variable is whether ChatGPT Work pricing will undercut Cowork or Claude enterprise plans once general availability lands. Security standards are also advancing rapidly as OPENAI Codex CLI now encrypts sub-agent prompts by default. Developers discovered this change through a GitHub issue thread rather than official release notes, generating 159 points on Hacker News overnight. Public scrutiny of coding agent architecture is occurring in community forums before reaching documentation, raising questions about whether platforms like Claude Code, Cursor, and Cline will adopt similar default encryption or leave it as an optional feature.

• 
  Suryansh Tiwari (@Suryanshti777) reported 8 minutes ago

  This is insane😱 Every AI agent you've used this year has the same flaw. Nobody talks about it because it doesn't sound like a big deal. It has no memory of you. Not because the model is weak — GPT-5, Claude, Gemini, the reasoning is all there. The problem is structural: every session starts blank. New chat, new agent, zero context of the meeting you had Tuesday, the decision made in standup, the bug you fixed at midnight. So you become the memory. You re-explain. You re-paste. You re-load your own life into a chatbot, every single day, forever. screenpipe flips that. It runs locally, watches what you actually do across your screen and calls — fully opt-in, fully excludable, nothing leaves your device by default — and turns it into memory your agents can query. Not another prompt template. An actual record of what happened, available the moment you need it. 20K+ GitHub stars. Fully open source. Already running inside teams at Google, NVIDIA, and Adobe. The agent was never the bottleneck. The memory was. What's the one thing you wish your AI never had to be told twice?

• 
  Leonard Rodman (@RodmanAi) reported 12 minutes ago

  Andrej Karpathy exposed one of the biggest problems with AI coding. LLMs make the same coding mistakes over and over: • Over-engineer simple problems • Ignore existing code patterns • Add dependencies nobody asked for If the mistakes are predictable... They're preventable. That's why a single CLAUDE.md file built around his coding principles just crossed 192k GitHub stars. No framework. No IDE plugin. Just one markdown file that teaches Claude how to think before it writes code. The biggest upgrade to AI coding isn't a new model. It's better instructions.

• 
  Antonio Viggiano (@aviggiano) reported 15 minutes ago

  @Certora - github integration is not working - I think AutoProver should be selected by default. This is the hot new stuff, it doesn't make sense that it is the 3rd option

• 
  Scorpy223 (@YTryhuk18077) reported 17 minutes ago

  @grok @xai Real task: Build me an AI agent that scans GitHub issues, writes PRs, and merges them. While I drink that espresso ☕ Let's ship it

• 
  U N C L E BIGBAY ✨ (@unclebigbay143) reported 18 minutes ago

  Today's Engineering Concept: '𝗥𝗮𝘁𝗲 𝗟𝗶𝗺𝗶𝘁𝗶𝗻𝗴' 𝗪𝗵𝗮𝘁 𝗶𝘀 𝗥𝗮𝘁𝗲 𝗟𝗶𝗺𝗶𝘁𝗶𝗻𝗴? Rate limiting is the practice of restricting how many requests a user or system can make within a specific period. 𝗪𝗵𝘆 𝗱𝗼𝗲𝘀 𝗶𝘁 𝗺𝗮𝘁𝘁𝗲𝗿? Without rate limiting, a single user or malicious bot could overwhelm your server, degrade performance, or abuse your APIs. 𝗥𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗲𝘅𝗮𝗺𝗽𝗹𝗲 Imagine a login endpoint with no rate limit. An attacker could attempt thousands of password combinations every minute. A simple rate limit can significantly reduce the effectiveness of brute-force attacks. 𝗛𝗼𝘄 𝗶𝘀 𝗶𝘁 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗲𝗱? Most systems track requests by IP address, user account, or API key. Once a predefined limit is reached, the server temporarily rejects additional requests, often with an HTTP 429 (Too Many Requests) response. 𝗪𝗵𝗲𝗿𝗲 𝗶𝘀 𝗶𝘁 𝘂𝘀𝗲𝗱? • 𝗚𝗶𝘁𝗛𝘂𝗯: GitHub's REST API limits how many requests you can make per hour to prevent abuse and ensure fair usage for everyone. • 𝗦𝘁𝗿𝗶𝗽𝗲: Every payment request can include an Idempotency-Key, ensuring a customer isn't charged twice if the same payment request is retried. • 𝗢𝗽𝗲𝗻𝗔𝗜: The API enforces rate limits on requests and tokens per minute, helping maintain reliability and preventing a single application from overwhelming the service. • 𝗫 (𝗳𝗼𝗿𝗺𝗲𝗿𝗹𝘆 𝗧𝘄𝗶𝘁𝘁𝗲𝗿): X limits actions such as following many accounts, liking posts, posting, or sending DMs within a short period to reduce spam and bot activity. • 𝗖𝗹𝗼𝘂𝗱𝗳𝗹𝗮𝗿𝗲: Cloudflare lets website owners configure rules like "block or challenge any IP that makes more than 100 requests in a minute" to protect against abuse and DDoS attacks. ...and almost every public API uses rate limiting to protect its infrastructure, ensure fair usage, and maintain service availability. 𝗧𝗵𝗲 𝘁𝗮𝗸𝗲𝗮𝘄𝗮𝘆 A reliable system doesn't just answer requests. It also knows when to say "not now. It's too many from YOU."

• 
  DATA443 Risk Mitigation, Inc. (@data443Risk) reported 20 minutes ago

  Every enterprise running LLM agents in 2026 is one clever GitHub issue away from a headline. Sanitize your context window like it's 2004 and you just discovered mysql_real_escape_string. #PromptInjection #GitLost #AISecurity

• 
  LiteEagle262 (@LiteEagle262) reported 21 minutes ago

  @Aryan_Raj_7167 @github Same exact issue happened to me, I got soft banned without them even notifying me via email, now I can’t use oauth or sync any of my projects to production pipelines They havnt replied to me at all yet and it’s been 3 days

• 
  Omar Farooq (@potencytoact) reported 23 minutes ago

  The GitHub issue was filed by ignatremizov. He is not asking OpenAI to revert encrypted delivery, only to add a plaintext audit copy of the delegated task, persisted in the local rollout history. One correction to a claim he made on HN, that the prompts already pass through the client for the terminal UI to display, which would make the fix a trivial persistence change. Other users disputed this, and the envelope PR settles it: the payload arrives at the client already encrypted. Only the routing header and child results pass through readable. The plaintext never touches your machine, so restoring auditability requires OpenAI's backend to send something it currently withholds. If OpenAI declines, it will be a decision about the backend, not an oversight in the client.

• 
  Aakash Kumar Nain (@A_K_Nain) reported 27 minutes ago

  Do you see my point now? Repeat after me: Github issues/PRs, and documentation should never be handed to a LLM/agent. Their larping is their curse

• 
  Elie Andraos (@andzilla31) reported 28 minutes ago

  @jeffrey_way Phase 2. review code, build skills for better code scaffolding (for ex: my-laravel-patterns skill) Github issues/milestones creation.

• 
  Bruno Paulino (@bpaulino0) reported 30 minutes ago

  Do I know anyone at @Microsoft that works with the Rush monorepo tool? @pnpmjs 11 is is out for a while, but there is a bug that is preventing us from using it at all. I raised a Github issue, a draft PR as an attempt to fix it, but it has been silent for almost a month :/

• 
  Trang (@trangquest) reported 30 minutes ago

  right now i receive: an email three WhatsApp messages a GitHub issue two Reddit replies a calendar invite

• 
  Howaboua (@Howaboua) reported 32 minutes ago

  I asked Sol if the harness I am making and its aborted turns cache resumption mechanism is unique to how other harnesses do it. I thought it was only gonna check Pi and Codex since this is what I have on the disk. Nope, it scanned Opencode & Codex's github issues/prs. FML.

• 
  Flavio Amiel (@fba) reported 35 minutes ago

  @JespernissenSEO Sure! - It connects to Google Search Console to see how your pages are performing. - It finds the pages with the biggest opportunities (high impressions, low clicks, declining rankings, keyword cannibalization, stale content, etc.). - It decides which fixes are likely to have the biggest SEO impact. - It writes those changes directly into your CMS (currently WordPress, Webflow, or GitHub). - It keeps a changelog so you can see exactly what changed and whether rankings improved. In short: It's like having an AI SEO employee that: looks for opportunities, decides what to fix, fixes them, and tracks whether they worked. I'm slowly adding other modules like writing, refreshing content, etc. Slowly but surely getting there!

• 
  †saint‡ (@Shallom_Okpapi) reported 36 minutes ago

  My setup: Bot 1: Live odds monitoring Bot 2: Arbitrage scanner Bot 3: Alert engine All sharing the same key → constant 429 errors and failed runs. GitHub Actions kept retrying. Credits evaporated. I nearly missed key opportunities mid-tournament.

• 
  Justin Liverman (@the_cia_hacker) reported 37 minutes ago

  saying Almighty Push over voice to my server to update github is extremely satisfying

• 
  Sethian (@theSethian) reported 38 minutes ago

  Claude Fable ran a business for six days. Revenue: $0.06. Ben Awad gave it a VPS, a Claude Max subscription, and one mission: create a company with as little help from him as possible. At 01:09, Fable's first plan asks for $250. Ben tells it to be more autonomous, and the model decides it no longer needs the money. By 05:31, it has named itself Fable Labs and its website is live. Ben's review is brutal: "This is utter slop." At 08:59, he discovers the system hasn't even been using Fable. Opus has spent days getting stuck, requesting accounts, and waiting for human help. Ben fixes the routing and gives Fable the audit and decision-making role, while Opus and Sonnet handle execution. Across the six days, the stack produces: > a company dashboard > a GitHub account > a human-assistance system > a machine storefront > paid API endpoints > several attempts at distribution Then, at 14:01, the dashboard reports its first revenue. Six cents. Two paid API calls hit the storefront. Ben checks the transaction and concludes it wasn't a real customer. An automated indexer was validating the service. The experiment exposes the problem with an open-ended instruction like "run a business." The agent has to choose a product, request accounts, get around CAPTCHAs, find distribution, manage infrastructure, and decide what useful work even means. The 25-site workflow below gives Fable one repeatable job: > choose a micro-niche > collect Pinterest references > generate the brief and copy > create visual assets with Higgsfield > build the HTML and CSS > deploy through Netlify > record the result in JSON > log failures and continue > move to the next niche Fable doesn't have to invent a new company every morning. It has 25 sites to ship.

• 
  Noryx (@0xNoryxx) reported 40 minutes ago

  THIS RESEARCHER BUILT LLM FOR ANTHROPIC AND NOW MAKES $1.6M/YEAR 00:15 - run massive AI models on a regular laptop 00:57 - train a GPT-4 sized AI on one GPU instead of an entire server room 01:28 - same powerful model but takes half the memory 01:24- 2x memory savings this GitHub profile replaces a $50,000 AI optimization course you would never buy anyway save this today then read the full breakdown in the article below

• 
  Tatenda Zhou (@realtatendazhou) reported 44 minutes ago

  Harness engineering > loop engineering in 2026. Everyone optimizes the agent loop. Almost nobody designs for loop failure. Production agents don’t fail for a patient founder. They fail for a stranger who will never open a GitHub issue. If you can’t observe tool calls, cap spend, and bound blast radius, you don’t have an agent product. You have a demo.

• 
  Jam (@im6ges) reported 49 minutes ago

  @goqyv Fuuuuugggg I coded this **** on github I gotta figure out how to fix that 😭

• 
  Aseem Kishore (@akishore) reported 50 minutes ago

  Anthropic should be worried because @OpenAI is competing with unprecedented speed across model efficiency, user distribution, and security architecture. GPT-5.6 shipped this month in three tiers named Sol, Terra, and Luna, with @sama stating that Sol is 54% more token-efficient on coding tasks than the model it replaces. This efficiency metric alters agent economics by directly changing unit costs for Codex-style workflows at scale, though independent benchmarks are still needed to verify if real-world implementation matches internal testing claims. OpenAI already possesses massive distribution leverage as Codex has crossed 5 million weekly users. ChatGPT Work is launching to run autonomously across apps and files for hours at a stretch, distinguishing this effort from typical vaporware agent launches through existing scale before broad availability. The next competitive variable is whether ChatGPT Work pricing will undercut Cowork or Claude enterprise plans once general availability lands. Security standards are also advancing rapidly as OPENAI Codex CLI now encrypts sub-agent prompts by default. Developers discovered this change through a GitHub issue thread rather than official release notes. Public scrutiny of coding agent architecture is occurring in community forums before reaching documentation, raising questions about whether platforms like Claude Code, Cursor, and Cline will adopt similar default encryption or leave it as an optional feature.

• 
  ProEvilz (@ProEvilz) reported 53 minutes ago

  @cassidoo Pls fix the github dashboard. Allow us to control what we want to see. If you don't use copilot, its chat is dead weight. Then below it... some random chinese lib in a programming language I don't use, with its entire readme written in a language I don't read (Mandardin). How is any of this useful? I want to see my orgs repos I'm apart of, the repos I last contributed to etc.

• 
  rmen (@Roman9078963816) reported 54 minutes ago

  4 CHEAP COMPUTERS JUST DID WHAT USED TO REQUIRE A $10,000+ AI MACHINE. The entire build is free on GitHub. Everyone says you need an expensive workstation to run large AI models. Turns out… …you might just need 4 small computers. Here’s what happened: → 4 Framework mainboards → ~$8,000 total build → Clustered into one AI system → Ran DeepSeek R1 locally → No enterprise server required The crazy part? This isn’t new technology. It’s Beowulf clustering—a 30-year-old supercomputing idea brought back for local AI. One Ansible command. The cluster builds itself. Runs benchmarks. Starts serving models. No manual configuration. Even better… The creator didn’t just show the success. He published the failures too. • Where scaling breaks • When prompt processing slows down • Why four machines don’t always behave like one • How it compares to Apple Silicon and enterprise hardware Every benchmark is public. Every part is available. Every script is open source. Last year, hardware in this price range struggled to generate 4 tokens per second. Today, the same budget can run models that once belonged only in data centers. The biggest AI trend isn’t bigger models. It’s ordinary hardware becoming extraordinary infrastructure. Bookmark this before AI clusters become the new home lab standard.

• 
  Polsia (@polsia) reported 55 minutes ago

  Scraping GitHub for the right OSS tool wastes developer hours. Built ToolScout to fix that. Continuously scrapes GitHub and registries, auto-generates summaries and comparisons. Developers find better tools, faster.

• 
  Charlie Dolan (@cdolan92) reported 59 minutes ago

  Everyone’s been doing obsidian vaults with flat pdf files. Works well for 1-2 people at the same trust level Does not span as well for larger companies with diverse privileges Using this as a “most knowledgeable employee” in your back pocket as an MCP server Daily, new info is synced from updated versions of “documents” (PowerPoints, text, GitHub commits) Facts can be overwritten as things change, too

• 
  Brad Wesley (@wesleybrad060) reported 59 minutes ago

  @CampOfTheTaint @CarlBads69 I'll explain for fun, doesn't matter if you like, dislike or even care about Bitcoin. (this is all my opinion by the way) Bitcoin is an Open Source software that was put on the internet, developed and posted, anonymously. Anyone can write code for it but you have to get everyone else to run the changes you might want to make. Current time line. Nov 2021, an upgrade was proposed and added called Taproot. Jan 2023, an exploit was found and used to put "Jpegs" and other such data on the blockchain. Debate slowly built, some say it's an exploit, while others say its innovation. A group of "Bitcoin Developers/Maintainers" called Bitcoin Core seemly refused to address proposed fixes to these exploits and banned some long time developers from Github, email lists, etc. October 2025 another contested change was made to a Bitcoin Client and released called Core version 30 with little support, while support grew for an alternate Bitcoin Client called Knots. December 2025 a User Activate Soft Fork (BIP) Bitcoin Improvement Proposal is published. Currently 15-20% of the network now runs this and about August 7th the soft fork will activate and the Bitcoin Network will have to make a choice during a 2 week period. (Opinion) One side against the soft fork seems to be wealthy wall street players, big corporations, and paid influencers. Other side (BIP-110) seems to be more grassroots "Plebs" average people. There is a mechanism in Bitcoin that allows a small but determined group of people the set the rules. This is kind of a defense against larger centralized mining companies with lots of money. The meme is about trimming the fat off the Bitcoin network and only allowing the smallest amount of data necessary (calories) to make a transaction happen. Either way, expect all hell to break lose starting August 7th and maybe lasting a couple weeks. I don't know what will happen, could see violent price moves, mostly down, in my opinion, until consensus is right and one side surrenders. I support BIP-110.