Company Logo

Is there an PubNub outage?

PubNub status: Systems Active

Last checked: 8 minutes ago

Get notified about any outages, downtime or incidents for PubNub and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

PubNub outages and incidents

Outage and incident data over the last 30 days for PubNub.

There have been 1 outages or incidents for PubNub in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for PubNub

Outlogger tracks the status of these components for Xero:

Functions Service Active
Key Value store Active
Scheduler Service Active
Vault Active
Asia Pacific Points of Presence Active
European Points of Presence Active
North America Points of Presence Active
Southern Asia Points of Presence Active
Access Manager Service Active
App Context Service Active
DNS Service Active
Mobile Push Gateway Active
MQTT Gateway Active
Presence Service Active
Publish/Subscribe Service Active
Realtime Analytics Service Active
Storage and Playback Service Active
Stream Controller Service Active
Administration Portal Active
PubNub Support Portal Active
SDK Documentation Active
Website Active
Component Status
Active
Functions Service Active
Key Value store Active
Scheduler Service Active
Vault Active
Active
Asia Pacific Points of Presence Active
European Points of Presence Active
North America Points of Presence Active
Southern Asia Points of Presence Active
Active
Access Manager Service Active
App Context Service Active
DNS Service Active
Mobile Push Gateway Active
MQTT Gateway Active
Presence Service Active
Publish/Subscribe Service Active
Realtime Analytics Service Active
Storage and Playback Service Active
Stream Controller Service Active
Active
Administration Portal Active
PubNub Support Portal Active
SDK Documentation Active
Website Active

Latest PubNub outages and incidents.

View the latest incidents for PubNub and check for official updates:

Updates:

  • Time: May 16, 2024, 12:48 a.m.
    Status: Postmortem
    Update: ### **Problem Description, Impact, and Resolution**  On Sunday, May 12, 2024 at 14:16 UTC, customers using PubNub’s legacy Access Manager Version 2 may have experienced increased errors and latency across all services in our US-East point of presence. After investigation, we discovered that several database nodes were failing. We were prepared to fail out of that region when the nodes recovered and the errors stopped by 15:20 UTC.  Customers using Access Manager Version 3 were unaffected because Version 3 does not leverage a database.  ### **Mitigation Steps and Recommended Future Preventative Measures**  To prevent a similar issue from occurring in the future, we are increasing allocated resources in the affected infrastructure, as well as tuning the auto-scale threshold. Additionally, we continue to encourage and assist customers using Access Manager Version 2 to migrate to Version 3. For information on migrating to Access Manager Version 3, please refer to our [Migration Guide](https://www.pubnub.com/docs/general/resources/migration-guides/pam-v3-migration), or contact [[email protected]](mailto:[email protected]) for assistance.
  • Time: May 12, 2024, 3:41 p.m.
    Status: Resolved
    Update: From 14:16 UTC to 15:20 UTC on May 12, 2024, users may have experienced increased latency and errors across all PubNub services in our US East PoP. Our Engineering teams applied a fix and the issue has been resolved since 15:20 UTC. A root cause analysis will be posted soon.

Updates:

  • Time: March 20, 2024, 6:27 p.m.
    Status: Postmortem
    Update: ### **Problem Description, Impact, and Resolution**  At 00:06 UTC on March 17, 2024, we observed increased error rates and latency in our Tokyo region for History calls. We then identified the source of latency and errors were due to our third-party provider for storage. We alerted the third-party provider, which then restarted the impacted storage nodes, and the issue was resolved at t 00:47 UTC on March 17, 2024.   ‌ ### **Mitigation Steps and Recommended Future Preventative Measures**  To prevent a similar issue from occurring in the future we have added monitoring to the swap space level on our servers so we will have better alerting if such issues with our third-party provider occur in the future.
  • Time: March 17, 2024, 1:24 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 17, 2024, 1:24 a.m.
    Status: Monitoring
    Update: We have not seen any errors or increased latency for ~45 minutes. We will continue to monitor history to validate the resolution.
  • Time: March 17, 2024, 1:06 a.m.
    Status: Monitoring
    Update: The elevated state of History errors and latency has returned to normal. We will continue to monitor the incident
  • Time: March 17, 2024, 12:43 a.m.
    Status: Investigating
    Update: Around 00:06 UTC we began to notice increasing errors and latency for History in Tokyo region. We are investigating this incident.

Updates:

  • Time: March 8, 2024, 2:11 p.m.
    Status: Postmortem
    Update: ### **Problem Description, Impact, and Resolution**  Around 14:45 UTC, March 1, 2024, we observed the Presence service started experiencing missed Presence webhook calls. The missed webhook calls were due to a migration of the Presence webhooks across multiple customers. We rolled back the migration for all customers in case the issue was broader and created a status page for transparency. Further investigation showed the missed webhook calls were isolated to a small subset of customers.  ### **Mitigation Steps and Recommended Future Preventative Measures**  To prevent a similar issue from occurring, we added and deployed redirect functionality in our Events & Actions service and added monitoring for future webhook migrations.
  • Time: March 2, 2024, 2:39 a.m.
    Status: Resolved
    Update: This incident has been resolved with no errors observed for the last 30 minutes. We apologize for any impact this may have had on your service. Don't hesitate to contact us by reaching PubNub Support ([email protected]) if you wish to discuss the impact on your service. An RCA will be provided soon.
  • Time: March 2, 2024, 2:08 a.m.
    Status: Monitoring
    Update: A fix was implemented at 01:45 UTC. We are monitoring the results for the next 30 minutes.
  • Time: March 2, 2024, 1:37 a.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: March 2, 2024, 1:26 a.m.
    Status: Investigating
    Update: `Around 14:45 UTC (06:45 PT) March 01, the Presence service began to experience missed Presence webhook calls for some users. PubNub Technical Staff is investigating and more information will be posted as it becomes available. If you are experiencing issues that you believe to be related to this incident, please report the details to PubNub Support ([email protected]).

Updates:

  • Time: Oct. 31, 2023, 3:59 p.m.
    Status: Postmortem
    Update: ### **Problem Description, Impact, and Resolution**  On October 30, 2023 at 17:52 UTC, we observed a high number of errors and increased latency in our Subscribe service, mostly in our US-East point of presence. This was a result of increased Subscribe traffic in the region growing since around 13:45 UTC.  Customers making subscribe API calls at the time may have experienced increased response latency, or failures with error. We increased service capacity, and memory allocation in all regions, and the issue was resolved on October 30, 2023 at 18:23 UTC.  ### **Mitigation Steps and Recommended Future Preventative Measures**  To prevent a similar issue from occurring in the future, we updated our monitoring to provide early warning of increased Subscribe traffic, giving us sufficient time to scale before issues occur.
  • Time: Oct. 30, 2023, 6:59 p.m.
    Status: Resolved
    Update: This incident has been resolved with no errors observed for the last 30 minutes. We apologize for any impact this may have had on your service. Don't hesitate to contact us by reaching PubNub Support ([email protected]) if you wish to discuss the impact on your service. An RCA will be provided soon.
  • Time: Oct. 30, 2023, 6:31 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented. We will continue to provide regular updates.
  • Time: Oct. 30, 2023, 6:11 p.m.
    Status: Investigating
    Update: Starting around 13:45 UTC, we began observing elevated latency and errors in calls made to our Subscribe endpoint in our US East point of presence. PubNub Technical Staff is investigating, and more information will be posted as it becomes available. We apologize for any impact this may have had on your service. Don't hesitate to contact us by reaching PubNub Support ([email protected]) if you wish to discuss the impact on your service.

Updates:

  • Time: Oct. 3, 2023, 8:21 p.m.
    Status: Postmortem
    Update: We received a notification from an infrastructure provider that they were having issues that could affect our US-East Point of Presence. On that recommendation, we shifted our infrastructure to avoid any potential problems. We posted this incident in advance of shifting, in order to keep our customers informed of any issues that might arise. In the end, we were able to make the changes \(and revert them back once the provider was stable again\) without any disruption to PubNub services. As always, please contact PubNub Support with any questions about this \(or other\) concerns or issues.
  • Time: Sept. 28, 2023, 10:42 p.m.
    Status: Resolved
    Update: We've had no customer impact from this configuration change, and are closing this incident. As always, contact PubNub support with any questions.
  • Time: Sept. 28, 2023, 10 p.m.
    Status: Monitoring
    Update: We have completed our changes, with no customer impact reported. We will continue to monitor the situation closely.
  • Time: Sept. 28, 2023, 9:19 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Sept. 28, 2023, 9:18 p.m.
    Status: Investigating
    Update: We are proactively reconfiguring our services, based on advice from an infrastructure provider that is experiencing issues in our US-East point-of-presence. There is no customer impact at this time, and we will update this page if we see any impact during this process. Please contact PubNub support if you experience any issues.

Check the status of similar companies and alternatives to PubNub

Qualys
Qualys

Issues Detected

Netskope Trust Portal
Netskope Trust Portal

Issues Detected

Ping Identity
Ping Identity

Systems Active

Veracode
Veracode

Systems Active

OPSWAT
OPSWAT

Systems Active

Sonatype
Sonatype

Systems Active

Aqua Security
Aqua Security

Systems Active

appviewx
appviewx

Systems Active

Signifyd
Signifyd

Systems Active

Alert Logic
Alert Logic

Systems Active

Red Canary
Red Canary

Systems Active

Frequently Asked Questions - PubNub

Is there a PubNub outage?
The current status of PubNub is: Systems Active
Where can I find the official status page of PubNub?
The official status page for PubNub is here
How can I get notified if PubNub is down or experiencing an outage?
To get notified of any status changes to PubNub, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of PubNub every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does PubNub do?
Utilize hosted real-time APIs to create interactive remote experiences with features such as in-app chat, push notifications, and location tracking.