Is there an Alloy outage?
Alloy status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Alloy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for Alloy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Alloy.
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 |
|---|---|
| Customer Dashboard | Active |
| Production API | Active |
| Sandbox API | Active |
| SDK | Active |
| Webhooks | Active |
View the latest incidents for Alloy and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: March 6, 2024, 1:42 p.m.
Description: From 6:01am to 6:12am we experienced a spike in latency following a spike in throughput from a third party vendor. Service is fully restored and we will continue monitoring and follow up to prevent this moving forward.
Status: Resolved
Impact: Major | Started At: Feb. 29, 2024, 11:04 a.m.
Description: We released a change to our dashboard that was causing evaluation page to not display, which also affected journey applications page. Outage happened from 13:30 to 13:52 EST.
Status: Resolved
Impact: None | Started At: Feb. 15, 2024, 6:30 p.m.
Description: During this time there was a brief loss of connectivity to our API and dashboard (about 4 minutes). Initially we believed this to be related to a routine security networking change which we rolled back immediately. However, working with AWS on a RCA, we determined that the service interruption was actually the result of a rarely exposed load balancer bug within the AWS ALB service. A workaround is pending to prevent this bug from surfacing again.
Status: Resolved
Impact: Major | Started At: Jan. 26, 2024, 8:59 p.m.
Description: Between the hours of 22:02 and 22:12 ET (10 minutes), a scheduled database migration that had been tested successfully in lower environments acquired an unintended long lock on a database table, resulting in a backup of queries and increasingly high latencies. The migration was automatically detected and killed, freeing up database performance and returning operations to normal. The postmortem process is underway and multiple new checks for this type of failure are already in process.
Status: Resolved
Impact: Major | Started At: Jan. 17, 2024, 3 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.
