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 03:27 UTC on 2022-16-02, we observed errors with Channel Group registrations \(add/remove channels to/from channel groups\) in the South AP PoP \(Mumbai\). We immediately escalated to our storage provider while we routed storage traffic to US West to mitigate the issue. The issue was resolved at 04:30 UTC on 2022-02-15. This issue occurred due to a bug in our storage providers' platform. Our internal monitoring detected the errors which allowed us to take immediate actions with rerouting traffic and escalating to our provider. ### **Mitigation Steps and Recommended Future Preventative Measures** We plan to migrate our Mumbai PoP to Kubernetes which will allow us to more efficiently reroute traffic to another PoP when needed. Our storage provider will resolve the existing bug.
Status: Postmortem
Impact: Critical | Started At: Feb. 16, 2022, 3:41 a.m.
Description: ### **Problem Description, Impact, and Resolution** At 15:44 UTC on 2022-02-04, we observed degraded performance with our functions in the Mumbai region. When we realized a drop in service, we doubled our internal capacity to account for the degraded performance. The issue was resolved for most customers at 19:11 UTC on 2022-02-04, but a small subset of affected customers continued to see issues through 04:00 UTC on 2022-02-05. The reason for the degraded performance was due to a service failure with our vendor. When the service failed, we did not have alerting in place to proactively detect the failure. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we have set up the necessary alerting of our service and continue to work with the vendor to understand the underlying cause.
Status: Postmortem
Impact: Minor | Started At: Feb. 4, 2022, 6:55 p.m.
Description: ### **Problem Description, Impact, and Resolution** At 15:44 UTC on 2022-02-04, we observed degraded performance with our functions in the Mumbai region. When we realized a drop in service, we doubled our internal capacity to account for the degraded performance. The issue was resolved for most customers at 19:11 UTC on 2022-02-04, but a small subset of affected customers continued to see issues through 04:00 UTC on 2022-02-05. The reason for the degraded performance was due to a service failure with our vendor. When the service failed, we did not have alerting in place to proactively detect the failure. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we have set up the necessary alerting of our service and continue to work with the vendor to understand the underlying cause.
Status: Postmortem
Impact: Minor | Started At: Feb. 4, 2022, 6:55 p.m.
Description: We apologize for the impact this may have had on your service. Please reach out to us by contacting PubNub Support ([email protected]) if you wish to discuss the impact on your service. This incident has been resolved, and we will follow up with a post-mortem soon.
Status: Resolved
Impact: Minor | Started At: Feb. 4, 2022, 4:25 p.m.
Description: We apologize for the impact this may have had on your service. Please reach out to us by contacting PubNub Support ([email protected]) if you wish to discuss the impact on your service. This incident has been resolved, and we will follow up with a post-mortem soon.
Status: Resolved
Impact: Minor | Started At: Feb. 4, 2022, 4:25 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.