Is there an Applaud outage?
Applaud status: Systems Active
Last checked: 48 seconds ago
Get notified about any outages, downtime or incidents for Applaud and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 48 seconds ago
Get notified about any outages, downtime or incidents for Applaud and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Applaud.
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 |
|---|---|
| Production EU | Active |
| Production US | Active |
| Tryapplaud EU | Active |
| Tryapplaud US | Active |
View the latest incidents for Applaud and check for official updates:
Description: The instance is up and we continue monitoring it. We will continue to look at ways to prevent these kinds of incidents in the future. Apologies for the incontinence caused by this incident. Applaud Team.
Status: Resolved
Impact: Critical | Started At: May 13, 2024, 1:45 a.m.
Description: We observed issues with the underlying instances where the application services are running and fixed them. Now the services are running without any interruption. We will share the detailed RCA post the full analysis of the incident. Apologies for the inconvenience caused by this incident. Thanks, Applaud Team.
Status: Resolved
Impact: Major | Started At: April 30, 2024, 4:35 p.m.
Description: Tryapplaud Cloud US is down for 5 minutes on 26/03/2024.
Status: Resolved
Impact: None | Started At: March 26, 2024, 5:46 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Feb. 8, 2024, 6:58 a.m.
Description: ## Primary Symptom * Complete unavailability of all services in the EU region, resulting in downtime for all tenants and users accessing the system. ## Initial Investigation & Findings * Analysis revealed that upon termination of the old server within the Auto Scaling Group \(ASG\), the corresponding elastic IP associated with one of the proxy servers utilized by Route 53 \(DNS\) was released, leading to disruption of services. * Few of the customers encountered accessibility challenges, specifically with custom sign-in pages after restoring the services to the Production EU environment. ## Underlying Issues * Further analysis revealed that the reported accessibility issues from customers originated from the inadvertent disabling of cross-zone load balancing during updates to network load balancer IPs. This led to uneven traffic distribution across availability zones\(AZ\), causing instability. * Cross-zone load balancing plays a crucial role in ensuring the stability and resilience of our infrastructure by distributing incoming traffic evenly across healthy targets in multiple AZ. Due to its inadvertent deactivation, the load balancer nodes were only directing traffic to healthy targets within their respective AZ’s, thereby resulting in an unstable instance and the reported accessibility issues by the clients. # **Resolution** * Added back the old IP in DNS and attached that to one of the running proxy servers temporarily to fix the accessibility issues. * Enabled cross-zone load balancing in the Network Load balancer for proper traffic distribution across AZ. * In the next Production scheduled downtime, we will remove the outdated IP address associated with the proxy servers from the DNS configuration. # **Preventive Measures** * We are proactively implementing measures to mitigate automatic adjustments and enhance our configuration review protocols to ensure sustained system stability.
Status: Postmortem
Impact: Critical | Started At: Feb. 6, 2024, 2:09 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.
