Tickets from the last year excluding application bugs, that resulted in downtime. I did not get any notification of outages on these. Everything has been resolved and I am very happy with the product when it is working. I get that some of these are due to companies you rely on for your infrastructure.
#26561 Server Not Responding (No reponse for over a day)
#24895 500 on Application Settings (17 hour for response 24 for fix)
#29731 Sever Not Responding (disk full with no warning [actually at 67% but that hangs backups]) Solution expand block storage which failed several times.
That are a lot of issues, I sorry that you've had all those problems with GitHost.io.
GitHost.io is a service we've offered because GitLab.com was not usable for everyone. One of the problems was the latency of GitLab.com. We're making good progress in fixing that.
Are there other things that keep you on GitHost.io? We've heard that people want LDAP sync and we're planning to bring this to GitLab.com. Is there anything else we should focus on?
Personally, I think there's a lot of Wizard of Oz going on with gitlab. Put up a decent front so far but utterly incoherent/incompetent behind the scenes.
In page https://about.gitlab.com/products/#comparison it says "Community and support forums only" which is applicable only to "Community Edition". It may better be titled as "Community and support forums" and show the tick mark below every Edition. This could of course save you some time (and money).
#26561 Server Not Responding (No reponse for over a day)
#24895 500 on Application Settings (17 hour for response 24 for fix)
#29731 Sever Not Responding (disk full with no warning [actually at 67% but that hangs backups]) Solution expand block storage which failed several times.
#41739 Repositories Unavailable (Githost infrastructure failure moving storage to block storage)
#45163 DNS failure (DYN Attack)
#22524 Expired SSL Certificate
#72593 Server Not Responding (Data Center Outage)