Is there an Gini outage?
Gini status: Systems Active
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Gini and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: a minute ago
Get notified about any outages, downtime or incidents for Gini and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Gini.
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 |
|---|---|
| APIs | Active |
| Banking API | Active |
| User-Center API | Active |
| Document Processing | Active |
| Native Documents | Active |
| Scanned Documents | Active |
| Text Documents | Active |
View the latest incidents for Gini and check for official updates:
Description: Starting Friday around 15:00 we received alerts about reduced API availability and around 15:30 our entire external network was down. Our investigations quickly revealed that this outage is out of our immediate control and we contacted our datacenter provider for additional assistance. Looking from the outside it became clear that our network was no longer announced via BGP or that the routes kept changing. As we learned during the outage this was done by our provider as part of a DDoS mitigation which we fell victim to. Neither Gini nor our provider were the actual target but we were still affected and had to take countermeasures. After it became apparent, that redistributing the traffic alone will not stop the attack, our provider decided to use a number of scrubbing centres to remove the unwanted traffic and gain back control. The attack continued until Sunday morning but our services regained full stability from Saturday 03:30 onwards. We discussed additional options to reduce the time it took to fend off the attack and we and our datacenter provider will continue to optimise the procedures and tools.
Status: Postmortem
Impact: Critical | Started At: March 27, 2020, 3:11 p.m.
Description: We experienced some connectivity issues between 00:53 and 02:39 which resulted in a total downtime of 19 minutes. During that timeframe our APIs were not reachable and no documents could be accepted and processed. We are investigating the events that led to this outage and will provide updates accordingly.
Status: Resolved
Impact: None | Started At: March 27, 2020, midnight
Description: We experienced some connectivity issues between 00:53 and 02:39 which resulted in a total downtime of 19 minutes. During that timeframe our APIs were not reachable and no documents could be accepted and processed. We are investigating the events that led to this outage and will provide updates accordingly.
Status: Resolved
Impact: None | Started At: March 27, 2020, midnight
Description: Our production system was affected by an outage that lasted, with varying degrees of impact for our partners, from 25.11.2019 23:00 until 26.11.2019 03:15. **Document processing and API availability was seriously impacted until 01:15**. The initial outage was caused by a failure in one of our Kubernetes clusters. We operate a redundant control plane but this specific problem still resulted in a downtime of the Kubernetes API server. The API server is vital to the functionality of the cluster and without it the problem spread into wide parts of our infrastructure. After the API functionality was restored we needed longer than anticipated to identify, understand and fix a networking issue that was caused by the API outage in the first place. After the networking problems were fixed we finished the reactivation of affected data stores and databases to restore full service functionality. **No data was lost and all the documents that we accepted have been processed**. We strive to provide the best service and availability to our partners and customers and we didn’t live up to this goal. We already identified ways to circumvent similar issues in the future and we are already working on the implementation. Feel free to contact us at [[email protected]](mailto:[email protected]) if you have any questions about Gini or this outage.
Status: Postmortem
Impact: None | Started At: Nov. 25, 2019, 10:13 p.m.
Description: Our production system was affected by an outage that lasted, with varying degrees of impact for our partners, from 25.11.2019 23:00 until 26.11.2019 03:15. **Document processing and API availability was seriously impacted until 01:15**. The initial outage was caused by a failure in one of our Kubernetes clusters. We operate a redundant control plane but this specific problem still resulted in a downtime of the Kubernetes API server. The API server is vital to the functionality of the cluster and without it the problem spread into wide parts of our infrastructure. After the API functionality was restored we needed longer than anticipated to identify, understand and fix a networking issue that was caused by the API outage in the first place. After the networking problems were fixed we finished the reactivation of affected data stores and databases to restore full service functionality. **No data was lost and all the documents that we accepted have been processed**. We strive to provide the best service and availability to our partners and customers and we didn’t live up to this goal. We already identified ways to circumvent similar issues in the future and we are already working on the implementation. Feel free to contact us at [[email protected]](mailto:[email protected]) if you have any questions about Gini or this outage.
Status: Postmortem
Impact: None | Started At: Nov. 25, 2019, 10:13 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.
