Is there an Etleap outage?
Etleap status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Etleap and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Etleap and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Etleap.
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 |
|---|---|
| Integrations | Active |
| EU Hosted App (app.eu.etleap.com) | Active |
| API | Active |
| Event Streams | Active |
| Pipelines | Active |
| UI | Active |
| US Hosted App (app.etleap.com) | Active |
| API | Active |
| Event Streams | Active |
| Pipelines | Active |
| UI | Active |
View the latest incidents for Etleap and check for official updates:
Description: All missed notifications have now been sent.
Status: Resolved
Impact: Minor | Started At: April 24, 2023, 4:08 p.m.
Description: On April 21, 2023, between 01:01 and 02:24 UTC, we experienced an outage for our Event Stream endpoints. Any data sent to Event Stream endpoints during this time was unfortunately lost. We take incidents like this very seriously, and we are sorry for any data integrity issues caused by this. The root cause of the issue was an expired certificate that prevented our containers from starting. During startup, the container attempted to fetch a dependency from a third-party service. However, since the certificate had expired, the fetch failed, causing the container to fail to start. With old nodes being decommissioned and new ones being started over time, the entire cluster eventually became depleted. Additionally, due to a configuration error, the endpoint’s load balancer remained "open" even after all the nodes became unhealthy. This resulted in traffic being routed to unhealthy nodes, which again resulted in the endpoint returning successful \(200\) rather than unsuccessful \(500\) status codes. To prevent this issue in the future, we will upgrade our containers so that they do not need to fetch any dependencies on startup. Additionally, we will change our configuration so that the load balancer stays “closed” if all nodes in the cluster become unhealthy, resulting in 500 rather than 200 response status codes being returned.
Status: Postmortem
Impact: Critical | Started At: April 21, 2023, 1 a.m.
Description: A fix has now been deployed and the incident is now resolved.
Status: Resolved
Impact: Major | Started At: April 20, 2023, 10:56 a.m.
Description: The fix has now been deployed and the UI is fully-operational again.
Status: Resolved
Impact: Major | Started At: April 18, 2023, 2:25 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: April 17, 2023, 4:38 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.
