Is there an PubNub outage?
PubNub status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for PubNub and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 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** At 18:36 UTC on August 9, 2022, we observed a small number of errors served across all PubNub services in our US-West PoP. We identified a configuration sync issue with a load balancer, removed it from service, and the issue was resolved at 19:29 UTC. This issue occurred because alerting did not include the specific configuration problem affecting the load balancer which had to be identified through investigation. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we are working to enhance server-level monitoring and alerting in the coming days. This will ensure we are immediately aware of any recurrence and can act quickly to resolve it.
Status: Postmortem
Impact: Minor | Started At: Aug. 9, 2022, 6:56 p.m.
Description: ### **Problem Description, Impact, and Resolution** At 18:36 UTC on August 9, 2022, we observed a small number of errors served across all PubNub services in our US-West PoP. We identified a configuration sync issue with a load balancer, removed it from service, and the issue was resolved at 19:29 UTC. This issue occurred because alerting did not include the specific configuration problem affecting the load balancer which had to be identified through investigation. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we are working to enhance server-level monitoring and alerting in the coming days. This will ensure we are immediately aware of any recurrence and can act quickly to resolve it.
Status: Postmortem
Impact: Minor | Started At: Aug. 9, 2022, 6:56 p.m.
Description: At 01:08 UTC on August 3rd we observed that messages published to persistence from our Europe PoP from 23:32 August 2nd to 00:41 UTC August 3rd were not accessible by History API call, and push notifications sent during the same period were not delivered. We implemented a fix and the issue was resolved at 02:04 UTC on August 3rd resulting in stored messages being backfilled and accessible as expected. Push notifications sent during the period in question remained undelivered due to expiry. This issue occurred because there was an error in our server code that went undetected, resulting in messages waiting in the queue unprocessed. To prevent a similar issue from occurring in the future we expanded testing coverage to ensure messages are written to persistence as intended. In the coming days we will implement enhanced internal alerting to provide early warning of such an occurrence in the future.
Status: Postmortem
Impact: None | Started At: Aug. 3, 2022, 1:08 a.m.
Description: At 01:08 UTC on August 3rd we observed that messages published to persistence from our Europe PoP from 23:32 August 2nd to 00:41 UTC August 3rd were not accessible by History API call, and push notifications sent during the same period were not delivered. We implemented a fix and the issue was resolved at 02:04 UTC on August 3rd resulting in stored messages being backfilled and accessible as expected. Push notifications sent during the period in question remained undelivered due to expiry. This issue occurred because there was an error in our server code that went undetected, resulting in messages waiting in the queue unprocessed. To prevent a similar issue from occurring in the future we expanded testing coverage to ensure messages are written to persistence as intended. In the coming days we will implement enhanced internal alerting to provide early warning of such an occurrence in the future.
Status: Postmortem
Impact: None | Started At: Aug. 3, 2022, 1:08 a.m.
Description: ### **Problem Description, Impact, and Resolution** At 15:45 UTC on 2022-06-27, we observed delays in push notifications sent and messages written to history, as well as excess presence join & leave events. In response, we scaled the underlying systems supporting these services,, and the issue was resolved at 16:05 UTC. This issue occurred because our third party service provider experienced an outage in the US-East PoP. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we are updating our processes to ensure that malfunctioning nodes are restarted in a way that will preserve their state for analysis, as well as updating our runbook for scaling the system.
Status: Postmortem
Impact: None | Started At: June 27, 2022, 4:16 p.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.
