Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Flowspace and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Flowspace.
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 |
---|---|
Document printing | Active |
Label purchasing | Active |
Seller Integrations | Active |
Shopify Integration | Active |
View the latest incidents for Flowspace and check for official updates:
Description: Shipping label generation has been fully restored at this time.
Status: Resolved
Impact: None | Started At: June 1, 2022, 9:17 p.m.
Description: Shipping label generation has been fully restored at this time.
Status: Resolved
Impact: None | Started At: June 1, 2022, 9:17 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: May 6, 2022, 1:39 p.m.
Description: At approximately 12:00am ET on the morning of March 26, we began a normal database upgrade process. The upgrade appeared to complete normally, but near 3:00am ET we noticed load spikes on our primary database. Shortly after, it became unresponsive. We began working with our infrastructure provider and determined that the upgrade had caused corruption and our primary database was unresponsive. We then began the process of restoring our data from a replica and bringing up a new primary instance. At approximately 4:00pm ET, we completed the restoration and brought our services back online. We did not experience any data loss, and will continue to monitor our services to ensure they function normally.
Status: Resolved
Impact: Critical | Started At: March 26, 2022, 8:05 a.m.
Description: At approximately 12:00am ET on the morning of March 26, we began a normal database upgrade process. The upgrade appeared to complete normally, but near 3:00am ET we noticed load spikes on our primary database. Shortly after, it became unresponsive. We began working with our infrastructure provider and determined that the upgrade had caused corruption and our primary database was unresponsive. We then began the process of restoring our data from a replica and bringing up a new primary instance. At approximately 4:00pm ET, we completed the restoration and brought our services back online. We did not experience any data loss, and will continue to monitor our services to ensure they function normally.
Status: Resolved
Impact: Critical | Started At: March 26, 2022, 8:05 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.