Is there an CometChat outage?
CometChat status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for CometChat and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: April 28, 2023, 7:49 a.m.
Description: The Incident: Starting at 01:33am MST on 04/28/2023, CometChat became aware of degraded performance on our API clusters for some apps hosted in the EU region. Root Cause: On further investigation, we noticed that one of our primary databases on that cluster was not accessible intermittently due to increased load on the database which resulted in unresponsive database infrastructure leading to partial service disruption. Resolution: As an immediate action, our DevOps team bypassed the proxy and restored the services by 02:06am MST. To ensure this doesn't happen again our database solution architects and engineers have optimised the database proxy server configurations for optimal performance.
Status: Resolved
Impact: None | Started At: April 28, 2023, 7:33 a.m.
Description: The Incident: Starting at 01:33am MST on 04/28/2023, CometChat became aware of degraded performance on our API clusters for some apps hosted in the EU region. Root Cause: On further investigation, we noticed that one of our primary databases on that cluster was not accessible intermittently due to increased load on the database which resulted in unresponsive database infrastructure leading to partial service disruption. Resolution: As an immediate action, our DevOps team bypassed the proxy and restored the services by 02:06am MST. To ensure this doesn't happen again our database solution architects and engineers have optimised the database proxy server configurations for optimal performance.
Status: Resolved
Impact: None | Started At: April 28, 2023, 7:33 a.m.
Description: The Incident: Starting at 10:40 am MST on 02/20/2023, CometChat became aware of API endpoints hosted in the US region. Root Cause: On investigation, the team found an increased load on the database which resulted in unresponsive database infrastructure leading to partial service disruption. Resolution: As an immediate action, our DevOps team bypassed the proxy and restored the services by 10:50am MST. To ensure this doesn't happen again our database solution architects and engineers have optimized the database proxy server configurations for optimal performance.
Status: Resolved
Impact: None | Started At: Feb. 20, 2023, 5:40 p.m.
Description: The Incident: Starting at 10:40 am MST on 02/20/2023, CometChat became aware of API endpoints hosted in the US region. Root Cause: On investigation, the team found an increased load on the database which resulted in unresponsive database infrastructure leading to partial service disruption. Resolution: As an immediate action, our DevOps team bypassed the proxy and restored the services by 10:50am MST. To ensure this doesn't happen again our database solution architects and engineers have optimized the database proxy server configurations for optimal performance.
Status: Resolved
Impact: None | Started At: Feb. 20, 2023, 5:40 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.
