zlacker

> If you missed the initial news of the impending showdown, Platformer reported on June 10th that Twitter had been refusing to pay Google for its cloud services ahead of their contract’s June 30th renewal date.

> Twitter’s Google Cloud contract dates back to 2018.

https://www.engadget.com/twitter-has-supposedly-started-payi...

Oh... this explains all this fiasco :facepalm:

>>summer+(OP)
As the article says, and as Bloomberg, etc have also reported. Twitter finally agreed to play nice with Google and the issue was resolved. They are probably trying to get off of GCP, but this isn't because they suddenly lost access to GCP from payment refusal.

>>summer+(OP)
https://www.reuters.com/technology/twitter-resumes-paying-go...

That's from a week ago.

>>partia+u1
Well, I'm sure that migration off of GCP will go smoothly with no problems. Won't cause any more stability issues with Twitter. /s

>>summer+(OP)
Twitter does not use google cloud as the main backend service. All of its self hosted.

Gcloud only supports batch jobs and data analysis.

>>18pfsm+07
The sourcing on that story is a single unnamed person whereas both companies refused to comment. Seems like there could be more to the story than "Twitter started paying again and everything's fine."

>>summer+(OP)
Twitters core services are on prem dcs