In the past week I have had no less than ten different clients experience failures of their backups to Google nearline. There are three different errors that have been occurring:

• "Gone" - that is all it says - it is a Google 410 error
• Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
• The device is not ready. Position xxxxxxxxxxxx count : 512 . ErrorCode:21 HR:80070015

I asked support if i am the only one experiencing these errors and I do not get a response - Am just told to contact Google directly which of course I cannot do as I do not maintain a support contract (at $100 per month per user). Over the past 6 years it has been rare to have two errors like these in one month, an now I have had ten+ failures in a little over a week?
I was told to run the repo sync - which I did, but sometimes just rerunning the plan works fine.
So I am asking this forum if anyone else has experienced these or similar issues using Google as a backend.
I am currently in the process of doing some testing with the failed plans going to Azure in an attempt to prove that it is a Google specific issue.