<!--DEBUG:--><!--DEBUG:dc3-united-states-software-in-english-pdf-2--><!--DEBUG:--><!--DEBUG:dc3-united-states-software-in-english-pdf-2--><!--DEBUG-spv-->{"id":1998252,"date":"2021-09-27T16:14:00","date_gmt":"2021-09-27T14:14:00","guid":{"rendered":"http:\/\/nhub.news\/?p=1998252"},"modified":"2021-09-27T17:04:12","modified_gmt":"2021-09-27T15:04:12","slug":"google-apologizes-to-cloud-customers-over-threatening-emails","status":"publish","type":"post","link":"http:\/\/nhub.news\/fr\/2021\/09\/google-apologizes-to-cloud-customers-over-threatening-emails\/","title":{"rendered":"Google apologizes to cloud customers over threatening emails"},"content":{"rendered":"<p style=\"text-align: justify;\"><b>A broken update triggered emails in which customers were warned about being late with cloud payments<\/b><br \/>\nGoogle has apologized for the emails it recently sent out to Cloud, Firebase and API users in which it asked them to update their payment information or face account suspension. As it turns out, the emails were sent out in error, triggered by a misconfigured update for the Google Cloud Platform. \u00ab\u00a0Google Workspace customers received a warning message on the Admin console user interface and an email regarding an issue with processing their account payment,\u201d the company explained in its incident report. \u201cImpacted customers were redirected to update payment information. Attempts to update the primary payment method caused the admin console to become unresponsive. Initial investigation of this issue revealed the impact was triggered after an update to the payment configuration was released during the impact time frame.\u00a0\u00bb The issue first occurred in the afternoon of September 22, and lasted approximately 12 hours before being fixed. During that time, users of the abovementioned services received the following email: \u201c Action required Dear Google customer, You are receiving this email because you are a Google Cloud Platform, Firebase, or API customer. Our records indicate that your billing account: [account_id] is past due or does not have valid payment information associated with it. This may happen if your credit card has expired or was canceled, and we haven&rsquo;t received valid payment information from you. Please update your billing account with valid payment information by following this link: https:\/\/console.cloud.google.com\/billing\/[account_id]\/settings Failure to make payments may result in suspension and\/or termination of your billing account and the related Project(s) or Service(s). If you have already updated your payment information, please disregard this message. \u201d After resolving the issue, Google sent out another email: \u00a0\u00bb You may have received a notification from us yesterday or earlier today indicating that your billing account is past due or your payment information is invalid and must be updated. That notification was provided in error due to a technical issue,\u00a0\u00bb explained today&rsquo;s email from Google. \u00ab\u00a0The issue has been resolved, and no action is required on your part.\u00a0\u00bb \u00ab\u00a0We apologize for any inconvenience this may have caused. \u00a0\u00bb If you received one of these emails, it would be wise to double-check the payment information provided to Google, and make sure there is no past due balance. Via: BleepingComputer<\/p>\n<script>jQuery(function(){jQuery(\".vc_icon_element-icon\").css(\"top\", \"0px\");});<\/script><script>jQuery(function(){jQuery(\"#td_post_ranks\").css(\"height\", \"10px\");});<\/script><script>jQuery(function(){jQuery(\".td-post-content\").find(\"p\").find(\"img\").hide();});<\/script>","protected":false},"excerpt":{"rendered":"<p>A broken update triggered emails in which customers were warned about being late with cloud payments Google has apologized for the emails it recently sent out to Cloud, Firebase and API users in which it asked them to update their payment information or face account suspension. As it turns out, the emails were sent out [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1998251,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[93],"tags":[],"_links":{"self":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/1998252"}],"collection":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/comments?post=1998252"}],"version-history":[{"count":1,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/1998252\/revisions"}],"predecessor-version":[{"id":1998253,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/posts\/1998252\/revisions\/1998253"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media\/1998251"}],"wp:attachment":[{"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/media?parent=1998252"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/categories?post=1998252"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/nhub.news\/fr\/wp-json\/wp\/v2\/tags?post=1998252"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}