Salesforce Q1 FY2027 Earnings Beat Expectations Despite Soft Q2 Revenue Outlook 
SpaceX Starship V3 Test Flight Boosts IPO Momentum Ahead of Historic Market Debut 
Samsung Workers Approve Wage Deal, Avoiding Major Strike and Boosting Chip Supply Confidence 
HP Q2 2026 Earnings Beat Expectations Despite Memory Chip Pressure 
Samsung Union Dispute Escalates Over Semiconductor Bonus Vote 
Kentucky School District Secures $27 Million in Social Media Addiction Lawsuit Settlements 
SK Hynix Joins $1 Trillion Club as AI Chip Demand Fuels Stock Surge 
Synopsys Q2 FY2026 Earnings Beat Driven by AI and Semiconductor Demand 
SpaceX Delays Starship V3 Launch Ahead of Potential Record IPO 
Xiaomi Shares Drop After Weak Q1 Earnings Amid Rising Smartphone Costs 
Mega IPOs Like SpaceX and OpenAI Could Reshape S&P 500 and Nasdaq 100 Portfolios in 2026 
Elon Musk Explores Possible Tesla-SpaceX Merger Amid Growing AI Investments 
Snowflake Stock Soars 30% After Q1 Earnings Beat and Major AWS AI Partnership 
MongoDB Q1 FY2027 Earnings Beat Expectations, Raises Full-Year Outlook 
Samsung to Invest $1.5 Billion in Vietnam Semiconductor Testing Plant by 2027 
Meta AI Push Could Add $26 Billion in Revenue by 2027, Wolfe Research Says 
Distributed denial of service (DDoS) has been a problem for years and it would seem that GitHub just got hit by the biggest attack using the tactic in history. While this development is already disturbing enough, it might be possible that the perpetrators were only using this opportunity to test a bigger, more effective weapon in their arsenal. An even bigger attack could be on the way.
According to the site, the attack came in two waves, the first being worth 1.35Tbps, which would have been enough to overwhelm most domains’ servers. The second was smaller, at 400Gbps, but it would still have been enough to do some damage. As ZDNet points, the biggest DDoS attack before this incident clocked in at 1.1Tbps, which makes GitHub a winner of sorts.
On its engineering page, GitHub provided users with details with regards to the incident and reassured users that no data was compromised during the attack. Based on its own record, it would seem that the attack only caused minor inconvenience and only a short downtime, lasting only a few minutes.
“On Wednesday, February 28, 2018 GitHub.com was unavailable from 17:21 to 17:26 UTC and intermittently unavailable from 17:26 to 17:30 UTC due to a distributed denial-of-service (DDoS) attack. We understand how much you rely on GitHub and we know the availability of our service is of critical importance to our users. To note, at no point was the confidentiality or integrity of your data at risk. We are sorry for the impact of this incident and would like to describe the event, the efforts we’ve taken to drive availability, and how we aim to improve response and mitigation moving forward,” GitHub wrote.
As to what makes this particular attack unique, it would seem that the perpetrators used memcached traffic that’s based on UDP, which amplified the power of the DDoS strike. The two consecutive strikes were basically meant to take advantage of vulnerabilities in this particular aspect. According to security firm Akamai, this incident revealed a new method of attack for hackers, which could make it more popular.
