The availability issues for GitHub, posted earlier today, have now been resolved. In an update post, the GitHub team notes that all GitHub services are back to normal.
Deploys to VIP Go sites are now back to normal as well as well access to repos, issues, pull requests, etc.
If you have any questions or issues, please let us know.
Update Thursday, Oct 11, 2018 20:16 UTC:
From 19:32 UTC to 20:06 UTC, some sites on the VIP Go platform experienced elevated error rates that affected availability. This issue affected a small subset of production sites (less than 5 percent) and was caused by errors in a platform-wide deploy that have since been fixed.
We are currently troubleshooting availability issues for some hosts on the VIP Go platform, and some sites may experience slow load times or errors in the meantime.
Sorry for the trouble! We are working on the issue, and will follow up with another alert once this is resolved.
We will continue to update this post and tweet out status updates from @wpvipstatus until the issue is resolved.
If you have any questions, please email vip-support@wordpress.com.
We’re pleased to announce an automated data sync process which copies data between production and non-production environments.
Having up-to-date production data in test environments simplifies debugging, testing, and QA. Our aim is sync data between production and other environments fast and easily. Today we’re launching new sync functionality that syncs even the largest production databases within minutes. Plus, with our UnionFS integration, media library contents are always available across environments.
To run a data sync, please contact us and we’d be be happy to initiate it for you. Very soon, we’ll be releasing tools that will make data syncing self-service (if you would like to help us test new functionality like this, please let us know).
If you’re interested in learning more, our documentation covers how data sync works and how to customize/extend it.
Jetpack 5.3 is now live across all VIP Go sites.
Jetpack 5.3 includes support for PHP 7.1*, greater control over the placement of your ads, and several enhancements to the experience viewing and managing your Jetpack site with the WordPress.com visual editor.
If you have any questions about this upgrade or anything else Jetpack related, please feel free to reach out to us.
* Note: VIP Go sites are currently running on PHP 7.0.
Jetpack 5.2 (and the 5.2.1 maintenance release) are now live across all VIP Go sites.
Jetpack 5.2 brings you a brand new contact form experience, a better explanation of our recommended features, and several performance improvements.
If you have any questions about this upgrade or anything else Jetpack related, please feel free to reach out to us.
Jetpack 5.1 is now live across all VIP Go sites.
Jetpack 5.1 brings you Comment Likes and a few additional enhancements and bug fixes that further improve compatibility and user experience.
If you have any questions about this upgrade or anything else Jetpack related, please feel free to reach out to us.
On Thursday, July 13, 2017, we will move all VIP Go sites to an improved review workflow utilizing GitHub’s Pull Request (PR) workflow.
In the new workflow, when your team has code ready for review you will open a pull request against the master branch. The VIP team will review the code on GitHub and either provide feedback if any changes are required or approve the PR. Approved PRs can be merged at your convenience, which automatically triggers a deploys to your site(s).
The new review workflow leverages GitHub’s excellent code review tools. Among other things, GitHub provides inline commenting, excellent syntax highlighting and diffing, and allows the VIP team to work with your team in a shared UI. In the future we plan to introduce automated code feedback and opportunities for integrating with Continuous Integration systems like Travis CI, CircleCI, and TeamCity.
Our documentation on the new GitHub PR Review Workflow describes the workflow in detail and answers many common questions. If your workflow involves development in an external repo and you need guidance automating the PR creation process, or if you have any other questions or concerns, please open a ticket and we’ll be happy to help.
In summary, the benefits are:
We will move all VIP Go sites to the new workflow on Thursday, July 13, 2017. If you would like to switch sooner, please open a ticket.
As always, if you have questions or thoughts on how we can make your VIP experience better, please get in touch.
VIP Go sites now have the ability to run custom mu-plugins.
Sometimes referred to as “must-use plugins”, these are plugins that are automatically loaded very early in the WordPress bootup process and do not need to be explicitly enabled or disabled. For multisite installs, the plugins are loaded on all sites on the network.
On VIP Go, these client-mu-plugins are loaded immediately after the platform-level vip-go-mu-plugins and follow similar behaviours:
muplugins_loaded hook.required by top-level files).How to use client-mu-plugins
If your site was set up after June 20, simply add your plugins to the client-mu-plugins folder in your repo and you’re all set.
For older sites, you will need to contact us as we need to ensure that the client-mu-plugins folder is made available on your site:
client-mu-plugins folder to your repo (see vip-go-skeleton for an example).We’ll take it from there, rebuild the web servers (this process does not require any downtime), and follow-up once complete.
For those interested, you can view the code which enables this functionality on Pull Request: Add support for additional mu-plugins.
Thanks to everyone who sent in feedback and requested this functionality. As always, if you have questions, concerns, or thoughts on how we can make your VIP experience better, please feel free to reach out.
Starting Tuesday, June 27, 2017, all insecure (http) traffic to go-vip.co subdomains will be redirected to the secure (https) URL.
$ curl http://example.go-vip.co -s -I | grep Location Location: https://example.go-vip.co
This change will largely affect non-production sites (develop, preprod, etc.) that are using the default *.go-vip.co domain, and we don’t anticipate any issues.
If, for some reason, you still need to access your non-production site over an insecure (http) connection, you can do so with a custom domain. Please open a ticket and we can help set this up.
This change is part of our continued efforts to encourage and spread the use of HTTPS everywhere (a movement being championed by Google as well). If your team needs help getting started with the switch and understanding what’s involved, please reach out and we’d be happy to help.
Starting Monday November 14th, two-step authentication will be required for all admins on VIP Go sites via Jetpack SSO. If you have sites on the WordPress.com VIP platform, you’ll remember that two-step authentication has been a requirement for admin users for some time. For any sites using a conflicting SSO plugin, we’ll work with your developers to ensure admin users have two-step authentication enabled as well.
The new requirement will be enforced for admins by default, but will be possible to expand to all users via a filter. We’ll follow up with details following the November 14th deadline.
In the meantime, we recommend ensuring all admin users on your sites have enabled two-step authentication on their WordPress.com account before November 14th. If you try to log into a VIP Go site as an admin with an account that does not have two-step authentication set up, you’ll be directed to the security settings page on WordPress.com.
WordPress VIP Lobby 
You must be logged in to post a comment.