GitHost

Painless GitLab and GitLab CI Hosting

[GitHost @GitHostIO]

Attention https://t.co/RBtVaowgTB users - We’re sad to say that GitHost will stop operating on June 1st, 2019.

Check out FAQ pages (https://t.co/npEdN9U3cL) for details & available migration options.

[GitHost @GitHostIO]

@CristhianSalta Everything is running nominal now. Sorry for the inconvenience.

[GitHost @GitHostIO]

@edisonalday it should be fixed now, really sorry about that. Tell us if you're still seeing an issue.

[GitHost @GitHostIO]

@wernminlim See @gitlabstatus for the latest status updates. Everything should be okay now.

[GitHost @GitHostIO]

@thenanobel Yup. You can always check which version is https://t.co/DP9HhnKYfO running by going to https://t.co/NMnzn4FBKH

[GitHost @GitHostIO]

@magic_cacti You can list all visible projects when sort them by your "trending logic" via https://t.co/pGGQfcoR7B

[GitHost @GitHostIO]

@shinusuresh See the latest updates on @gitlabstatus. Also https://t.co/1hABgodSx5. We're back up now.

[GitLab.com Status @gitlabstatus]

Issue for the problems with our NFS server earlier today: https://t.co/EHfHzaAQAt

[GitHost @GitHostIO]

@dirtylowprofile Sorry for the inconvenience. We're back up now.

[GitHost @GitHostIO]

@stevefolly Sorry for the inconvenience. Are you still affected? Could've been a load spike with our runners.

[GitHost @GitHostIO]

@ihostage Sorry about that. We had a tiny problem with background processing (https://t.co/tMIZroh07I). Are you still affected?

[GitLab.com Status @gitlabstatus]

We are currently experiencing a delay in background job processing and are adding additional capacity to clear the queue.

[GitHost @GitHostIO]

@PatrikS can you email support at https://t.co/MMcsyEG3Lx with more info to get this resolved? Sorry for the trouble :(

[GitHost @GitHostIO]

@avinapster See https://t.co/loK9tT767h Sorry for the inconvenience. Everything should be working now.

[GitLab.com Status @gitlabstatus]

We are seeing a high increase of git operations through HTTPS, this is impacting the service, we are investigating

[GitHost @GitHostIO]

@cmsimike We identified an issue with our Markdown parser, and this will be fixed in 9.1 via https://t.co/bgFle8arDB.

[GitHost @GitHostIO]

@Routhinator Sorry for the inconvenience. Could be a minor glitch. Glad that it worked out for you in the end.

[GitHost @GitHostIO]

@edisonalday Could you open a support ticket about this, so we can resolve this for you ASAP?

[GitHost @GitHostIO]

@akashkaveti They're stored on S3. No encryption.

[GitHost @GitHostIO]

@Soshaw96 You don't need (and can't) sign in. It's publicly available.

[GitHost @GitHostIO]

@laurence_man We had an issue with our auth mechanism. Should be fixed now. Sorry for the inconvenience.

[GitHost @GitHostIO]

@yeehaa We had an issue with our auth mechanism. Should be fixed now. Sorry for the inconvenience.

[GitHost @GitHostIO]

@domparry We had an issue with our auth mechanism. Should be fixed now.