Skip to main content
gcpdown

Is Pub/Sub down?

OperationalLast checked Oct 30, 2026, 5:53 PM UTC

Last 90 days

99.688% uptime · 2 incidents
2026-08-02: operational2026-08-03: operational2026-08-04: operational2026-08-05: operational2026-08-06: operational2026-08-07: operational2026-08-08: operational2026-08-09: operational2026-08-10: operational2026-08-11: operational2026-08-12: operational2026-08-13: operational2026-08-14: operational2026-08-15: operational2026-08-16: operational2026-08-17: operational2026-08-18: operational2026-08-19: operational2026-08-20: outage2026-08-21: operational2026-08-22: operational2026-08-23: operational2026-08-24: operational2026-08-25: operational2026-08-26: operational2026-08-27: operational2026-08-28: operational2026-08-29: operational2026-08-30: operational2026-08-31: operational2026-09-01: operational2026-09-02: operational2026-09-03: operational2026-09-04: operational2026-09-05: operational2026-09-06: operational2026-09-07: operational2026-09-08: operational2026-09-09: operational2026-09-10: operational2026-09-11: operational2026-09-12: operational2026-09-13: operational2026-09-14: operational2026-09-15: operational2026-09-16: operational2026-09-17: operational2026-09-18: operational2026-09-19: operational2026-09-20: operational2026-09-21: operational2026-09-22: operational2026-09-23: operational2026-09-24: operational2026-09-25: operational2026-09-26: operational2026-09-27: operational2026-09-28: operational2026-09-29: operational2026-09-30: operational2026-10-01: operational2026-10-02: operational2026-10-03: operational2026-10-04: operational2026-10-05: operational2026-10-06: operational2026-10-07: operational2026-10-08: operational2026-10-09: operational2026-10-10: operational2026-10-11: operational2026-10-12: operational2026-10-13: operational2026-10-14: operational2026-10-15: operational2026-10-16: operational2026-10-17: operational2026-10-18: operational2026-10-19: operational2026-10-20: degraded2026-10-21: operational2026-10-22: operational2026-10-23: operational2026-10-24: operational2026-10-25: operational2026-10-26: operational2026-10-27: operational2026-10-28: operational2026-10-29: operational2026-10-30: operational
2026-08-022026-10-30

What Pub/Sub does - and how it fails

Pub/Sub is the global messaging fabric between Google Cloud services - the glue in event-driven architectures, streaming pipelines, and microservice fan-out. Pub/Sub incidents rarely lose messages (durability is its core promise); they show up as delivery latency, subscriber backlog growth, or publish errors in one region.

  • Message delivery delays - backlogs grow while publishes still succeed
  • Elevated publish error rates or latency in one region
  • Push subscriptions failing while pull subscribers keep working (or vice versa)
  • Downstream pipeline lag: Dataflow and Cloud Run jobs starving because delivery is delayed

Recent Pub/Sub incidents

  • Multiple services were experiencing issues in the europe-west2 region.

    October 20, 2026 · 6h 8m

    Multiple services were experiencing issues in the europe-west2 region.

  • We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

    August 20, 2026 · 3h 40m

    We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.

Full analyses live in the post-mortem archive.

Pub/Sub questions

Is Pub/Sub down right now?

The live status above reflects our latest check. Pub/Sub degradation usually means late, not lost - watch subscription backlog (oldest unacked message age) rather than publish success to see real impact.

Will I lose messages during a Pub/Sub incident?

Acknowledged publishes are stored durably and replicated; historical incidents have overwhelmingly been delivery delays, not data loss. Design subscribers to be idempotent so the post-incident redelivery burst is safe.

Does Pub/Sub have an SLA?

Yes - 99.95% monthly uptime. Tiered credits apply below target, must be requested within 30 days, and cap at 50% of the month’s Pub/Sub spend.

Get alerted when Pub/Sub breaks

Instant email the moment we detect an incident - affected services and regions included.

Get outage alerts