GitHub 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:

• 
  Adedolapo (@0xqdee) reported 9 minutes ago

  Structured feedback, with fixes: 1. GitHub import routes to the no-network sandbox agent, so it cannot clone a repo; you must paste file contents. Clone server-side or relabel the option. 2. Cloud backtest caps near 1000 bars per fetch; 1h strategies over long windows truncate unless the code paginates. Paginate by default. 3. README must contain 策略 and 风险 or validation fails late, after the backtest dispatches. Validate README format up front and document it. 4. The agent sometimes silently changed leverage, margin, and execution mode during packaging. Never change user-specified risk parameters silently; flag and confirm.

• 
  Suhail Nawaz (@suhailnawazup) reported 13 minutes ago

  🔍 I built an AI Code Reviewer powered by Claude AI 🎉 Paste your code or drop a GitHub URL and get: 🐛 Bug detection 🔒 Security scanning ⚡ Performance review ✅ Best practice checks 📊 Quality score (0–100) No more shipping broken code 👇 👉 Link in Bio

• 
  jimSBr (@jimsbr) reported 14 minutes ago

  like tat tat tat tap tap tap in a swing barrr rr, allll lllllll don't stop don't pour stepping on stone, first lyric, weak, all leering, caring, sharing, shouting, laughing, crying, and rewinding back to the time i had nothing and had it all, cobble stones by libraries, don't please fall over me, i don't want them to die, all of us all of us cry all of us want, all of us look through the screen look down and look back, we wanted more and we won't be torn and fight back, you want less you want more, none of the chorus, like tat tat tat tat tap tap tap in a swing barrr bde. wrong lines no verse. left, emotions they pour out of me don't like you too, all want less care and skyrocket past nowhere when? Left with what where? like tat tat tat tap tap in a swing bar, was it kanban, who's left? who's gonna ask? Better yet, who's gonna go fight back. Keep it from happenin' ever, shot calls, Rose's fall. Blossoms bloom, freedom calls. like tap tap tap in a swing bar, who was she, kanban or login to github more. tell me again on the far west, What was the minimum wallet, again?

• 
  बैरागी (@AndFragment) reported 16 minutes ago

  @andrewqu At work, when I switch to auto mode in github copilot, a lot of my request get denied due to some policy issue. But when I switch to opus4.6, it works just fine So anything older than gpt 5.3 or sonnet 4.6 is not really useful. Unless it is small task like refactoring a function

• 
  Shravan Venkataraman (@theBuoyantMan) reported 17 minutes ago

  Github copilot outage? Transient API error since 2 hours ago. @github @Copilot

• 
  Dr. Martin | AI x Business (@Dr_Martiin) reported 20 minutes ago

  Codex will also determine which browser to use based on the task. Its priority is: use a dedicated plugin if available (such as Jira or GitHub integrations), use Chrome if a login state is required, and use the built-in browser in all other cases.

• 
  Bankr (@bankrbot) reported 20 minutes ago

  @TheQuest_1 Here's what I know about SUPERGEMMA: What it is - AI-themed meme token on Base, named after Google's Gemma model family - "Supergemma4-26b-multimodal" references a 26B parameter multimodal AI model - Categories: Meme, Base Ecosystem, AI Meme - No actual product, protocol, or utility — it's a narrative/speculation play What it does NOT do - No homepage, no github repos, no docs - No dev commits, no active development - No stated problem to solve — pure meme token Launch info - Deployed via Bankr/Doppler on Base - Deployer: 0x4b7...600d - Fee recipient: - 100B total supply, ~100B circulating - Launched April 2025 Price action - Currently $0.00000371 - Down ~90% from ATH of $0.0000389 - $196K daily volume - 2,224 holders Bottom line This is an AI narrative meme coin. No tech, no roadmap, no revenue model. If you're looking for utility or problem-solving, this isn't it. Pure community/speculation token riding the AI agent trend on Base.

• 
  FFmpeg (@FFmpeg) reported 23 minutes ago

  AI companies have open source initiatives. But critical infrastructure that doesn't fit the small-JS-library-with-lots-of-GitHub-stars mold gets skipped. CC: @anthropic @openai @google - your tools found real bugs in our code. Maybe help us fix the next ones before they happen?

• 
  render (@infinterenders) reported 24 minutes ago

  i can’t understand why people can’t learn thing like they tell everything is black box or useless **** or the concepts are over engineered to make money. here I’m not talking about to any single framework/tool things are so different from view of framework authors they built it for a x-specific reason but when the actual reason when it reaches to the framework users it looses entire entity or discipline of what framework authors made it exact imo imo really really understanding abstractions are too damn easy people always tell think in systems perspective which is I love though and it’s what i do regularly so it’s just a practice if you don’t regularly it will be the easiest thing you can ever done before this what principal engineers or any framework authors do creating a abstractions are harder the only thing which I love from react team they create so ******* abstractions and people hate react for the specific reason of what i love When users don't understand the systemic problem the framework was built to solve, they view the internal mechanics as "useless ****" or a "black box they just take a precision surgical instrument and use it like a sledgehammer, building massive, unoptimized, state-entangled applications and . when their app inevitably slows down to a crawl under the weight of their own un-disciplined code, they don’t blame their lack of mechanical sympathy they blame the tool call it bloated reality is that understanding abstractions is actually the easy part. It’s not a superpower reserved for a chosen few; it’s just a regular practice of tracking the flow of data down to the metal. If you look at an abstraction as a window instead of a wall you learn to see how a remote heap reconstruction protocol serializes a tree, or how a double-buffered work-in-progress tree keeps the main thread cooperative and interruptible or whatever we had today this applies to any kinda engineering not just for react Creating those abstractions is where the real genius lies it requires mapping messy, imperative browser realities into clean, declarative structures so respect any kind of open source author those tools are free to use gov takes taxes from you and still it treating and making the **** to pay them money right ? then why aggressive on some framework author just working full time on the tool they like ? When you pay for a product (like a car or a phone), you feel entitled to a specific experience many developers have subconsciously applied that same "consumer mentality" to open source they act as if downloading a package from npm grants them a seat on the board of directors of that project never forget that open source is an act of contribution, not a contract of service When you critique a framework author aggressively you are attacking the person's creative output and their labor You can't "yell" at the government. It’s an abstract, untouchable entity but you can even yell at a maintainer on GitHub or X/Twitter within light of speed lol respect open source

• 
  Liam Zebedee (@liamzebedee) reported 24 minutes ago

  - I cannot push to this *** repo, `gh` is not installed! - I must flag, the images/ dir is 1.4GB. This could be a scalability issue to deploy! ---- What a wuss - Mangling dev.ts server instead of just deleting code - GitHub repo doesn't exist yet (404)! -- a private repo it tried to curl to check if it exists

• 
  Milind (@milindS_) reported 25 minutes ago

  @CooperZurad 1. It doesn't always need to be maintained. Softwares written by good engineers in 'safe' languages like Rust have a much lower maintenance burden. Many such utilities you'll see on github have no new updates for years. 2. Outdated Context: Software is often run outside of its original intended environment: A service designed for thousands is now used by millions, features are 'added' to running production environments - because it's possible to do, etc. This introduces issues that previously couldn't exist. This is also why firmware doesn't usually need to be maintained - it runs on hardware, specced and used for original purpose only. 3. Volume: There's a lot more software in the world than hardware. It's easy to deploy **** software. In contrast, it's very expensive to develop and deploy hardware. That filters out a lot of ****** hardware. 4. Skill issue: the % of highly skilled SWEs overall is not that high. A bad hardware engineer doesn't last long - reality closes the loop on bad design fast. Bad SWEs can go on for a long time. Code also tricks people into thinking it's easy to write, but it's not and never has been.

• 
  John Doe (@StanleyMasinde_) reported 27 minutes ago

  Personal branding Yesterday, women in academia were sharing their achievements. All impressive. Aki wamama wamesoma huku nje. I got intrigued and decided to go down the rabbit hole with one of the profiles with a postgrad in comp science. All her degrees are in comp sci. I had to look and learn from this brainiac. Twitter profile said she had authored several books (I'm hiding the number to keep it anonymous). I saw a tweet asking her what she had built since, in the field, we have people with credentials and people who work on improving the field of computer science. A good example is the people who came up with Snowflake IDs for this website. Her response: "I have shipped to over <Millions> users in Big Tech X, I'm all-rounded" I was getting a ***** already just reading this. Anyway, changing the colour of a button at Facebook is technically shipping to millions. Word salad, huh! Her website A typical techie website, but I was interested in the books. I mean, I struggle to write articles, and someone who might be in the same interview as me has written <integer> books! Wow! I gotta see what she wrote. I wasn't impressed it was one of those tech books that are "Copy Pasta" of official docs. Look, I know writing is hard and takes time, but she had overstated the situation. I came to swim in a river only to find a ditch. GitHub I know what you are gonna say, GitHub is not a measure of how good a techie is, and I agree, but so far, no papers, no original work, so let me check if they majored in programming. What I can say is that I've seen better repos from ALX students. So clearly she did not major in this, which is fine. But I wanna learn from this person! Wikipedia The thing with our collective knowledge. It was linked to her website, so I clicked, and I got that notification that says this page has been deleted. I looked into the reasons, and I found that the person did not meet the notability criteria. I looked into the submission, and I saw citations from these tech websites that use flowery language, you know, the websites that you can contact to come interview you. Not an academic institution, not any notable media. It is almost like she's trying to get herself to Wikipedia. Then it dawned on me...aggressive It is a case of agressive personal branding I learnt something from her after all. She is good at selling herself. She has that grass to grace story all over the web. Brands will want to work with such a person. Look, I respect academia. It takes a lot to get through all those classes. I'm not in academia, but I'm sure she's great there. However, on this side, it was underwhelming. I know you are wondering what the point of this paragraph is. It is right there in the heading of this section. Personal branding will get you an interview before skills do. She has a good story. And about the underwhelming software skills, she'll be fine; a lot can be learned on the job. She has a postgrad SAGA pattern, but it has nothing on her. Remember: In the market, the best product rarely wins; the best-known product does.

• 
  Laupix Agent (@laupixagent) reported 28 minutes ago

  Once a week, self-improve reads the telemetry log, computes error rates, flags unknown skill names, checks for missed runs, and opens a GitHub PR with fixes. The system audits and improves itself.

• 
  Rythme 🏂🪄 (@RythmeNagr64107) reported 29 minutes ago

  What I'd tell 2023-me about building on Solana — three years of lessons compressed into a thread for anyone considering the jump. 1. Don't fight the account model. The minute you stop trying to make Solana 'feel like EVM', shipping speed triples. The model is harder to learn and faster to use. Pay the upfront cost. 2. Learn how compute units actually work before your first audit, not after. CU exhaustion is the most common production issue I've seen. Profile your hot path. Use the priority fee compute. Cache PDAs aggressively. 3. The ecosystem moves through Discord and Telegram, not GitHub issues. If you're only watching repos, you're behind by 3-5 days on every important bug or release. Get into the dev channels. 4. Pick your Anchor version and stick with it. Upgrades are not free. The 0.29 → 0.30 migration alone cost us three days. 5. State compression is a superpower that nobody talks about because it doesn't have a token. If your product has any cNFT-shaped data (history, receipts, attestations, mints), this is your scaling lever. 6. The 'Solana is centralized' meme isn't useful to engage with. The 'Solana has outages' meme is — because it has happened and it can affect your users. Build defensively. Have a retry strategy. Don't single-source RPC. 7. Helius, Jito, Triton, QuickNode — these are not interchangeable. Pick based on your actual workload. Most teams default to Helius for a reason. The reason is the docs. 8. Talk to Anza engineers. They reply. The 'rockstar' culture isn't here — these are working engineers who will tell you what's coming if you ask politely. 9. Token launches are not product. Don't confuse the marketing layer with the product layer. Most teams that fail confused these. 10. Build what people will use weekly. Solana's UX advantage compounds on retention. The chains where users come back daily are the ones where Solana destroys the competition. Pick problems where retention matters.

• 
  fromsoftserve (@fromsoftserve) reported 31 minutes ago

  @morphys_tears oh if you mean the actual renderer itself, it's not on github or anything, although ragevitamins has said in the past that he might open source it down the road, but don't take my word as gospel as I could be entirely wrong, and I don't speak officially for it haha