6 ms·
GitHub connectivity issues
- msoad 11y agoIt's completely unusable for me :(
- vonklaus 11y agowow I knew it. Everything is absolutely crawling. I am trying to push up my repo and get some packages. I could tell something was definitely up. Damn it. Thanks for the update.
- rubiquity 11y agoHow 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.
- sgloutnikov 11y agoCouldn't push, so came here to find out it wasn't only me. 'Server aborted the SSL handshake' Edit: seems back to normal now
- smaili 11y agoLooks like I wasn't the only one! Wonder who's behind this one.
- titomc 11y agoworks for me now.
- hueving 11y agoThis is likely due to the new algorithm they chose to select backend servers that no longer considers response time because it was too meritocratic. The load balancing algorithms now are mainly based on ensuring that all different server types are equally represented, rather than selecting for high performance.
- KB1JWQ 11y agoThis type of comment isn't helpful.
- hueving 11y agoWell it's not really surprising that an organization which does not value technical skill is having stability issues.
- zorpner 11y agoTechnical skill is systemically undervalued, by people who preferentially hire other people who look like them, went to school with them, and don't make them uncomfortable. Diversity increases average technical ability, every way you measure it. This is why accelerators like YC, who have access to performance data for a wide range of companies, are interested in diversity efforts.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- andrewguenther 11y agoWhat I actually find more interesting is the spike in hook delivery time that correlated with the spike in exception rate. My guess would be that some hooks were timing out which possibly causes an internal exception? Maybe? It is interesting that they would include timeouts of external services in their exception count. Purely speculation though.
- adrianmacneil 11y agoRuby with resque/sidekiq will definitely cause an exception if an http call fails or times out. This is what causes it to end up back in the job queue.
- TuringNYC 11y agoI'm working on GMT+3, and our work-day starts at 7am. Sort of sucks to have my core work hours be the typical SFO downtime slot...
- TuringNYC 11y agoI'm working on GMT+3, and our work-day starts at 7am. Sort of sucks to have my core work hours be the typical SFO downtime slot...
- slacka 11y ago00:38 Eastern Standard Time All systems reporting at 100%. https://status.github.com/messages https://status.github.com/messages