Incident Library
Applied filters Root causeCapacity exhaustionComponentCloud load balancerOrganisationPubNubClear 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-0558 New PubNub instance types in FRA hit connectivity limits, and Pub/Sub, History and Presence saw intermittent errors
    PubNub2025
    Symptoms

    From 08:15 UTC on Friday 27 June 2025, PubNub's Pub/Sub, History and Presence services showed occasional, intermittent increases in latency and server errors in the Europe (FRA) region.

    High latencyHigh error rate
    Trigger

    PubNub introduced new instance types to its system to get access to more cloud server capacity across its regions.

    Root cause
    Capacity exhaustion
    Component
    Cloud load balancer
    Contributing factor
    Partial rolloutUnverified assumptionMonitoring blind spot
    Remediation
    • Configured the affected services to run on other instance types
    • Launched more capacity
    Action items
    • Make the new instance types emit metrics on OS thresholds and limits, so approaching or exceeding a limit is detected on any instance type
    • Scale ahead of demand and route traffic according to instance type
    View case
Check your cluster for this

This case involves Cloud load balancer. 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

Capacity exhaustion1 case

Component
Cloud load balancer
Contributing factor
Unverified assumptionMonitoring blind spotPartial rollout
Organisation
PubNub
  1. IL-0558 New PubNub instance types in FRA hit connectivity limits, and Pub/Sub, History and Presence saw intermittent errors
    PubNub2025