As of today, 04/30/2025 at 7:17pm, I am unable to load any logs for my Cloud Run project. Now, at 11:50pm, the problem remains, and no outages are reported for region us-east1.
When trying to access logs for a Cloud Run Function from the Cloud Console, I first get a long attempt to load the logs with a message like: "Loading... Scanned up to 5/1/2025,3:59PM", followed by, "Error: Internal error encountered".
Logs Explorer is perpetually stuck loading the logs with this message displayed, "Loading... Scanned up to 4/30/25, 10:26 PM."
Running, 'gcloud logging read' from my local device returns:
ERROR: (gcloud.logging.read) HttpError accessing <https://logging.googleapis.com/v2/entries:list?alt=json>: response: <{'vary': 'Origin, X-Origin, Referer', 'content-type': 'application/json; charset=UTF-8', 'content-encoding': 'gzip', 'date': 'Thu, 01 May 2025 02:13:40 GMT', 'server': 'ESF', 'x-xss-protection': '0', 'x-frame-options': 'SAMEORIGIN', 'x-content-type-options': 'nosniff', 'server-timing': 'gfet4t7; dur=9023', 'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000', 'transfer-encoding': 'chunked', 'status': 500}>, content <{
"error": {
"code": 500,
"message": "Internal error encountered.",
"status": "INTERNAL"
}
}
>
This may be due to network connectivity issues. Please check your network settings, and the status of the service you are trying to reach.
Finally, the mobile app says "Something went wrong".
This is NOT a network connectivity issue. The last thing I did before noticing this issue was update and run the source code of an existing Cloud Run Function. Could I have creating a devastating bug?? Is anyone else experiencing issues with Cloud Logging?
Update: Logs Explorer is now a completely blank page.
LinkedIn
Twitter
