Is there an Galley Solutions outage?
Galley Solutions status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Galley Solutions and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Galley Solutions and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Galley Solutions.
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 | Active |
| API | Active |
| Webapp | Active |
| Staging | Active |
| API | Active |
| Webapp | Active |
View the latest incidents for Galley Solutions and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: June 27, 2023, 9:02 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: June 27, 2023, 9:02 p.m.
Description: **Background:** The graphQL Federated Gateway \(aka Gateway\) process all requests from the web or customer systems. The Galley team has been slowly over the past few weeks updating and introducing an updated gateway leveraging the Federation 2.0 standard instead of the old 1.0 standard. The initial version of this upgrade was successfully deployed on Tuesday May 30th. An additional small updated to address some small quantity of errors was deployed in the morning of Friday June 2nd. **Problem Observed:** The June 2nd deploy did not have a change to the tests that were run and looked to not have any problems in production but in fact eliminating the targeted small number of errors. But on Monday there were reports of “BadGateway” errors from a wide variety of places. We also observed elevated number of load balancer 502 errors. **Root Cause:** The changes introduced needed additional test cases to force a higher volume of long running transactions that would better trigger the failures. The changes also needed high volume of test traffic to see the affect of a failure would have on other users.
Status: Postmortem
Impact: Major | Started At: June 5, 2023, 4:10 p.m.
Description: **Background:** The graphQL Federated Gateway \(aka Gateway\) process all requests from the web or customer systems. The Galley team has been slowly over the past few weeks updating and introducing an updated gateway leveraging the Federation 2.0 standard instead of the old 1.0 standard. The initial version of this upgrade was successfully deployed on Tuesday May 30th. An additional small updated to address some small quantity of errors was deployed in the morning of Friday June 2nd. **Problem Observed:** The June 2nd deploy did not have a change to the tests that were run and looked to not have any problems in production but in fact eliminating the targeted small number of errors. But on Monday there were reports of “BadGateway” errors from a wide variety of places. We also observed elevated number of load balancer 502 errors. **Root Cause:** The changes introduced needed additional test cases to force a higher volume of long running transactions that would better trigger the failures. The changes also needed high volume of test traffic to see the affect of a failure would have on other users.
Status: Postmortem
Impact: Major | Started At: June 5, 2023, 4:10 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: May 15, 2023, 5:37 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.
