Get started Dashboard
Google Cloud

Expert incident response for Google Cloud

Our founding team picks up your incident, and Polylane's agents dig through your logs, metrics, traces and code with them.

  • Real engineers who've carried the pager The team has been on-call at Cloudflare, Webflow, Groq, Twilio, and Robinhood. They've been where you are right now.
  • Multi-cloud incident response Polylane investigates incidents across AWS, Cloudflare, Vercel, Kubernetes and the rest of your stack, from the edge to the database.
  • Unified context & investigation Logs, metrics, traces, deploys and code in one context graph. Connect in minutes, not weeks.
  • Least-privilege access New cloud accounts connect read-only, with scoped credentials. Nothing in production changes unless you allow it.

By submitting this form, you agree to our Privacy Policy.

My app on Google Cloud is down. What should I do?

Check the Google Cloud status dashboard and Personalized Service Health in your console first. If Google reports nothing, find the failing service: Cloud Run returns 503s when instances crash or never start, and a load balancer 502 usually means unhealthy backends. If the errors started with a deploy, send traffic back to the previous Cloud Run revision with gcloud run services update-traffic, then read the logs in Cloud Logging.

  1. 1 Check Google Cloud's status The status dashboard lists incidents by product and location, and Personalized Service Health in the console shows the ones affecting your projects.
  2. 2 Find the failing service Cloud Run 503s mean instances are crashing or not starting: a container that doesn't listen on $PORT never becomes ready. A load balancer 502 usually means its backends are failing health checks.
  3. 3 Line it up with your last change Compare when the errors started with your latest Cloud Run revision, GKE rollout or Cloud Build deploy. gcloud run revisions list shows recent revisions.
  4. 4 Roll back, then dig in gcloud run services update-traffic SERVICE --to-revisions=REVISION=100 sends all traffic back to a known-good revision. Then filter Cloud Logging by severity and resource to find the first error.

How we resolve active incidents

  1. 1 Rapid onboarding A Polylane engineer reaches out, connects Polylane to your clouds, code and telemetry, and confirms what's affected.
  2. 2 Investigation & mitigation Polylane's agents investigate across logs, metrics, traces and recent changes, and an engineer works with you on the right mitigation.
  3. 3 Remediation, validation & monitoring The fix lands in your repo for your team to review. Polylane checks that things are back to normal and keeps watching every deploy after it.

Why teams choose Polylane

Every cloud in one graph AWS, Cloudflare, Vercel, Kubernetes and more, mapped into one context graph with your code.
Connected in minutes Connect with OAuth or the CLI. No agents to install, no code changes.
Real engineers on the other end Your report goes straight to the people who build Polylane.
Evidence for every claim Every finding links to the log line, metric or deploy behind it.
You stay in control Read-only by default. Nothing writes to production unless you allow it, and you can switch it off at any time.
Works with your coding agents Claude Code, Cursor and other agents reach Polylane over MCP, so they can dig in with you.
“a few days into using @polylane and I have merged like 40 something worthwhile PRs, seems my agents think the PRs are much higher utility than what detail was giving me”
Ben Anthony @benjamin_ACD

Common questions

Is Google Cloud down or is it my app?

Check the status dashboard and Personalized Service Health. If neither shows an incident for your products and region, the errors are coming from your own services.

Why is Cloud Run returning 503 errors?

Usually the container crashes at startup, doesn't listen on the port in $PORT, or runs out of memory. The revision's logs in Cloud Logging show which.

How do I roll back on Cloud Run?

Route traffic back to the previous revision, from the service's Revisions tab or with gcloud run services update-traffic. Old revisions stay deployed, so no rebuild is needed.

Who will help me with a Google Cloud incident?

Our founding team, engineers who have carried the pager for production systems at scale, working with Polylane's agents across your Google Cloud projects, code and telemetry.

Down on a specific platform?

Trusted by teams that ship to production every day