The first portion of the attack against the developer platform peaked at 1.35Tbps, and there was a second 400Gbps spike later.
In a post on its engineering blog, the developer platform said that, on Feb.
Then, the attacker spoofs the "get" request message with a target's source IP, and thus, a short request to the exposed server can result in a pile of traffic arriving at the victim.
GitHub said that, because of the scale of the attack, it decided to move traffic to Akamai, which could help provide additional edge network capacity.
It said it is now investigating the use of its monitoring infrastructure to automate enabling DDoS mitigation providers and will continue to measure its response times to incidents like this -- with a goal of reducing mean time to recovery.