Incident History

Back to status page
  1. Oct 21, 2025

    1. Reggora – Ongoing Service Disruption Due to AWS Outage

      Impact: Reggora continues to experience partial service disruptions following the AWS outage. There are intermittent service failures. This affects inbound items from the integration, as well as outbounds from Jaro to Reggora. Our system will continue retrying failed outbounds and jobs automatically once Reggora’s services are fully restored to ensure no data is lost.

      Scope: Only customers utilizing Reggora are impacted. All other Jaro systems remain fully operational.

      Customer Action: No action is required at this time. Our team is closely monitoring the situation and will retry all pending or failed jobs once Reggora confirms stability.

      Current Status: Reggora reports that their systems are partially recovered, but issues remain with LOS integrations, AMC integrations, and general platform usage. Their team continues to work directly with AWS, who is allocating additional resources to support recovery efforts. Reggora is exploring all possible avenues to ensure full restoration as quickly as possible. We will provide updates as new information becomes available or when the issue is fully resolved.

    2. Third-Party Integrations – Service Disruption Due to AWS Outage

      Impact: Reggora is currently experiencing service disruptions following the recent AWS outage. This affects inbound items from the integration, and all of our outbounds from Jaro to Reggora. We'll retry all outbounds and failed jobs once Reggora is back up so that no data will be lost.

      Scope: Only customers utilizing Reggora are impacted. Jaro systems remain operational.

      Customer Action: None required at this time. We will provide updates and retry failed jovs as services are restored by the impacted provider.

      Current Status: We are monitoring our systems and Reggora’s technical team is actively working with AWS to resolve lingering integration and performance issues. They continue to dedicate resources toward full restoration of service.

  2. Oct 20, 2025

    1. **RESOLVED** JaroDesk – Service Disruption Due to AWS Outage

      Impact: Automated features such as JaroBots and real-time order updates are currently not functioning as expected.

      Scope: While the JaroDesk application remains accessible, JaroBots are not executing after actions, and orders are not auto-refreshing with pushed updates. Manual refresh is required to view the most recent order status. Payment status on orders is also affected as part of those pushed updates. Payments are recorded properly, but the order paid status may be inaccurate.

      Customer Action: Please refresh orders manually to ensure you are viewing the latest data. We will advise once full automation functionality is restored.

      Current Status: Functionality disruption is linked to the ongoing AWS US-East outage. We are monitoring the situation closely and will provide updates as they become available. Payment information is intact and in process of being reflected properly.

    2. Third-Party Integrations – Service Disruption Due to AWS Outage

      Impact: Some third-party integrations are currently experiencing disruptions and high rates of degraded performance due to an ongoing outage in AWS's US-East regions.

      Scope: While JaroDesk is unaffected, certain integrations—such as Reggora—are fully down or intermittently unavailable.

      Customer Action: None required at this time. We will provide updates as services are restored by the impacted providers. All data will be retried and sent by Jaro once restored. We will update at that time.

      Current Status: AWS outage is ongoing. This affects many service providers, including Reggora and Encompass / EPC. We are monitoring our systems and integration partners and will post any known affects here. Amazon is working to resolve the issue, but each affected service may have their own remediation timelines

  3. Oct 19, 2025

    1. JaroKit scheduled maintenance

      Impact: JaroKit will be inaccessible for the duration. JaroInspect will have degraded access