3 ms·
My problem with a credit is that it never even comes close to what I'm losing in income. An ISP is an excellent example. I might get a $10 credit for 24 hours o
by tchaffee 9y ago
My problem with a credit is that it never even comes close to what I'm losing in income. An ISP is an excellent example. I might get a $10 credit for 24 hours of downtime. I'm charging slightly more per hour than that... /s
Maybe switch to bitbucket or other competition for a while?
- eof 9y agoswitched to gitlab a few weeks ago, didn't notice the outage until I saw this thread.
- tekism 9y agoI use VSTS, it's actually improved much over the years!
- justinclift 9y agoGitea's pretty good if you just need a GitHub-like experience (eg good UX) git repo host: https://gitea.io https://gitea.io
- scott_karana 9y agoIf the price of the service working (or not working) is disproportionately large compared to the price of your lost business, that's a problem at your end: you needed to calculate the risk vs return for redundancy. Eg, if your Internet costs $100/mo, but you'd lose $100/hour when it's down during business hours, buy a fallback connection from a competing ISP. ;)
- tchaffee 9y ago> a competing ISP Wow! That actually exists in some places? ;-) Infrastructure so often becomes a monopoly. I can't pay a competing bridge service to drive to work quicker, I can't pay a competing gas company to deliver gas via different pipelines to my house. And I can't pay a competing electric company that uses different wires. I actually am lucky enough to live in a city where there are many competing high speed ISPs. But guess what? I've paid for fallback connections in the past and when one goes down, the other goes down, so I go out to lunch and see the guys working on the wires in the cabinet down the street. The wires that both my ISPs share. I suppose I could get a satellite ISP? That latency. True redundancy for infrastructure is actually very expensive in most cases.