GitHub seems pretty slow for me this morning | Hacker News Reader

GitHub seems pretty slow for me this morning

4 pointsjsingleton5 comments

A quick look at status.github.com shows a spike for time to first byte. So don't worry if you're having issues. It's not just you.

View on HN

this is my ping: $ ping github.com PING github.com (192.30.252.131): 56 data bytes 64 bytes from 192.30.252.131: icmp_seq=0 ttl=48 time=101.542 ms 64 bytes from 192.30.252.131: icmp_seq=1 ttl=48 time=102.449 ms 64 bytes from 192.30.252.131: icmp_seq=2 ttl=48 time=101.219 ms 64 bytes from 192.30.252.131: icmp_seq=3 ttl=48 time=100.985 ms 64 bytes from 192.30.252.131: icmp_seq=4 ttl=48 time=101.502 ms 64 bytes from 192.30.252.131: icmp_seq=5 ttl=46 time=101.458 ms 64 bytes from 192.30.252.131: icmp_seq=6 ttl=46 time=101.489 ms 64 bytes from 192.30.252.131: icmp_seq=7 ttl=46 time=101.400 ms 64 bytes from 192.30.252.131: icmp_seq=8 ttl=46 time=101.400 ms 64 bytes from 192.30.252.131: icmp_seq=9 ttl=46 time=101.385 ms 64 bytes from 192.30.252.131: icmp_seq=10 ttl=46 time=101.384 ms 64 bytes from 192.30.252.131: icmp_seq=11 ttl=46 time=101.571 ms Request timeout for icmp_seq 12 Request timeout for icmp_seq 13 Request timeout for icmp_seq 14 Request timeout for icmp_seq 15 Request timeout for icmp_seq 16 Request timeout for icmp_seq 17 Request timeout for icmp_seq 18 Request timeout for icmp_seq 19 Request timeout for icmp_seq 20 92 bytes from 192.30.252.203: Time to live exceeded Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 5400 9201 0 0000 01 01 3d96 192.168.108.199 192.30.252.131

Something is grinding over there. Page build failures were at 100%, exceptions shot up and 3.5 seconds to start loading a page.

Might be showing signs of recovery though. Build failures are down. But that could be because there are no builds now!

Hopefully just a blip.

Edit:

  We are investigating reports of connectivity problems.

https://twitter.com/githubstatus/status/636110568911409152

It's a DDOS attack against them: https://status.github.com/messages

fatal: unable to access 'https://github.com/SOMETHING/': TCP connection reset by peer. Yeah - that's pretty bad

Now dropping a lot of connections, status looks not good..

Reply on news.ycombinator.com