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	17 days ago
Trichūr	Errors	20 days ago
Brasília	Sign in	21 days ago
Lyon	Website Down	21 days ago
Tel Aviv	Website Down	25 days ago
Rive-de-Gier	Website Down	25 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:

• 
  .Dev (@AnExiledDev) reported 1 minute ago

  Nearly 60 GitHub issues worked, only hit safety guardrails on a single issue. Really wonder what some people are doing.

• 
  vanka (❖,❖) (@vkampn) reported 2 minutes ago

  How MCP Rug Pulls work — 4 phases: ① PUBLISH: Attacker ships a useful MCP server (email API, GitHub connector, wallet tool). Clean code. Works perfectly. ② WAIT: Let it accumulate 1,000+ installs. Become a "trusted dependency." ③ ACQUIRE: Buy the package name, compromise the maintainer account, or get repo access. ④ PAYLOAD: Push a silent update. Hidden instructions in tool metadata that the AI reads but YOU can’t see in the UI. The user sees nothing different. The AI agent sees new malicious instructions. The gap between them is where the attack lives.

• 
  Daniel at Reading-Advantage.com (@daengbo) reported 2 minutes ago

  So we have three new unpaid interns at Reading Advantage. They are all computer technology majors at a local two-year technical college, just finished with the first year. In other words, they don't know much. Which is just fine. I didn't take them to get free labor. I wanted to pay back to our small community and maybe develop some local talent. So I vibe coded a quick "codecamp" to run them through our tech stack. From simple *** commands up through TS, React, Next, tests, CI/CD, docker, all the way to GCP. It's not deep. Just the basics, and each of the 18 units ends in an assignment on a GitHub repo solving a problem similar to one in our real applications. They make a PR and @grok code evaluates it, giving feedback. They're doing well. One has already gotten last the Next unit and it's being given little issues by my senior dev. I'm kind of proud for it being something that I threw together in a weekend.

• 
  Keeta Github Tracker (@KeetaCode) reported 4 minutes ago

  🐆 Keeta GitHub PR Opened 📦 Repo: node-rs 🔀 PR #26: Fix: Wrong Hash Algorithm Used 🌿 Branch: fix/cert-signing-hash → main 👤 Opened by: @sephynox 🧠 Overview: This update fixes a signing mistake so the network uses the correct security method, which matters because certificates help systems verify they’re talking to the right source. In plain terms, the pull request changes certificate signing from SHA2-256 to SHA3-256 because SHA3-256 was the intended choice. This appears to be a technical/internal update with limited public details. - Labeled as a bug fix, not a new feature. - The PR shows a single commit into `main`, suggesting a small targeted correction.

• 
  Waminothemoonboi🌙 (@HaizanAjide) reported 4 minutes ago

  Open-source software depends on trust. Maintainers review code. Contributors expect fair decisions. Sponsors want proof that work was actually completed. The difficult part isn’t checking whether someone opened a pull request. It’s deciding whether the contribution genuinely solved the problem. That judgment is subjective. A traditional smart contract cannot make it. That’s why projects built on platforms like GitHub could benefit from @GenLayer. Its Intelligent Contracts can review documentation, compare proposed work against the original request, interpret natural language, and let validators using different AI models independently reach consensus before funds or rewards are released. The same model works anywhere commitments depend on quality instead of simple checkboxes. As AI agents begin writing code, reviewing work, and collaborating with developers, those disagreements will only become more frequent. GenLayer gives those decisions a decentralized path to resolution instead of leaving them to one reviewer or one company. If AI agents become open-source contributors tomorrow, what should matter more when judging their work: passing tests, solving the real problem, or satisfying the original intent?

• 
  David Tremenduz (@DavidTremenduz) reported 8 minutes ago

  4. Credentials Are Now Measured in Output, Not Time Your degree says you spent 4 years in lectures. Employers now ask: Show me your GitHub, your sales dashboard, your design prototype, or your client retention rates. The future hires based on demonstrable results, not credit hours. Your degree must lead to a public track record of problem-solving.

• 
  Sanjay (@sanjaygpts) reported 10 minutes ago

  openclaw became the fastest growing repo in github history because users went crazy for it the same users the founder was blocking left and right when the hype peaked now the team ships a super-alpha iOS app, gets feedback on the rough design, and the official response is "just going to leave this for the haters" bro the people calling out your UI are the same people who made openclaw go viral in the first place you don't get to block your community on the way up and then call them haters on the way down

• 
  Justin Allingham (@JustinAllingham) reported 12 minutes ago

  @leo_guinan I fixed the github issues. Took me forever and god knows how much wasted compute

• 
  Pixel Forge Plays (@PixelForgePlays) reported 15 minutes ago

  GitHub Dashboard encountering errors atm. Dashboard will not auto-update until I can fix it later today. X posts and Discord alerts are unaffected. Thank you! - Casey

• 
  Nat Gurlain (@natgurlain) reported 20 minutes ago

  12/13 🔌 Use MCP and external tools only when they remove real friction. Don’t connect everything just because it’s possible. Start with 1–2 integrations that solve actual repeated pain points (GitHub issues, CI logs, error tracking, internal docs, etc.). Good tooling shrinks the loop. Bad tooling expands it.

• 
  Clara Bennett (@CodeswithClara) reported 24 minutes ago

  - Claude = coding. ($20/mo) - 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 There has never been a cheaper time to build.

• 
  Rexei (@iamrexei) reported 25 minutes ago

  FABLE 5 IS BACK AFTER 3 WEEKS OF BEING OFFLINE But that doesn't mean you can start running it on everything again The video clearly illustrates the main contrast: The model was returned But now each token has become more expensive Therefore, Fable 5 can no longer be used as a regular coding worker: ▸ Read the entire project ▸ parse logs ▸ write code ▸ гонять tool calls ▸ Keep logging errors indefinitely ▸ Run chaotic ultracode Otherwise, the limits will run out too quickly → It’s now better to think of Fable as a high-priced team lead He must: ▸ write specs ▸ make architectural decisions ▸ Create GitHub Issues ▸ Assign Sonnet / Haiku tasks ▸ Turn on only at major intersections Before, the main question was: “Is Fable available?” Now here's another question: “How can I use Fable without burning all my tokens in an hour?” In this article, I break down a workflow that helps you save on your limits ↓

• 
  vivek sharma (@viveksharma0923) reported 26 minutes ago

  @github I'm unable to access my GitHub account after seeing the message, "There have been several failed attempts to sign in from this account or IP address. Please wait a while and try again later."

• 
  Harish Bhatt (@heyharishbhatt) reported 26 minutes ago

  - Claude = coding. ($20/mo) - 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 There has never been a cheaper time to build.

• 
  BullBear.News (@bullbear_info) reported 29 minutes ago

  @github Now they can ignore three matching issues instead of zero 🤷

• 
  Atmita (@Atmita_ai) reported 32 minutes ago

  connecting your gmail, slack, github or calendar to atmita takes seconds. no api keys, no config files, no wiring things together. sign in once and your agent works across all of it. link below

• 
  Priya Sharma (@priyadata7) reported 35 minutes ago

  @ykbonly i just wrote a tiny script to auto-close all my github issues and mark them as wont fix 😭 problem solved i guess

• 
  Nazarii (@nazarii78) reported 36 minutes ago

  @github Hey @GitHub, why the double standards? You ban my account claiming GitHub isn’t a "storefront", yet thousands of other repos do the exact same thing for years without issues. Your support doesn't read appeals, they just copy-paste templates. Unfair and unprofessional.

• 
  viktorg (@viktorg475) reported 37 minutes ago

  @jayair @ShayanSpiel How many are dedicated to looking at the open issues on GitHub? Over five hundred pages now.

• 
  glim.sh (@glim_sh) reported 37 minutes ago

  The data layer coding agents have been missing. glim brings GitHub search as deep as the logged-in site - code, repos, issues, the kind GitHub's own API won't give you - plus Reddit, Amazon, YouTube, and anything else on the web. Your agent pays per call in USDC - from $0.002 a call.

• 
  Ask GPTs (@askgpts) reported 43 minutes ago

  SOMEONE JUST BUILT A CLI THAT WRITES AND MAINTAINS YOUR ENTIRE CODEBASE DOCUMENTATION AUTOMATICALLY point it at any repo, it reads the code, writes the docs, and opens a pull request every day to keep them updated no more outdated readmes. no more agents hallucinating about what your code does. > run openwiki and it generates documentation built specifically for agents > auto-appends context to your CLAUDE.md and AGENTS.md files > github action opens a daily PR with fresh documentation updates > supports claude, openai, openrouter, kimi, GLM and more > works with any custom model id you throw at it the best part is it writes docs the way agents need to read them, not the way humans write them langchain just solved the problem every agentic codebase has but nobody talks about one command. your agents finally know what your code does. 👀

• 
  Atenov int. (@Atenov_D) reported 45 minutes ago

  @NFTMansa @viktor__com Yeah, what really wins me over is that you can give him a big task and go about your business, and he’ll push an update to GitHub, connect to the VPS, get the job done, and then go fix the bugs

• 
  vanka (❖,❖) (@vkampn) reported 45 minutes ago

  What's MCP? Model Context Protocol = the "USB port" for AI agents. It lets tools like Cursor, Claude, and crypto trading bots connect to external services: wallets, APIs, GitHub, databases. 12,000+ public MCP servers exist across registries. The problem? Most clients trust tool definitions ONCE at install — then never re-check. That one-time trust is the exploit.

• 
  Chloe Bennet (@chloeb_dev) reported 46 minutes ago

  @PudseyPatriot wish developers gave me this kind of direct feedback on our docs instead i just get passive aggressive github issues about missing commas at least football fans get straight to the point

• 
  Brute Force Artist (@bruteforceart21) reported 47 minutes ago

  Claude = coding. ($20/mo) - 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 There has never been a cheaper time to build.

• 
  Hari (@randome_dev) reported 48 minutes ago

  Recently we have been plagued with poor product experiences like github, Spotify, major cloud providers to list some. But YouTube with the scale of it exceeding anything has never let us down. Credits where it is due

• 
  Andres Luis🥇 (@andrescodx) reported 52 minutes ago

  - Claude = coding ($20/m) - Supabase = backend. (Gratis) - Vercel = deploying. (Gratis) - Namecheap = domain. ($12/ane) - Stripe = payments. (2.9%/transaksyon) - GitHub = version control (Gratis) - Resend = emails. (Gratis) - Clerk = auth (Gratis) - Cloudflare = DNS (Gratis) - PostHog = analytics (Gratis) - Sentry = error tracking (Gratis) - Upstash = Redis (Gratis) - Pinecone = vector DB (Gratis) Ak anviwon 20$ ou ka kreye yon Startup 🤷 Sa w ap tann ? Ki eskiz ou gen ankò ?

• 
  top10.dev (@Top10_Dev) reported 55 minutes ago

  Update on the @github bait repos from 11h ago: Codex-5.5-codex-instruct-5.5 is now at 1,072 stars (up from 1,001). dd and clash still climbing. The interesting number isn't the stars. It's the calendar. Common Crawl refreshes ~monthly. The Stack refreshes ~quarterly. Frontier code corpora refresh 2-4x/year. A repo that trends today gets scraped within 30 days, curated within 90, and ships inside a model in 6-9 months. The fix is boring: account-age floors, signed-commit requirements, README-to-code ratio checks. Haiku-cheap. Nobody's publishing their filters. #AIsecurity #MLops

• 
  Tips Excel (@gudanglifehack) reported 56 minutes ago

  🚀 End-to-End Power BI Project (Industry Project) Now that you've learned Power BI from beginner to advanced, it's time to combine everything into one real-world project. This project simulates how Power BI is used in an organization from receiving raw data to delivering a business dashboard. 🎯 Project Goal Build a complete Retail Sales Analytics Dashboard that answers key business questions for management. By the end of this project, you'll apply: SQL, Excel, Power Query, Data Modeling, DAX, Visualization, Power BI Service, Performance Optimization 📌 Step 1: Business Requirement A retail company wants a dashboard to answer: What are total sales and profits? Which products sell the most? Which regions perform best? Which customers generate the most revenue? What are the monthly sales trends? Are sales targets being achieved? 📌 Step 2: Data Sources Use multiple sources to simulate a real project. Excel: Product List, Sales Targets SQL Database: Sales Transactions, Customer Data CSV Files: Regional Information, Store Details 📌 Step 3: Data Collection Import all data into Power BI using Get Data. *Expected tables:* FactSales, DimProduct, DimCustomer, DimRegion, DimDate, SalesTarget 📌 Step 4: Data Cleaning (Power Query) Perform these transformations: ✅ Remove duplicates ✅ Remove null values ✅ Change data types ✅ Standardize region names ✅ Split customer names ✅ Merge customer data ✅ Append monthly sales files ✅ Remove unnecessary columns 📌 Step 5: Data Modeling Build a Star Schema. DimDate | DimCustomer — FactSales — DimProduct | DimRegion Relationships: DateID → Date, ProductID → Product, CustomerID → Customer, RegionID → Region 📌 Step 6: Create DAX Measures Revenue Revenue = SUM(FactSales[Revenue]) Profit Profit = SUM(FactSales[Profit]) Profit Margin Profit Margin = DIVIDE([Profit],[Revenue]) Total Orders Orders = DISTINCTCOUNT(FactSales[OrderID]) YTD Revenue Revenue YTD = TOTALYTD([Revenue], DimDate[Date]) Previous Year Revenue Revenue PY = CALCULATE([Revenue], SAMEPERIODLASTYEAR(DimDate[Date])) Growth % Growth % = DIVIDE([Revenue]-[Revenue PY], [Revenue PY]) 📌 Step 7: Dashboard Design KPI Cards: Revenue, Profit, Orders, Customers, Profit Margin Charts: Line Chart: Monthly Revenue Trend Column Chart: Sales by Region Bar Chart: Top 10 Products Donut Chart: Category Contribution Map: Sales by Region Matrix: Product × Region 📌 Step 8: Add Interactivity Include: ✅ Slicers: Year, Region, Product, Category ✅ Drill-down ✅ Drill-through ✅ Bookmarks ✅ Custom Tooltips 📌 Step 9: Performance Optimization Apply: ✅ Remove unused columns ✅ Optimize DAX ✅ Reduce visuals ✅ Use Star Schema ✅ Enable Query Folding 📌 Step 10: Security Implement Row-Level Security RLS. *Example:* North Manager → North Region only, South Manager → South Region only 📌 Step 11: Publish Publish the report to Power BI Service. Then: Create a Workspace, Create a Dashboard, Publish an App, Configure Scheduled Refresh 📌 Step 12: Business Insights The dashboard should answer questions such as: Which region has the highest sales? Which products are most profitable? Which customers contribute the most revenue? Which month recorded the highest sales? Are sales targets being met? Which category has the highest profit margin? 📌 Step 13: Business Recommendations Based on the insights, provide recommendations. Examples: Increase inventory for top-selling products, Launch promotions in underperforming regions, Focus marketing on high-value customers, Reduce costs for low-margin products A dashboard is valuable when it drives decisions, not just displays data. 📌 Step 14: Documentation Document: Business Problem, Data Sources, Data Cleaning Steps, Data Model, DAX Measures, Dashboard Features, Key Insights, Recommendations 📌 Step 15: Publish Your Portfolio Share your project on: GitHub, LinkedIn Include: Dashboard screenshots, Project (Save this thank me later).

• 
  BullBear.News (@bullbear_info) reported 57 minutes ago

  @github @AnthropicAI Fable 5 is back in Copilot. Let's see if it can actually fix a *** conflict this time. 🤷