Is there an CometChat outage?
CometChat status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for CometChat and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for CometChat and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for CometChat.
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 |
|---|---|
| CometChat APIs | Active |
| App Management API | Active |
| Rest API (AU) | Active |
| Rest API (EU) | Active |
| Rest API (IN) | Active |
| Rest API (US) | Active |
| CometChat Frontends | Active |
| Dashboard | Active |
| Website | Active |
| CometChat v2 | Active |
| Client API (EU) | Active |
| Client API (US) | Active |
| WebRTC (EU) | Active |
| WebRTC (US) | Active |
| WebSockets (EU) | Active |
| WebSockets (US) | Active |
| CometChat v3 | Active |
| Client API (EU) | Active |
| Client API (IN) | Active |
| Client API (US) | Active |
| WebRTC (EU) | Active |
| WebRTC (IN) | Active |
| WebRTC (US) | Active |
| WebSocket (IN) | Active |
| WebSockets (EU) | Active |
| WebSockets (US) | Active |
View the latest incidents for CometChat and check for official updates:
Description: Starting at 10:40 PM MST on 28th February 2022, our team noticed degraded performance on one of our API clusters for some apps hosted in the EU region. On further investigation, we noticed that one of our primary databases on that cluster was not accessible intermittently due to an issue with the underlying cloud provider's infrastructure. Our team immediately worked with our cloud provider's support engineers to resolve this issue. Meanwhile, the customers with apps hosted on that cluster faced intermittent access. By 11:20 PM MST, we were able to restore the complete system. Based on the RCA provided by our cloud provider, the database's underlying OS was repeatedly hitting the number of open files limit that resulted in the crash. The report also mentions that this happened due to a known bug in the underlying OS. The bug created a deadlock in IO operations because of a race condition. Our current priority is to work alongside our cloud provider to ensure that such an event does not happen again. We apologize for this disruption.
Status: Postmortem
Impact: Major | Started At: March 1, 2022, 5:40 a.m.
Description: Starting at 10:40 PM MST on 28th February 2022, our team noticed degraded performance on one of our API clusters for some apps hosted in the EU region. On further investigation, we noticed that one of our primary databases on that cluster was not accessible intermittently due to an issue with the underlying cloud provider's infrastructure. Our team immediately worked with our cloud provider's support engineers to resolve this issue. Meanwhile, the customers with apps hosted on that cluster faced intermittent access. By 11:20 PM MST, we were able to restore the complete system. Based on the RCA provided by our cloud provider, the database's underlying OS was repeatedly hitting the number of open files limit that resulted in the crash. The report also mentions that this happened due to a known bug in the underlying OS. The bug created a deadlock in IO operations because of a race condition. Our current priority is to work alongside our cloud provider to ensure that such an event does not happen again. We apologize for this disruption.
Status: Postmortem
Impact: Major | Started At: March 1, 2022, 5:40 a.m.
Description: Our Engineering team has resolved the issue. If you continue to experience problems, please contact us. We apologize for any inconvenience.
Status: Resolved
Impact: None | Started At: Nov. 6, 2021, 12:50 a.m.
Description: Starting at 4:27am MST on October 28, 2021, some customers started experiencing occasional errors and increased latency while using CometChat. Around 4:40 am MST we started receiving database connectivity issues and CometChat wasn’t usable for a few of the customers with apps hosted in our EU region for one of the clusters. Our DevOps team started investigating and found that there was a VPC communication failure, and due to which our application servers were not able to communicate with one of our databases. To resolve the issue they immediately updated the VPC routes to point to a new connection. Our current priority is working alongside our cloud vendor and adding more checkpoints in place to prevent similar problems from happening again. We’re truly sorry for the disruption.
Status: Postmortem
Impact: Major | Started At: Oct. 28, 2021, 10:30 a.m.
Description: Starting at 4:27am MST on October 28, 2021, some customers started experiencing occasional errors and increased latency while using CometChat. Around 4:40 am MST we started receiving database connectivity issues and CometChat wasn’t usable for a few of the customers with apps hosted in our EU region for one of the clusters. Our DevOps team started investigating and found that there was a VPC communication failure, and due to which our application servers were not able to communicate with one of our databases. To resolve the issue they immediately updated the VPC routes to point to a new connection. Our current priority is working alongside our cloud vendor and adding more checkpoints in place to prevent similar problems from happening again. We’re truly sorry for the disruption.
Status: Postmortem
Impact: Major | Started At: Oct. 28, 2021, 10:30 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.
