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:

• 
  DemonKingSwarn (@DemonKingSwarn) reported 4 minutes ago

  @ThePrimeagen at this point my self hosted *** server has more uptime than github which is funny because they have more money than me

• 
  validate.qa (@Validate_QA) reported 7 minutes ago

  cursor can now auto-fix ci failures agents that watch github, hunt down the issues, and push prs with real fixes. no more endless debugging loops this changes how fast teams can ship without breaking stuff

• 
  Emedy (@EmedyXBT) reported 8 minutes ago

  @Bybit_Official @BybitAfrica Local virtual dollar cards made perfect sense when you first discovered them. Naira cards were restricted from processing international transactions, which meant apps like Spotify, Amazon, Adobe, GoDaddy, GitHub, and so many others became unreachable. Local fintech apps launched USD-denominated virtual cards within minutes. The problem looked finished. So we used them, recommended them to friends, and kept using them.

• 
  Safal Gautam (@SafalGautam11) reported 9 minutes ago

  Not even able to load github properly lol. Forget about issues and prs.

• 
  Danilo (@Daniel_adsss) reported 12 minutes ago

  Elon just dropped the entire X algorithm on GitHub and the code tells you exactly how to win the For You feed. Grok scores every post based on predicted engagement. Likes, replies, reposts all push you up. Blocks, mutes and reports drag you down. Which means every sharp comment you leave on a big account is training the algorithm to show more people like you that content. 16.5k stars in 24 hours. Developers already pulling it apart.

• 
  Jerome Israel (@jerome_fletcher) reported 13 minutes ago

  github actions down? what's going on 👀

• 
  Adi (@wtfaditya_) reported 14 minutes ago

  As github actions are down, I was thinking what if they were using actions itself to deploy their service, How they gonna fix it (deadlock) And if they are not using github actions then why should i use if they are not using itself @GitHub any help?

• 
  Daniel (@moly_dat) reported 15 minutes ago

  Github seems to be down #github

• 
  Benitto J D (@BenittoJD) reported 17 minutes ago

  Github actions are down again

• 
  Bro Techster (@techstermania) reported 19 minutes ago

  Github issues tonight?

• 
  Erik Goins (@erikgoinsHQ) reported 20 minutes ago

  I built a financial forecasting app for our real estate business. Some take aways: 1. It's incredible what you can do with AI. This took me ~3 days part time. 2. If you're not a dev, good luck... Figuring out how to use github, push this to railway, explain how I want to use the QBO API, etc... there's still a big learning curve here. 3. Domain expertise is still very real. The first version of this was terrible. I had to help the AI create forecasting rules. 4. Businesses (enterprises) are going to need a lot of AI governance. Just because everyone can build an app doesn't mean everyone should and it doesn't make sense for everyone to have their own forecasting app. You really want one well done app, not 100 bad ones. 5. We're not replacing QBO. Too ingrained- it gets to stay the system of record. Looks like there's still a very real moat for the right SaaS products. Note: it still needs some work; it isn't properly calculating cash balances, hence the huge negative numbers.

• 
  René Cannaò (@rene_cannao) reported 20 minutes ago

  @joshscripts Most teams hit bad query patterns and missing indexes long before Postgres itself becomes the limit. Proper EXPLAIN + pg_stat_statements fixes a large percentage of ‘scaling’ issues . Also, since when PostgreSQL powers GitHub? I think this is a very incorrect claim

• 
  Overpower (@Overpowerfeed) reported 21 minutes ago

  @PrinceBuildsAI the "indie dev to openAI acquisition" pipeline is the most efficient data laundering operation in silicon valley history. they don't even have to scrape github anymore, you're literally just paying $20 a month to type your proprietary code directly into their training server.

• 
  Adam Sheldrick (@ECSM_Research) reported 21 minutes ago

  @DimitrisPapail It would be nice to have that problem. I'm currently stuck using Zenodo and Github for my work, as I'm not tied to any institution.. just getting an endorsement for arXiv is a near impossible..

• 
  Aditya Sharma (@aditya_sharma) reported 22 minutes ago

  elon musk dropped the X algorithm on github. i read all 25,000 lines so you don't have to. here's what actually decides your reach. what actually matters - dwell time is the entire game. how long someone pauses on your post is counted twice in the scoring. likes barely move the needle. the pause does. - saves and shares are the highest-value engagement after dwell. they signal the strongest intent. - video has a minimum duration floor. clips shorter than the threshold get zero video credit. five seconds plus, always. - one post per conversation thread survives in any feed. your five-post thread competes with itself. the algorithm picks the strongest one. - replies to big accounts (1000+ followers) get scored on a 0-3 quality scale. high score and you land in the reply panel of viral tweets. low score and you're invisible. - replies to small accounts get a binary spam check only. no quality scoring path. no reach upside. - mutual follow overlap matters. tight clusters of mutuals create reach corridors for everyone in them. - clear topic identity beats vague posting. the algorithm tags your post with topics. clear topics route you to people who follow those topics. - new accounts on the platform get an easier path to reach you than established ones. if you target young/new users, the algorithm is on your side. what kills your reach - posting too often. the algorithm has decay coded in. your second post of the day gets a fraction of your first. your fifth gets almost nothing. - quoting or replying to a flagged tweet. you inherit the badness. your whole post gets dropped even if it's clean. - ai slop. there's a dedicated slop detector that scores your post 1 to 3. high slop = killed reach. - being unclear what your post is about. vague content doesn't match anyone's interests cleanly. - mid-controversial content. it gets pushed away from the high-attention slots in the feed because ads can't sit next to it. - posting your own tweet's reply hoping it boosts the original. only one of them shows up. it might be the reply, not the original. myths to kill - hashtags do nothing. zero boost in the code. they're not even read by the ranker. - premium doesn't get you reach. paid and free accounts go through the same pipeline. - long threads don't beat single posts. the algorithm picks one post per thread. - engagement bait doesn't work. it trips spam classifiers on low-follower accounts. - posting twelve times a day doesn't get twelve impressions. it gets one strong one and eleven weak ones competing with each other. - replying to viral tweets isn't easy reach. the quality bar is high. cheap replies fall straight into the spam path. - timing tricks don't beat ranking. timing helps you enter the candidate pool. quality decides if you win. - external links don't hurt you. clicks are actually one of the 19 positive scoring signals. - the algorithm doesn't hate any specific format. it hates unclear content. format is fine if the content is sharp. - you don't need 10k followers to get reach. the algorithm doesn't read follower count as a scoring input. it reads engagement quality. the playbook - write posts that make people pause for 5+ seconds. dense info, clear structure, screenshots with detail, comparisons. - if you use video, clear the duration floor. always. pick one clear topic per post. don't mix five things into one tweet. - reply to bigger accounts in your niche with substantive, high-effort replies. one good reply beats ten mediocre ones. - build mutuals in tight clusters around your niche. broad spray-follow strategies don't help. focused clustering does. - post 1-2 times a day, not 10. quality compounds, volume decays. - don't quote tweets that look flagged or risky. clean what you cite. - write like a human. don't post ai output verbatim. target newer users on the platform if you can. they have a friendlier reach path for creators. if you're a small account starting out - replies to big accounts in your niche are your highest-leverage move - build a tight mutual cluster of 50-200 accounts in your exact space - one strong post a day beats five medium ones clear topic identity, every single post if you have an established audience - your reach problem is breaking outside your network - dwell time on individual posts is your biggest unused lever - clean brand safety keeps you in prime feed slots next to ads - volume hurts you more as you grow, not less the whole system is built on one bet: that a model fed engagement data can decide relevance better than any rule. there's no hashtag boost, no follower boost, no time-of-day trick in the code. just sequences in, probabilities out. what works is what humans actually want to read. the algorithm is just better at measuring it now.