Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Major Service Outage

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 85 posts

Re: GitHub Major Service Outage

#34

Post by i336_ »

yeukhon wrote: post #29
i336_ wrote: post #11

Earlier quoted context omitted.

I've noticed this behavior with a lot of services. I can only chalk it up to something like clock drift between the processing node and the database server. Irritatingly I can't remember which site it was but I posted something somewhere a couple days ago and immediately after hitting enter the site marked what I'd said as submitted "a few seconds from now". I never fail to be amused that the fuzzy time library being…

Git timestamp can be set with different timezone so technically GitHub can analzye the timestamp (which they do) and compare with the actual clock of timezone. There's only a small problem though: the latency from the clock check server must be low otherwise we would be 1 second ahead by the time we get response and then another second or two after webpage render. So from a UX we should simply discount time drift +-5…

Wow, interesting. This info is definitely filed away, thanks.

I don't quite remember but I think I might've been commenting on something on GitHub when I saw the time glitch.

Initially for a moment I thought "why not just have OCD local NTP tracking?" but then I realized that time glitching around (even at the millisecond level) can be disastrous. One way to solve this is to obsess about keeping up to date with NTP, but instead of updating the time, update a global reference to the offset. Then your time server is simply (system date)+-(saved offset), which should be super fast. And of course this can run on the node generating the HTML.

Re: GitHub Major Service Outage

#36

Post by richardwhiuk »

apeace wrote: post #30

As others have said, Github's postmortems are always great. But frankly, I'd rather they have better uptime. Every couple months is too much. I pay them. My work pays them. If their CEO is serious about zero downtime, how about he offers his paying customers a credit for time they cannot access the service?

They are? https://status.github.com/messages/2017-01-18 has a bunch of major service outages and no link to any post-mortem.

The vague rumour always seems to be 'DDoS attack I guess' but there's very little in the way of formal reporting as far as I can tell...

Re: GitHub Major Service Outage

#37

Post by Thaxll »

apeace wrote: post #30

As others have said, Github's postmortems are always great. But frankly, I'd rather they have better uptime. Every couple months is too much. I pay them. My work pays them. If their CEO is serious about zero downtime, how about he offers his paying customers a credit for time they cannot access the service?

Use on prem.

https://enterprise.github.com/faq

Re: GitHub Major Service Outage

#39

Post by Xylakant »

apeace wrote: post #30

As others have said, Github's postmortems are always great. But frankly, I'd rather they have better uptime. Every couple months is too much. I pay them. My work pays them. If their CEO is serious about zero downtime, how about he offers his paying customers a credit for time they cannot access the service?

> I pay them. My work pays them.

Hmm. You pay them to uphold a contract. What does that contract say about SLAs and availability? Probably the same as the TOS that I agreed to when paying and those specifically say:

    GitHub does not warrant that the Service will meet your requirements; 
    that the Service will be uninterrupted, timely, secure, or error-free; 
    that the information provided through the Service is accurate, reliable or 
    correct; that any defects or errors will be corrected; that the Service will 
    be available at any particular time or location; or that the Service is free 
    of viruses or other harmful components. You assume full responsibility and 
    risk of loss resulting from your downloading and/or use of files, 
    information, content or other material obtained from the Service.
If you negotiate, you might get better terms and guarantees, for example with github enterprise. You might also have to pay substantially more for those.

I understand, it sucks when github is down. But we all get what we pay for and we all don't want to pay for more. And yes, I do have clients that meticulously mirror all their dependencies from outside sources and spend significant money on this - money that pays off in exactly these situations.

Re: GitHub Major Service Outage

#40

Post by xrjn »

edoceo wrote: post #35
JohnHaugeland wrote: post #32

feel free to make a better one

It's called GitLab. Not 100% uptime but better (and constantly improving)

Gitlab does not have features parity with Github. I personally also stumbled upon a bizzare bug that doesn't allow a friend to add me to any of his private repo's. Asked on IRC and nothing much came of it unfortunately.
Post reply on HN