Incident Library
Applied filters SymptomMisrouted requestsOrganisationPubNubClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. IL-0560 Some PubNub messages in the US East point of presence were misrouted with no error and not delivered right away
    PubNub2026
    Symptoms

    At 12:10 UTC on 25 August 2026, PubNub's internal monitoring alerted that a very small subset of messages in one availability zone of the US East point of presence might not have been delivered right away to subscribers in the same region. Publish and Subscribe calls returned no errors, even though some messages did not appear in the responses.

    Misrouted requestsInconsistent reads from a data store
    Trigger

    During planned internal load testing, a group of internal routing servers was removed from service.

    Root cause
    Configuration change
    Component
    Service discovery
    Contributing factor
    –
    Detection

    PubNub's internal monitoring alerted at 12:10 UTC; synthetic monitoring then confirmed that no more messages were being missed.

    Remediation
    • Performed a rolling restart of the affected servers to clear the outdated routing addresses
    Action items
    • Deploy a fix to all publishing servers worldwide so that outdated internal routing addresses are retired correctly
    View case
Check your cluster for this

This case involves Service discovery. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

Open kubegap

By root cause1

Configuration change1 case

Component
Service discovery
Contributing factor
–
Organisation
PubNub
  1. IL-0560 Some PubNub messages in the US East point of presence were misrouted with no error and not delivered right away
    PubNub2026