4 ms·
How do we know it's a DDOS and not some sort of operational failure? Mods should change the title until it is confirmed.
by rubiquity 11y ago
How do we know it's a DDOS and not some sort of operational failure? Mods should change the title until it is confirmed.
- paulannesley 11y agoAgreed. Exact text on status page right now: > 20:51 PDT - We are investigating reports of connectivity issues to GitHub.com. No mention of DoS or DDoS.
- dang 11y agoOk, we changed the title from "GitHub under DDOS."
- cft 11y agoLook at the traceroute. This is a DDoS mitigated via Prolexic.
- BradRuderman 11y agoWouldn't the traffic run through to Prolexic regardless if it was under a DDOS or not?
- cft 11y agoTypically, DDoS mitigation services offer a limited number of 48-72 hour mitigations per year (can be a large number, depending on the contract). Outside of these periods the traffic is not routed via them.
- BradRuderman 11y agoHow does that work? Does the DDOS mitigation software change DNS and if so how can it change the DNS in the middle of an attack assuming the attackers?
- cft 11y agoOnly very basic DNS mitigations services have you change DNS and proxy through them. Predictably GitHub is not using one of those. If you really want to protect your service (your own DNS or say SMTP, WebSockets, TCP), then you need to change the internet routing. This is done via BGP announcements of your IP subnets, such that you announce your inbound routes via the mitigation providers. The providers scrub the traffic and deliver clean traffic via a GRE tunnel to your routers. The outbound traffic is routed directly via your upstream providers.