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.
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.
Outage and incident data over the last 30 days for PubNub.
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 NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Functions | Active |
| Functions Service | Active |
| Key Value store | Active |
| Scheduler Service | Active |
| Vault | Active |
| Points of Presence | Active |
| Asia Pacific Points of Presence | Active |
| European Points of Presence | Active |
| North America Points of Presence | Active |
| Southern Asia Points of Presence | Active |
| Realtime Network | 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 |
| Website and Portals | Active |
| Administration Portal | Active |
| PubNub Support Portal | Active |
| SDK Documentation | Active |
| Website | Active |
View the latest incidents for PubNub and check for official updates:
Description: ### **Problem Description, Impact, and Resolution** On August 30, 2022 at 8:50 PM UTC, we observed slow or failed logins to our Admin Portal, as well as errors using some functionality within the portal once logged in. We investigated, and found that a third-party provider we use for subscription management was having an operational incident. We did what we could to work around the provider’s issue, and escalated with them. The provider resolved their issue, and the incident was resolved at 5:20 AM UTC on August 31. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we have added work to our roadmap to reduce our dependency on the third-party for Admin Portal logins, preferring to allow a login and alert the user to the reduced functionality in case of an error at the provider. We also added work to our operations backlog to better alert us to errors of this kind from the service provider.
Status: Postmortem
Impact: Minor | Started At: Aug. 31, 2022, 1:56 a.m.
Description: ### **Problem Description, Impact, and Resolution** On August 30, 2022 at 8:50 PM UTC, we observed slow or failed logins to our Admin Portal, as well as errors using some functionality within the portal once logged in. We investigated, and found that a third-party provider we use for subscription management was having an operational incident. We did what we could to work around the provider’s issue, and escalated with them. The provider resolved their issue, and the incident was resolved at 5:20 AM UTC on August 31. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we have added work to our roadmap to reduce our dependency on the third-party for Admin Portal logins, preferring to allow a login and alert the user to the reduced functionality in case of an error at the provider. We also added work to our operations backlog to better alert us to errors of this kind from the service provider.
Status: Postmortem
Impact: Minor | Started At: Aug. 31, 2022, 1:56 a.m.
Description: ### **Problem Description, Impact, and Resolution** At 04:59 UTC on August 10, 2022, we observed an elevated error rate for History and Channel Groups services globally. We contacted our third-party vendor where the affected servers reside, and the issue was resolved at 05:57 UTC when the backlog of requests was processed. This issue occurred because of a faulty process with our vendor that unexpectedly restarted our servers while performing an update. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we are working with our vendor to ensure this process gap is addressed and fixed.
Status: Postmortem
Impact: Minor | Started At: Aug. 10, 2022, 5:15 a.m.
Description: ### **Problem Description, Impact, and Resolution** At 04:59 UTC on August 10, 2022, we observed an elevated error rate for History and Channel Groups services globally. We contacted our third-party vendor where the affected servers reside, and the issue was resolved at 05:57 UTC when the backlog of requests was processed. This issue occurred because of a faulty process with our vendor that unexpectedly restarted our servers while performing an update. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we are working with our vendor to ensure this process gap is addressed and fixed.
Status: Postmortem
Impact: Minor | Started At: Aug. 10, 2022, 5:15 a.m.
Description: ### **Problem Description, Impact, and Resolution** At about 02:45 UTC on August 10, 2022, we observed the Channel Groups service reporting errors in our Mumbai PoP, preventing users from making channel group related API calls there. We contacted our third-party vendor where the affected node resides, and the vendor applied a fix resolving the issue at 03:20 UTC. This issue occurred because of an error in our vendor's configuration that went undetected. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we have confirmed that our vendor has applied a fix which addressed the root cause.
Status: Postmortem
Impact: Minor | Started At: Aug. 10, 2022, 3:02 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
