This page lists known issues for Cloud Run (fully managed).
You can also check for existing issues or open new issues in the public issue trackers.
Google Cloud services not yet supported
The following table lists services that are not yet supported by Cloud Run (fully managed). Note that Cloud Run for Anthos on Google Cloud can use any service that Google Kubernetes Engine can use.
|Filestore (NAS)||Filestore is not Firestore, which is supported.|
|VPC Service Controls|
|Web Security Scanner|
High request latency with custom domains when invoking from some regions
Requests to Cloud Run (fully managed) services using custom domains can have a very high latency from some locations. This issue is more pronounced for Cloud Run (fully managed) services in `asia-northeast1` and `us-east4`. If you observe this issue, you can achieve greater performance with Cloud Load Balancing using a serverless NEG.
WebSockets and gRPC bi-directional streaming support
inbound requests to Cloud Run (fully managed) services using WebSockets and gRPC bi-directional streaming are not supported. Server-side HTTP and gRPC streaming are supported.
outbound requests from Cloud Run (fully managed) services can use WebSockets and bi-directional gRPC streaming.
Delay with labels on Networking SKUs for new revisions
After deploying a new revision, labels can take up to a few hours to be associated with networking billing SKUs.
Cloud Run-specific networking SKU IDs are not final.
After general availability, Cloud Run-specific networking SKUs may be replaced by a common GCP neworking SKU. Pricing will remain the same.
Unsupported HTTP request methods
Requests with HTTP methods
CONNECT are not supported and therefore
will not be received by services running on Cloud Run (fully managed).
Reserved URL paths
It is not possible to use the following URL paths:
- Paths starting with
- Some paths ending with
CPU utilization metric is incorrect
(Alpha) is reporting incorrect data.
The reported CPU utilization is lower than the actual CPU utilization.
Reduced availability for requests longer than 15 minutes
Requests longer than 15 minutes may be subject to higher failure rates while timeouts above 15 minutes are in Beta.
Rapid service creation in new project might fail
Creating a Cloud Run service that fetches a token from the container instance metadata server in a newly created project might fail. You should try again a few minutes later.