PubNub incident

Presence Server Errors and Elevated Latency

Minor Resolved View vendor source →

PubNub experienced a minor incident on March 10, 2025 affecting North America Points of Presence and European Points of Presence and 1 more component, lasting 1h 12m. The incident has been resolved; the full update timeline is below.

Started
Mar 10, 2025, 08:25 PM UTC
Resolved
Mar 10, 2025, 09:38 PM UTC
Duration
1h 12m
Detected by Pingoru
Mar 10, 2025, 08:25 PM UTC

Affected components

North America Points of PresenceEuropean Points of PresenceAsia Pacific Points of PresencePresence ServiceSouthern Asia Points of Presence

Update timeline

  1. investigating Mar 10, 2025, 08:25 PM UTC

    At about 6:26 PM UTC, Presence service started to experience elevated latencies and server errors in all PoPs. PubNub Technical Staff is currently investigating and more updates will follow once available. If you are experiencing issues and believe them to be related to this incident, please report them to PubNub Support at [email protected].

  2. monitoring Mar 10, 2025, 08:38 PM UTC

    We have identified the issue and have taken effective remediation actions, and our engineers are diligently monitoring the situation to guarantee that stability is fully restored.

  3. monitoring Mar 10, 2025, 09:08 PM UTC

    We continue to monitor the situation to guarantee that stability is fully restored.

  4. resolved Mar 10, 2025, 09:38 PM UTC

    With no further issues observed, the incident has been resolved. We will follow up soon with a root cause analysis. If you believe you experienced impact related to this incident, please report them to PubNub Support at [email protected].

  5. postmortem Mar 13, 2025, 03:47 PM UTC

    ### **Problem Description, Impact, and Resolution** On March 10, 2025, we observed elevated latency and errors in the Presence service across our global points of presence from 18:26 to 18:40 UTC and again from 20:05 to 20:27 UTC. After investigating, we found that a short spike in traffic with an unusual pattern caused a downstream service provider to respond with increased latency, which affected our own response times. While this incident resolved quickly, we are working with the third-party provider to better handle this scenario in the future.