Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for Cratejoy and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Cratejoy.
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 |
---|---|
API | Active |
AWS cloudFront | Active |
AWS ec2-us-east-1 | Active |
AWS elasticache-us-east-1 | Active |
AWS elb-us-east-1 | Active |
AWS rds-us-east-1 | Active |
EasyPost - API | Active |
Filestack API | Active |
Mailgun - API | Active |
Marketplace | Active |
Merchant Portal | Active |
Storefront | Active |
Payment Gateways | Active |
Braintree API | Active |
Spreedly Core | Active |
Stripe - API | Active |
View the latest incidents for Cratejoy and check for official updates:
Description: This appears to have been a networking event, either outage or overload prior to getting to our application. We've expanded minimum capacity to this service as a precaution.
Status: Resolved
Impact: Minor | Started At: Sept. 30, 2019, 4:37 p.m.
Description: We've verified paypal checkouts are coming through on the stores affected.
Status: Resolved
Impact: Minor | Started At: Sept. 14, 2019, 9:28 p.m.
Description: We've verified paypal checkouts are coming through on the stores affected.
Status: Resolved
Impact: Minor | Started At: Sept. 14, 2019, 9:28 p.m.
Description: Functionality was restored across all services at 2:48 PM CDT The outage was caused by a failure in one of our master servers, combined with a failure in a system built to replace failing systems automatically. This combination resulted in much of our services to be unable to properly scale and route traffic. Once this was determined we were able to replace servers and migrate services. We apologize for the disruption. We'll be auditing our failure, replacement, and scaling systems to better insulate against this.
Status: Resolved
Impact: Major | Started At: Aug. 22, 2019, 6:56 p.m.
Description: Functionality was restored across all services at 2:48 PM CDT The outage was caused by a failure in one of our master servers, combined with a failure in a system built to replace failing systems automatically. This combination resulted in much of our services to be unable to properly scale and route traffic. Once this was determined we were able to replace servers and migrate services. We apologize for the disruption. We'll be auditing our failure, replacement, and scaling systems to better insulate against this.
Status: Resolved
Impact: Major | Started At: Aug. 22, 2019, 6:56 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.