G2

Greg G.

Principal Software Engineer

Enterprise (> 1000 emp.)

6/29/2026

"Saved Us Countless Dev Weeks on Server-Push Solutions"

4/5

What do you like best about PubNub?

Saved our teams countless dev weeks in building custom server-push solutions across the enterprise Review collected by and hosted on G2.com.

What do you dislike about PubNub?

Our main frustrations have been recurring, unexplained reliability issues — presence-related timeouts and 500 errors that have repeatedly hit our production services with no change on our end, usually requiring us to reach out and confirm the problem was on PubNub's side rather than being proactively notified. This is made worse by limited observability: the status page reports latency but not availability, and we lack self-service access to API and presence logs, so investigating an incident means manually requesting log exports and waiting. Usage and billing visibility is also weaker than we'd like — it's been consistently hard to understand what drives our transaction volume, including how transactions are counted and why a meaningful share of our billed publish volume comes from presence events we don't even consume. Review collected by and hosted on G2.com.

What problems is PubNub solving and how is that benefiting you?

PubNub powers the real-time messaging infrastructure behind our consumer-to-agent and consumer-to-consumer communication across several Zillow products. Rather than building and operating our own WebSocket and pub/sub infrastructure at scale, we rely on PubNub to deliver messages reliably and with low latency, manage channel subscriptions, and handle presence detection so we can show who's online and surface unread message counts. This lets our engineering teams focus on product features — chat experiences, co-shopper notifications, agent messaging — instead of the underlying real-time delivery layer, and it scales with our traffic without us having to manage that capacity ourselves. Review collected by and hosted on G2.com.