Last checked: 9 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: Thanks for your patience!
Status: Resolved
Impact: Maintenance | Started At: July 18, 2020, 11:31 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 17, 2020, 9:35 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: July 17, 2020, 9:35 p.m.
Description: We identified a sub-service that was being overloaded, in turn causing a backup of requests to the merchant portal. We're adjusting that service and looking into the behavior that caused it to overload.
Status: Resolved
Impact: Minor | Started At: July 11, 2020, 11:10 a.m.
Description: Between 1:09 and 2:21 PM CST we suffered an increased error rate across functions affecting both the Merchant Portal and Marketplace. The Merchant dashboard was hardest hit, impacting 10% of requests made, while the Marketplace only saw around 4%. The Merchant Portal uses this service heavily, including in the auto-suggest global search bar. This disruption was caused by a processing anomaly on one node of our primary search cluster. While this service already has built in failover should a node fail, the particular problem did not disable the node but maximized it’s usage drastically lowering the throughput. The result as a user is if you had the luck of being routed to that node, you’d have an extended wait, error or timeout. We’ve already reached out to our cloud provider about the issue of the problem with failover. We are expanding our capacity in our search cluster so that we have extra room for the unexpected going forward.
Status: Postmortem
Impact: Minor | Started At: July 6, 2020, 6:28 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.