Last checked: a minute ago
Get notified about any outages, downtime or incidents for Orderful and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Orderful.
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 |
Mailjet Email Content | Active |
Transaction Delivery | Active |
Trading Partner Delivery Services | Active |
UI | Active |
Rules Engine | Active |
Transaction Validation | Active |
UI | Active |
View the latest incidents for Orderful and check for official updates:
Description: The system has been stable for over two hours. Closing as resolved.
Status: Resolved
Impact: Major | Started At: April 20, 2021, 4:57 p.m.
Description: During a brief window between 2:01 PM PST and 2:15 pm PST a configuration issue caused some HTTP requests to POST /v2/transactions to be incorrectly rejected with a 4xx status code. System wide the total number of rejected transactions was < 100, however we are unable to differentiate between the incorrectly rejected requests and ones which should have been correctly rejected so the total number of requests rejected incorrectly could be less. If your company did experience any outbound transaction failures during this time, simply repost your transactions if you have not already done so. All requests will be handled correctly. During this incident, data integrity was maintained, no transactions were lost, and no inbound transactions were impacted.
Status: Postmortem
Impact: Major | Started At: Nov. 9, 2020, 11:45 p.m.
Description: During a brief window between 2:01 PM PST and 2:15 pm PST a configuration issue caused some HTTP requests to POST /v2/transactions to be incorrectly rejected with a 4xx status code. System wide the total number of rejected transactions was < 100, however we are unable to differentiate between the incorrectly rejected requests and ones which should have been correctly rejected so the total number of requests rejected incorrectly could be less. If your company did experience any outbound transaction failures during this time, simply repost your transactions if you have not already done so. All requests will be handled correctly. During this incident, data integrity was maintained, no transactions were lost, and no inbound transactions were impacted.
Status: Postmortem
Impact: Major | Started At: Nov. 9, 2020, 11:45 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Aug. 25, 2020, 7:14 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: Aug. 25, 2020, 7:14 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.