Last checked: 9 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 Tuesday May 2, 2023 at 14:26 UTC observed errors and latency on all services in US East PoP. We modified the configuration to scale faster during high load occurrences, and the issue was resolved on May 2, 2023 at 14:34 UTC. This issue occurred because the monitoring could not ramp up needed services quickly enough. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we modified our monitoring to increase resources more rapidly when needed. These changes were made during the incident and brought resolution to this incident.
Status: Postmortem
Impact: None | Started At: May 2, 2023, 2:30 p.m.
Description: ### **Problem Description, Impact, and Resolution** On Tuesday May 2, 2023 at 14:26 UTC observed errors and latency on all services in US East PoP. We modified the configuration to scale faster during high load occurrences, and the issue was resolved on May 2, 2023 at 14:34 UTC. This issue occurred because the monitoring could not ramp up needed services quickly enough. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we modified our monitoring to increase resources more rapidly when needed. These changes were made during the incident and brought resolution to this incident.
Status: Postmortem
Impact: None | Started At: May 2, 2023, 2:30 p.m.
Description: ### **Problem Description, Impact, and Resolution** On April 21, 2023 at 12:04 UTC, we observed increased latency for Publish API calls to our Mumbai Point of Presence. The issue specifically affected some customers whose publish calls are routed through the PubNub Functions service. We scaled up capacity, and the issue was resolved on April 21, 2023 at 13:40 UTC. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we are implementing changes to our scaling process to better address these traffic patterns and adding improved alerting and monitoring for earlier warning of such issues. This should assist with faster responses if there are repeated intervals of high load then lower load.
Status: Postmortem
Impact: Minor | Started At: April 21, 2023, 1:44 p.m.
Description: ### **Problem Description, Impact, and Resolution** On April 21, 2023 at 12:04 UTC, we observed increased latency for Publish API calls to our Mumbai Point of Presence. The issue specifically affected some customers whose publish calls are routed through the PubNub Functions service. We scaled up capacity, and the issue was resolved on April 21, 2023 at 13:40 UTC. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future, we are implementing changes to our scaling process to better address these traffic patterns and adding improved alerting and monitoring for earlier warning of such issues. This should assist with faster responses if there are repeated intervals of high load then lower load.
Status: Postmortem
Impact: Minor | Started At: April 21, 2023, 1:44 p.m.
Description: ### **Problem Description, Impact, and Resolution** On April 2, 2023 at 15:34 UTC we observed an increased rate of timeouts and errors in our services for Presence, Push, History, Subscribe, and Auth Services in our US East Point of Presence. We identified the issue was related to repair work being performed on this PoP by one of our third party vendors. After identifying the issue, we rerouted traffic from US East to US West and moved the incident to Monitoring status since improvement was observed. Once we received an update from our third-party vendor that the repair work was complete, we routed traffic back to our US East PoP, and the issue was resolved at 17:13 UTC. ### **Mitigation Steps and Recommended Future Preventative Measures** To prevent a similar issue from occurring in the future we will implement more granular monitoring and alerting for early warning of such issues to the affected infrastructure.
Status: Postmortem
Impact: Minor | Started At: April 2, 2023, 4:19 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.