Sorry to hear about your issues with GitHost - feel free to share any ticket IDs and we can look into it further on our side.
#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)
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?
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).