YouTube Embed Issues in London and Atlanta

Right now, we're operating under the assumption that Google is blocking a /64 pool since our affected customers are all falling within that pool.

While we wait for a response from Google, we've come up with a couple of workarounds which should work. The first, and easiest solution, is to add a few lines to the bottom of functions.php which will force cURL requests to go over IPv4:

add_action( 'http_api_curl', function( $curl_handle ) {
   curl_setopt( $curl_handle, CURLOPT_IPRESOLVE, CURL_IPRESOLVE_V4 );
});

Another step that can be taken is for us to assign a /64 pool to the affected Linode. It would need to be configured from the customer end in order to use an IP from the pool, which is why we recommend the simpler first option.

I have the same problem on the Frankfurt, Germany Server. It is a very annoying bug and it would be very nice if you can work this bug out with Google. WordPress is one of the most used website tools, so this will affect thousands of users which will in turn spent countless hours trying to find a solution.

We're experiencing the same issue on Newark servers. Are you still awaiting a response from Google?

We've yet to hear back from Google on this, but we do have a few ways to work around it. If the above suggestion of using IPv4 only won't work in your situation, we'll be happy to provide an IPv6 /64 pool of new addresses to any of your Linodes. Just open a ticket and myself or another member of the Support team will get it squared away.

@mjones I just wanted to check in and see if you had heard back from Google and resolved the issue. We have used the above fix to bypass the issue, but ideally we could remove that at some point, and it would be good to know that other sites we deploy will not encounter the same issue.