Open 8562056816031 opened 4 years ago
issue-label-bot[bot]
commented
4 years ago Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.68. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
8562056816031
commented
4 years ago ອອກຈາກຕົວເລືອກຄຳເຫັນ
@8562056816031
@<?xml version="1.0" encoding="utf-8"?>
8562056816031
commented
4 years ago Certain operation system, system files, basic function software, and applications contained in this device is contributed or developed by Vivo Mobile Communication Co., Ltd.
Copyright © 2011 - 2017 Vivo Mobile Communication Co., Ltd.
All Rights Reserved.
The works ("Works") herein refer to all files, system, software, and program of mobile phones, including without limitation, basic-function software, pre-installed applications, operation system, mobile phone programs, system files, that are developed, owned, or provided by Vivo Mobile Communication Co., Ltd. ("Vivo") and that are not separately released under the terms and conditions of an open source software license. The information contained in the Works is the exclusive property of Vivo worldwide and in perpetuity or as applicable. Prior to delivery of this terminal device to end users, any third party shall not modify, crack, decompile, or delete any file, system, software, or program contained in this terminal device, or pre-install any applications on this terminal device. The end user of this terminal device is merely granted to rightfully use the Works and shall not, by himself or through a third party, modify, crack, decompile, or delete any basic-function software, system files, operation system, system programs, or hosts contained in this terminal device which may cause harm to this terminal device, including without limitation, system files damage, malfunction, and instability of terminal device, disclosure of personal information, loss of property. The end user shall be liable for all such consequences resulting from the abovementioned conduct. Vivo reserves the right to claim compensations if such conduct causes damage to Vivo. No further right is granted hereunder, including but not limited to, distribution, reproduction, modification, and/or transmission. Any other usage of the Works shall be subject to the written consent of Vivo.
For all the relevant software (which includes components provided by suppliers and licensors of Vivo) bundled with or pre-installed on this terminal device purchased by you, the usage of such relevant software by you shall be subject to such suppliers/licensors’ copyright terms and conditions.
[]()vivo
vivo Privacy Policy
Last updated: April 9, 2020
vivo Mobile Communications Co., Ltd. (hereafter referred as "vivo" or "We") and its affiliates understand that information and privacy are important for you. If you would like to share your information with us, we can provide you with better products and services, and help you to solve the issues you might be facing while using our products.
We developed this vivo Privacy Policy (hereafter referred as "Privacy Policy") for your reference so that you will be able to understand how we collect, use, store, transfer and disclose your information. The Privacy Policy covers how we handle your information.
You can choose whether or not to share your information. However, if you decide not to share your information, we may not be able to provide you with related services and solve the issues you might be facing while using our products.
Main Content of the Privacy Policy
Personal information refers to the information that can be, either directly or indirectly, in combination with other information, used for individual identification.
1.1 Account creation, registration and purchase information – when you create an account, in order to register and create an account, complete the purchase of products and services and register or purchase our products or services, etc. you may be required to provide your name, phone number, email and mailing address, and payment method.
The foregoing information will be used for providing services to you or in some cases providing information on additional services offered by us.
1.2 Contact information When requesting to be contacted by vivo relevant personnel, you may be asked to provide information about yourselves. This information enables vivo relevant personnel to respond promptly and effectively to customer questions and requests. This information will be only used for address your questions.
1.3 Product activation information – When you use and activate the device for the first time, we may collect information such as IMEI code, location and activation time, in order to enable related products and services (such as warranty service). This type of information will be collected anonymously, and any information collected will not be used to determine your identity.
1.4 Abnormal or crash information – If you experience abnormal behavior or system crash after you have agreed to join vivo's User Experience Improvement Plan, we may collect your device model, the application name and version, the IMEI code, error log, and other related information in order to solve the issues you are facing while using the product. This type of information will be collected anonymously, and any information collected will not be used to determine your identity.
1.5 Function usage information – If you agree to join vivo's User Experience Improvement Plan, we will need to understand how you use the different functions of your device, so that we can provide you with better service and user experience. Information we collect may include your usage information of the different functions of the device and applications as well as the usage habits. This type of information will be collected anonymously, and any information collected will not be used to determine your identity.
1.6 Update and upgrade information – In order to promptly notify you about any update or upgrade for your system and application, we might need to collect information such as device name, system and application version, operating system and browser version, region and language settings, device identification information and service provider’s network code. The above information will only be collected for application update notification purposes. This type of information will be collected anonymously, and any information collected will not be used to determine your identity.
1.7 Location information – When you use certain feature or application from vivo, we will need to collect information about your location. For example, when you use applications and features such as search, navigation and weather enquiries, we may obtain your physical location in order to provide you with accurate information and services. This type of information will be collected anonymously, and any information collected will not be used to determine your identity.
1.8 Cookies – Our websites, online services, Internet applications, email and advertisement may use Cookies and other similar technologies (such as pixel tags and web beacons). Our cookies will not be used to determine your identity, save as expressly stated otherwise herein. They are only used to provide you with better user experience and improve our services.
We may disclose your personal information under the following circumstances, pursuant to the consent provided by you herein:
a. Your personal information will be disclosed to an affiliated company of vivo;
b. Your personal information will be disclosed to an authorized partner of vivo. We require authorized partners of vivo to comply with this Privacy Policy and to take necessary and reasonable measures to protect your information. vivo will never allow any authorized third party to use your personal information for any other purpose other than this Privacy Policy;
c. We are required to disclose your personal information by local judicial or government authorities, agencies or as mandated under applicable laws vivo may, without obtaining prior consent from you, share information with governmental agencies mandated under law to obtain information including sensitive personal data or information for the purpose of verification of identity, or for prevention, detection, investigation including cyber incidents, prosecution, and punishment of offences.
d. In the event of any merger, restructuring or bankruptcy, vivo may also provide your personal information to related third parties.
vivo will take necessary and reasonable steps to protect your information, including but not limited to technical and physical measures. However, please note that although we have implemented reasonable measures to protect your personal information, there is no security measure that can guarantee absolute safety.
We will only use or disclose information of minors under the following circumstances:
a. The disclosure of information is allowed by law;
b. Consent through this Privacy Policy from the legal representatives or guardians of the minors for and on behalf of the minors has been obtained;
c. Use or disclose information of minors in order to protect the minors.
vivo will not knowingly collect personal information from minors, except as set out above. We will immediately take steps to delete such information if we discover it is from minors and the parents or legal representatives had not consented for and on behalf of the minors.
The definition of "minors" shall be in accordance with the relevant local regulations and laws.
This Privacy Policy only applies to products and services from vivo, and does not apply to products and services from any third party. Our website, products, applications and services may contain links to third party websites, products and services. In addition, our products and services may use or provide the product or service from a third party. Your use of the products or services from a third party shall be subject to the provisions of privacy policy/terms of use of the third party, please pay attention to the privacy policy/terms of use of the third party.
vivo products and services can be provided from resources or servers of different countries or regions around the world. Therefore, your information may be stored or transmitted to servers outside of the country in which you are living, in accordance with applicable laws. If you agree to accept our services and allow us to collect, handle, disclose, transfer and use your information, you are also giving us permission to collect, transfer, store, use and process your information outside your country or region according to this Privacy Policy.
Cookie is a type of specific identifier to enable your device to be identified by our system.
Sometimes we will store cookies on your device to record your preferences and provide personalized services. It will also record your login credentials, so you don't have to enter this information each time you sign in.
Current browser configuration has settings to accept and limit the level of cookies. You may configure at your own preference when you use web browser to access the services.
You may learn more details about cookies from your browser's "Help" menu.
You may at any time disable cookies. By modifying your browser preferences, you can choose to accept all cookies, or to reject all cookies. You can still use vivo IT data network even if you do not accept cookies, but please note that certain services may be designed to work with cookies, and disabling cookies may affect your use of the services or part of the service.
We may use cookie-like technology, such as web beacons (or "pixel tags"), to send information from your device to server.
Web beacons are generally embedded in e-mail and online video. With beacon, we can read some specific information from your device, such as whether the e-mail was opened, device IP and so on.
We will analyze the data collected through web beacons, in order to optimize the products and provide services that suit you better.
By accessing and using our services, you are deemed to agree that cookies and web beacons will be stored on your device.
We will not use cookies or collect any personal information for any purpose other than those stated in this policy.
vivo may amend or update this Privacy Policy from time to time, and we will notify you of any major changes by publishing notice of change. For the most updated version of this policy, please refer to our website.
You hereby consent to the collection, storage, use, disclosure, transfer, of the personal information and information by vivo for the purposes of and in accordance with this Privacy Policy.
You may at any time withdraw your consent to the collection, storage, use, disclosure, and transfer, of the information by us. When you withdraw your consent, you can go settings and disable the functions by turning off the relative button or you can notify your intention in writing to us by sending an e-mail to the contact address notified under paragraph 10. Your act of withdrawing shall be deemed a notification to us that you are withdrawing your consent to the collection, storage, use, disclosure, and transfer, of the information. However, in the event that you so choose to withdraw your consent to the aforesaid, we shall be entitled to discontinue providing any or all of the products/services to you.
You may at any time review/ correct/ supplement/ add to, the personal information or information provided by you, by sending an e-mail to this effect to the contact address notified under paragraph 10. We shall at no time be responsible/liable for the authenticity/ veracity of the personal information or information provided by you.
If you have any question, comment or suggestion regarding this Privacy Policy, contact us via the “Feedback” app on your mobile phone, vivo official forum or our after-sales services. You can also reach us via e-mail at privacy@vivo.com.
Please be noted that the local version of the Privacy Policy may be different from the general version of the Privacy Policy due to the local laws and regulations and some features may not be available in all regions or all languages.
vivo
Home
Privacy Policy
Popular LinksV17S1 ProY19Y11All ModelsRetail Stores
SupportFAQsService CenterFuntouch OSSystem UpdateQuery of Spare Parts PriceIMEI AuthenticationSecurity Advisory
About vivoInfoPressCareers at vivo
Email Us
Privacy PolicyTerms of UseWarranty TermsGlobal-English
Copyright © 2020 vivo Mobile Communication Co., Ltd. All rights reserved.
8562056816031
commented
4 years ago Specially Designated Nationals and Blocked Persons list ("SDN List") and all other sanctions lists administered by OFAC, including the Foreign Sanctions Evaders List, the Non-SDN Iran Sanctions Act List, the Sectoral Sanctions Identifications List, the List of Foreign Financial Institutions Subject to Correspondent Account or Payable-Through Account Sanctions and the Non-SDN Palestinian Legislative Council List. Given the number of lists that now reside in the Sanctions List Search tool, it is strongly recommended that users pay close attention to the program codes associated with each returned record. These program codes indicate how a true hit on a returned value should be treated. The Sanctions List Search tool uses approximate string matching to identify possible matches between word or character strings as entered into Sanctions List Search, and any name or name component as it appears on the SDN List and/or the various other sanctions lists. Sanctions List Search has a slider-bar that may be used to set a threshold (i.e., a confidence rating) for the closeness of any potential match returned as a result of a user's search. Sanctions List Search will detect certain misspellings or other incorrectly entered text, and will return near, or proximate, matches, based on the confidence rating set by the user via the slider-bar. OFAC does not provide recommendations with regard to the appropriateness of any specific confidence rating. Sanctions List Search is one tool offered to assist users in utilizing the SDN List and/or the various other sanctions lists; use of Sanctions List Search is not a substitute for undertaking appropriate due diligence. The use of Sanctions List Search does not limit any criminal or civil liability for any act undertaken as a result of, or in reliance on, such use. Download the SDN ListSanctions List Search: Rules for useVisit The OFAC Website Download the Consolidated Non-SDN ListProgram Code Key
Lookup
Type: All Aircraft Entity Individual Vessel Address: Name:City: ID #:State/Province:* Program: All 561-Related BALKANS BELARUS BURUNDI CAATSA - IRAN CAATSA - RUSSIA CAR CUBA CYBER2 DARFUR DPRK DPRK2 DPRK3 DPRK4 DPRK-NKSPEA DRCONGO ELECTION-EO13848 FSE-IR FSE-SY FTO GLOMAG HIFPAA HK-EO13936 HRIT-IR HRIT-SY ICCP-EO13928 IFCA IFSR IRAN IRAN-CON-ARMS-EO IRAN-EO13846 IRAN-EO13871 IRAN-EO13876 IRAN-EO13902 IRAN-HR IRAN-TRA IRAQ2 IRAQ3 IRGC ISA LEBANON LIBYA2 LIBYA3 MAGNIT MALI-EO13882 NICARAGUA NICARAGUA-NHRAA NPWMD NS-PLC SDGT SDNT SDNTK SOMALIA SOUTH SUDAN SYRIA SYRIA-CAESAR SYRIA-EO13894 TCO UKRAINE-EO13660 UKRAINE-EO13661 UKRAINE-EO13662 UKRAINE-EO13685 VENEZUELA VENEZUELA-EO13850 VENEZUELA-EO13884 YEMEN ZIMBABWE
Country:
List:
All Afghanistan Albania Algeria Angola Argentina Armenia Aruba Australia Austria Azerbaijan Bahamas, The Bahrain Bangladesh Barbados Belarus Belgium Belize Benin Bolivia Bosnia and Herzegovina Brazil Brunei Bulgaria Burkina Faso Burma Burundi Cambodia Canada Cayman Islands Central African Republic Chile China Colombia Comoros Congo, Democratic Republic of the Congo, Republic of the Costa Rica Cote d Ivoire Croatia Cuba Cyprus Czech Republic Denmark Dominica Dominican Republic Ecuador Egypt El Salvador Equatorial Guinea Eritrea Ethiopia Finland France Georgia Germany Ghana Gibraltar Greece Guatemala Guernsey Guyana Haiti Honduras Hong Kong India Indonesia Iran Iraq Ireland Israel Italy Jamaica Japan Jersey Jordan Kazakhstan Kenya Korea, North Korea, South Kosovo Kuwait Kyrgyzstan Laos Latvia Lebanon Liberia Libya Liechtenstein Luxembourg Malaysia Maldives Mali Malta Marshall Islands Mauritania Mexico Moldova Mongolia Montenegro Morocco Mozambique Namibia Netherlands Netherlands Antilles New Zealand Nicaragua Niger Nigeria Norway Oman Pakistan Palestinian Panama Paraguay Peru Philippines Poland Qatar Region: Crimea Region: Gaza Region: Kafia Kingi Region: Northern Mali Romania Russia Rwanda Saint Kitts and Nevis Saint Vincent and the Grenadines Samoa Saudi Arabia Senegal Serbia Seychelles Sierra Leone Singapore Slovakia Slovenia Somalia South Africa South Sudan Spain Sri Lanka Sudan Sweden Switzerland Syria Taiwan Tajikistan Tanzania Thailand The Gambia Trinidad and Tobago Tunisia Turkey Turkmenistan Uganda Ukraine undetermined United Arab Emirates United Kingdom United States Uruguay Uzbekistan Vanuatu Venezuela Vietnam Virgin Islands, British West Bank Yemen Zimbabwe
All Non-SDN SDN
Minimum Name Score:

Lookup Results: 0 Found
NameAddressTypeProgram(s)ListScore 
Your search has not returned any results.
SDN List last updated on: 11/10/2020 10:04:04 AMNon-SDN List last updated on: 3/17/2020 10:53:27 AM
dennismuchene
commented
8 months ago www.google.com
www.bing.com
<?xml version="1.0" encoding="utf-8"?> urn:google-cloud-status:feed 2020-11-12T16:51:36Z Google Cloud Platform Google Cloud Status Dashboard Updates RESOLVED: Incident 20012 - Elevated frequency of Host Maintenance events on GCE instances with an attached GPU(s) and SSD(s) The issue with Google Compute Engine instances with an attached GPU(s) and SSD(s) is believed to be affecting a very small number of projects and our Engineering Team continues to work on it. If you have questions or are impacted, please open a case with the Support Team and we will work with you until this issue is resolved. No further updates will be provided here. We thank you for your patience while we're working on resolving the issue. 2020-11-11T19:01:10Z urn:google-cloud-status:20012.20012003 UPDATE: Incident 20012 - Elevated frequency of Host Maintenance events on GCE instances with an attached GPU(s) and SSD(s) Description: Mitigation work is still underway by our engineering team. Further investigation of current impact and mitigation timeline is ongoing. We will provide more information by Wednesday, 2020-11-11 13:00 US/Pacific. Diagnosis: Affected customers will experience elevated frequency of Host Maintenance events on GCE instances with an attached GPU(s) and SSD(s). Workaround: Temporarily switch to use V100 GPU's which are unaffected by this issue. https://cloud.google.com/compute/docs/gpus 2020-11-11T00:04:29Z urn:google-cloud-status:20012.20012002 UPDATE: Incident 20012 - Elevated frequency of Host Maintenance events on GCE instances with an attached GPU(s) and SSD(s) Description: We are experiencing an issue with Google Compute Engine beginning in 2020-08. A firmware rollout is being created that should address the issue. The rollout is currently expected to complete next week, but mitigation efforts are still ongoing. We will provide more information by Tuesday, 2020-11-10 16:30 US/Pacific. Diagnosis: Affected customers will experience elevated frequency of Host Maintenance events on GCE instances with an attached GPU(s) and SSD(s). Workaround: Temporarily switch to use V100 GPU's which are unaffected by this issue. https://cloud.google.com/compute/docs/gpus 2020-11-10T22:33:27Z urn:google-cloud-status:20012.20012001 RESOLVED: Incident 20008 - GAE Cloud Monitoring Metrics are not being ingested. The issue with Google App Engine has been resolved for all affected projects as of Thursday, 2020-11-05 13:11 US/Pacific. We thank you for your patience while we worked on resolving the issue. 2020-11-05T21:43:49Z urn:google-cloud-status:20008.20008003 UPDATE: Incident 20008 - GAE Cloud Monitoring Metrics are not being ingested. Description: We have rolled back an update and believe the issue with Google App Engine is partially resolved. Our engineering teams are working to confirm full resolution. We do not have an ETA for full resolution at this point. We will provide an update by Thursday, 2020-11-05 13:45 US/Pacific with current details. Diagnosis: Metric dashboards for GAE services no longer update. Workaround: None at this time. 2020-11-05T20:57:17Z urn:google-cloud-status:20008.20008002 UPDATE: Incident 20008 - GAE Cloud Monitoring Metrics are not being ingested. Description: We are experiencing an issue with Google App Engine beginning at Thursday, 2020-11-05 09:55 US/Pacific. Cloud Monitoring Metrics are no longer being ingested causing telemetry data to be unavailable. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2020-11-05 13:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Diagnosis: Metric dashboards for GAE services no longer update. Workaround: None at this time. 2020-11-05T20:41:55Z urn:google-cloud-status:20008.20008001 RESOLVED: Incident 20011 - GCE instance creation/start/stop operations failing in us-central1-f The issue with Google Compute Engine has been resolved for all affected users as of Friday, 2020-10-30 16:35 US/Pacific. We thank you for your patience while we worked on resolving the issue. 2020-10-31T00:02:25Z urn:google-cloud-status:20011.20011004 UPDATE: Incident 20011 - GCE instance creation/start/stop operations failing in us-central1-f Description: We believe the issue with Google Compute Engine operations is partially resolved. All previous operations should have completed, and customers should experience normal latency on new operations. We will provide an update by Friday, 2020-10-30 17:45 US/Pacific with current details. Diagnosis: Affected customers may see delays performing instance operations, but they should eventually complete. Other Cloud Services that create instances on demand may also experience impact such as: Google Kubernetes Engine, Composer, Dataproc, and Dataflow. Workaround: When possible try instance operations in other zones. 2020-10-30T23:56:13Z urn:google-cloud-status:20011.20011003 UPDATE: Incident 20011 - GCE instance creation/start/stop operations failing in us-central1-f Description: Other Cloud Services that create instances on demand may be impacted such as: Google Kubernetes Engine, Composer, Dataproc, and Dataflow We will provide an update by Friday, 2020-10-30 17:00 US/Pacific with current details. Diagnosis: Affected customers may see delays performing instance operations, but they should eventually complete. Other Cloud Services that create instances on demand may also experience impact such as: Google Kubernetes Engine, Composer, Dataproc, and Dataflow. Workaround: When possible try instance operations in other zones. 2020-10-30T23:37:45Z urn:google-cloud-status:20011.20011002 UPDATE: Incident 20011 - GCE instance creation/start/stop operations failing in us-central1-f Description: We are experiencing an issue with Google Compute Engine starting on Friday, 2020-10-30 07:30 US/Pacific. The backlog is continuing to decrease, and delays on new instance creation have significantly decreased from the peak with an average of 1 minute. We are anticipating the backlog to clear in approximately 40 minutes. We will provide an update by Friday, 2020-10-30 17:00 US/Pacific with current details. Diagnosis: Affected customers may see delays performing instance operations, but they should eventually complete. Workaround: When possible try instance operations in other zones. 2020-10-30T23:30:55Z urn:google-cloud-status:20011.20011001 RESOLVED: Incident 20004 - We believe the issue with Cloud Run deployments failing is fully resolved as of Thursday, 2020-10-29 14:07. The issue with Cloud Run deployments failing globally has been resolved for all affected projects as of Thursday, 2020-10-29 14:07 US/Pacific. We thank you for your patience while we worked on resolving the issue. 2020-10-29T21:16:52Z urn:google-cloud-status:20004.20004004 UPDATE: Incident 20004 - We believe the issue with Cloud Run deployments failing is fully resolved as of Thursday, 2020-10-29 14:07. Description: We believe the issue with Cloud Run deployments failing is fully resolved as of Thursday, 2020-10-29 14:07. We are currently monitoring the situation to ensure there is no recurrence. We will provide an update by Thursday, 2020-10-29 14:45 US/Pacific with current details. Diagnosis: New deployments to Cloud Run will fail globally. Workaround: None at this time. 2020-10-29T21:11:24Z urn:google-cloud-status:20004.20004003 UPDATE: Incident 20004 - We believe the issue with Cloud Run deployments failing is fully resolved as of Thursday, 2020-10-29 14:07. Description: Our engineering team is currently rolling back a configuration change to mitigate the issue. We do not yet have an ETA for full resolution. Existing Cloud Run deployments are unaffected. We will provide more information by Thursday, 2020-10-29 14:30 US/Pacific. Diagnosis: New deployments to Cloud Run will fail globally. Workaround: None at this time. 2020-10-29T20:40:23Z urn:google-cloud-status:20004.20004002 UPDATE: Incident 20004 - We believe the issue with Cloud Run deployments failing is fully resolved as of Thursday, 2020-10-29 14:07. Description: We are investigating an issue with Cloud Run deployments failing globally starting at Thursday, 2020-10-29 12:45 US/Pacific. We will provide more information by Thursday, 2020-10-29 14:00 US/Pacific. Diagnosis: New deployments to Cloud Run may fail. Workaround: None at this time. 2020-10-29T20:12:17Z urn:google-cloud-status:20004.20004001 RESOLVED: Incident 20007 - We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. The issue with Google Cloud Storage buckets in us-central1 seeing higher latency and timeout errors has been resolved for all affected projects as of Tuesday, 2020-10-27 13:30 US/Pacific. 2020-10-27T21:09:41Z urn:google-cloud-status:20007.20007004 UPDATE: Incident 20007 - We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Mitigation has been effective and we believe the issue should be resolved as of Tuesday, 2020-10-27 13:30 US/Pacific. We are continuing to monitor the situation for any changes. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Diagnosis: Affected customers may experience request timeout errors. Downstream services may include Google Container Registry with images being stored in us-central1. This may cause GKE workloads to have trouble pulling new images in us-central1. Workaround: None at this time. 2020-10-27T20:53:23Z urn:google-cloud-status:20007.20007003 UPDATE: Incident 20007 - We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Description: We are experiencing an issue with Google Cloud Storage requests timing out as of Tuesday, 2020-10-27 11:00 US/Pacific. Google Container Registry is also experiencing timeout errors as a result of the Google Cloud Storage issues. Our engineers are currently investigating the root cause and working to mitigate the issue. We will provide more information by Tuesday, 2020-10-27 14:15 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. 2020-10-27T20:38:23Z urn:google-cloud-status:20007.20007002 UPDATE: Incident 20007 - We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Description: We've received a report of an issue with Google Cloud Storage as of Tuesday, 2020-10-27 11:00 US/Pacific. Our engineers are currently investigating the root cause. We will provide more information by Tuesday, 2020-10-27 14:00 US/Pacific. Location: us-central1 Diagnosis: Affected customers may experience request timeout errors. Workaround: None at this time. 2020-10-27T20:24:40Z urn:google-cloud-status:20007.20007001 RESOLVED: Incident 20005 - We are investigating an elevated error rate in us-east1 for Cloud Storage Customers. Mitigations are complete, and we are seeing service restored for all customers. We thank you for your patience while we worked on resolving the issue. 2020-10-24T19:02:57Z urn:google-cloud-status:20005.20005003