Last checked: 10 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: On Tuesday, 3:39AM MST, our engineers were notified of an issue with AWS's hardware which affected a number of our customers. A hard drive where our database was stored had malfunctioned and stopped working. At 4:05AM MST, this issue was resolved by transferring all traffic to an alternative server. We are working closely with the Amazon AWS team to ensure this issue does not happen in the future.
Status: Resolved
Impact: Major | Started At: Nov. 10, 2020, 10:30 a.m.
Description: On Tuesday, 3:39AM MST, our engineers were notified of an issue with AWS's hardware which affected a number of our customers. A hard drive where our database was stored had malfunctioned and stopped working. At 4:05AM MST, this issue was resolved by transferring all traffic to an alternative server. We are working closely with the Amazon AWS team to ensure this issue does not happen in the future.
Status: Resolved
Impact: Major | Started At: Nov. 10, 2020, 10:30 a.m.
Description: Our Engineering team has resolved the issue. The issue was due to Chrome disabling support for TLS 1.0 & 1.1. While our servers were configured to support TLS 1.2, they were defaulting to TLS 1.1 due to a bug in the Java runtime. This issue has been fixed now. We are continuing to monitor this closely. If you continue to experience problems, please contact us immediately.
Status: Resolved
Impact: Major | Started At: Oct. 28, 2020, 7:01 p.m.
Description: Our Engineering team has resolved the issue. The issue was due to Chrome disabling support for TLS 1.0 & 1.1. While our servers were configured to support TLS 1.2, they were defaulting to TLS 1.1 due to a bug in the Java runtime. This issue has been fixed now. We are continuing to monitor this closely. If you continue to experience problems, please contact us immediately.
Status: Resolved
Impact: Major | Started At: Oct. 28, 2020, 7:01 p.m.
Description: On Saturday, 8:09AM MST, our engineers identified an irregular spike in traffic which resulted in degraded performance for some users. At 8:17AM MST, we were able to resolve this issue by directing this traffic to a separate end-point.
Status: Resolved
Impact: None | Started At: Oct. 17, 2020, 2 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.