Is there an Gini outage?
Gini status: Systems Active
Last checked: 5 minutes ago
Get notified about any outages, downtime or incidents for Gini and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 5 minutes 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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 3, 2017, 7:45 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: April 13, 2017, 9:07 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Feb. 17, 2017, 12:05 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Feb. 17, 2017, 12:05 p.m.
Description: Gini operates it's services from two datacenters in Germany run by the same provider. We are currently using one of them to accept external traffic and processing is spread between the two locations. The outage on the 14th of February was caused by another customer in our ingress datacenter who has a special setup and deployed a erroneous network configuration. The infrastructure of our provider has dedicated network equipment and safety mechanisms in place to isolate misbehaving network segments and protect the core infrastructure. Unfortunately these mechanisms have resorted too late and the errors propagated to the core infrastructure which also affected Ginis external access points. Once the problem was identified our provider took these immediate countermeasures: - The customer causing the erroneous network configuration was shut down immediately and was reenabled only after their systems were isolated with another dedicated firewall. - The firewall is a managed system by our provider and they will ensure that a similar problem cannot happen again. After these measures have been taken the network was operational again and Ginis backend recovered from the outage. There are the next steps our provider initiated to prevent further events of this kind: - Other customers with similar setups are identified and will be isolated asap. - The special setup operated by the other customer is no longer allowed and new requests will be denied. - Our provider is in contact with the vendor of the core network components to figure out why the safety mechanisms did not work on time. Gini and our datacenter provider are both deeply sorry about the outage and the impact it had on Ginis customers. We strive to offer the best products and services and we haven not lived up to this goal. Feel free to contact us at [email protected] if you have any questions about Gini or this outage.
Status: Postmortem
Impact: Major | Started At: Feb. 14, 2017, 12:52 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.
