Company Logo

Is there an Orderful outage?

Orderful status: Systems Active

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.

Subscribe for updates

Orderful outages and incidents

Outage and incident data over the last 30 days for Orderful.

There have been 0 outages or incidents for Orderful in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for Orderful

Outlogger tracks the status of these components for Xero:

API Active
Mailjet Email Content Active
Trading Partner Delivery Services Active
Rules Engine Active
Transaction Validation Active
UI Active
Component Status
API Active
Mailjet Email Content Active
Active
Trading Partner Delivery Services Active
Active
Rules Engine Active
Transaction Validation Active
UI Active

Latest Orderful outages and incidents.

View the latest incidents for Orderful and check for official updates:

Updates:

  • Time: April 20, 2021, 11:19 p.m.
    Status: Resolved
    Update: The system has been stable for over two hours. Closing as resolved.
  • Time: April 20, 2021, 8:46 p.m.
    Status: Monitoring
    Update: Service from Auth0 has been restored and stable for an hour, hopeful restoration in permanent. We will continue to monitor it before resolving the issue. Marking service as operational for the time being.
  • Time: April 20, 2021, 8:11 p.m.
    Status: Identified
    Update: Service has been restored with degredated performance
  • Time: April 20, 2021, 6:25 p.m.
    Status: Identified
    Update: Issue has become worse. Partner service is aware and treating it as an "all hands on deck" issue. Will continue to monitor.
  • Time: April 20, 2021, 5:03 p.m.
    Status: Identified
    Update: Errors have stopped, logins rename slow. Downgrading to degredation.
  • Time: April 20, 2021, 4:58 p.m.
    Status: Identified
    Update: The issue has been identified with a partner service. We are working with them to resolve the issue.
  • Time: April 20, 2021, 4:57 p.m.
    Status: Investigating
    Update: We are seeing partial errors with our UI authentication service. It is preventing some users from logging into the UI and others are seeing slow log in times. Transaction Processing and API integrations in general are unaffected,

Updates:

  • Time: Nov. 10, 2020, 5:13 p.m.
    Status: Postmortem
    Update: 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.
  • Time: Nov. 10, 2020, 12:18 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 9, 2020, 11:45 p.m.
    Status: Monitoring
    Update: An issue with data migration resulted in failures of requests between 2:01 p.m. and 2:15 p.m. PST. Requests to v2/transactions would have returned status 400 errors. Data integrity was maintained, no transactions were lost and all client requests which returned success status code processed correctly.

Updates:

  • Time: Nov. 10, 2020, 5:13 p.m.
    Status: Postmortem
    Update: 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.
  • Time: Nov. 10, 2020, 12:18 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 9, 2020, 11:45 p.m.
    Status: Monitoring
    Update: An issue with data migration resulted in failures of requests between 2:01 p.m. and 2:15 p.m. PST. Requests to v2/transactions would have returned status 400 errors. Data integrity was maintained, no transactions were lost and all client requests which returned success status code processed correctly.

Updates:

  • Time: Aug. 26, 2020, 3 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 26, 2020, 3 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 25, 2020, 10:21 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 25, 2020, 10:21 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are now monitoring the results.
  • Time: Aug. 25, 2020, 7:14 p.m.
    Status: Identified
    Update: GET /transactions is returning transactions before the rules are applied. Issue has been determined to be a bug that was introduced by a recent deployment. Changes are being made to rectify this. No data was lost and once the fix is applied, transactions can be retrieved as usual.

Updates:

  • Time: Aug. 26, 2020, 3 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Aug. 26, 2020, 3 a.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 25, 2020, 10:21 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Aug. 25, 2020, 10:21 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are now monitoring the results.
  • Time: Aug. 25, 2020, 7:14 p.m.
    Status: Identified
    Update: GET /transactions is returning transactions before the rules are applied. Issue has been determined to be a bug that was introduced by a recent deployment. Changes are being made to rectify this. No data was lost and once the fix is applied, transactions can be retrieved as usual.

Check the status of similar companies and alternatives to Orderful

NetSuite
NetSuite

Systems Active

ZoomInfo
ZoomInfo

Systems Active

SPS Commerce
SPS Commerce

Systems Active

Miro
Miro

Systems Active

Field Nation
Field Nation

Systems Active

Outreach
Outreach

Systems Active

Own Company

Systems Active

Mindbody
Mindbody

Systems Active

TaskRabbit
TaskRabbit

Systems Active

Nextiva
Nextiva

Systems Active

6Sense

Systems Active

BigCommerce
BigCommerce

Systems Active

Frequently Asked Questions - Orderful

Is there a Orderful outage?
The current status of Orderful is: Systems Active
Where can I find the official status page of Orderful?
The official status page for Orderful is here
How can I get notified if Orderful is down or experiencing an outage?
To get notified of any status changes to Orderful, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Orderful every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Orderful do?
This service allows users to efficiently manage and resolve EDI trading partner relationships and transactions in real-time.