Finale Inventory Outage History

Finale Inventory is up right now

Finale Inventory had 5 outages in the last 2 years totaling 14h 8m of downtime — averaging 0.2 incidents per month.

There were 5 Finale Inventory outages since October 18, 2025 totaling 14h 8m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.finaleinventory.com

Notice June 29, 2026

Database outage

Detected by Pingoru
Jun 29, 2026, 07:34 PM UTC
Resolved
Jun 29, 2026, 09:51 PM UTC
Duration
2h 16m
Timeline · 4 updates
  1. identified Jun 29, 2026, 07:34 PM UTC

    We have identified an issue affecting our primary database. We have been working to identify the cause and are working to return the application to a working state.

  2. monitoring Jun 29, 2026, 07:52 PM UTC

    We have reverted all recently shipped code and have turned on integrations. Integrations will come online over the next two hours. We are continuing to monitor our database during that time.

  3. monitoring Jun 29, 2026, 09:30 PM UTC

    We are continuing to monitor the database. Integration tasks are still coming online and database load appears to be back to normal.

  4. resolved Jun 29, 2026, 09:51 PM UTC

    Integration tasks are fully online. This incident should be resolved.

Read the full incident report →

Notice May 23, 2026

Scheduled database maintenance causing system-wide outage

Detected by Pingoru
May 23, 2026, 12:49 AM UTC
Resolved
May 23, 2026, 01:57 AM UTC
Duration
1h 8m
Timeline · 2 updates
  1. identified May 23, 2026, 12:49 AM UTC

    We are starting a scheduled database maintenance period at 9pm Eastern which will last around 2 hours. The system will become unavailable for at least 15 minutes during this time.

  2. resolved May 23, 2026, 01:57 AM UTC

    The migration has completed. Integrations are coming online slowly over the next hour.

Read the full incident report →

Major March 30, 2026

Authentication failures

Detected by Pingoru
Mar 30, 2026, 02:40 PM UTC
Resolved
Mar 30, 2026, 03:39 PM UTC
Duration
58m
Timeline · 2 updates
  1. identified Mar 30, 2026, 02:40 PM UTC

    We are aware of an authentication issue with the Descartes Global Authentication Portal that is preventing some customers from accessing the Finale Inventory application. These errors are intermittent, so, we suggest to keep trying to login until it succeeds. Our teams are actively working on a fix, and we apologize for the inconvenience.

  2. resolved Mar 30, 2026, 03:39 PM UTC

    Login is resolved for all customers, in case of questions, please submit a ticket to our support team.

Read the full incident report →

Notice October 20, 2025

Degraded integration performance

Detected by Pingoru
Oct 20, 2025, 01:54 PM UTC
Resolved
Oct 20, 2025, 09:52 PM UTC
Duration
7h 57m
Timeline · 7 updates
  1. identified Oct 20, 2025, 01:54 PM UTC

    We are investigating issues affecting report generation, integrations, and barcode scanner syncing. Some customers may experience delays or failed syncs. Our team is actively working to identify the cause and restore normal operation. For further inquiries, please contact [email protected]

  2. identified Oct 20, 2025, 02:40 PM UTC

    Most errors appear to be related to an ongoing incident from AWS, see https://health.aws.amazon.com/health/status?path=open-issues We are throttling automatic integration tasks at least over the next hour to allow our system to recover. We will continue to monitor the incident at AWS and restart services as needed.

  3. monitoring Oct 20, 2025, 04:25 PM UTC

    Amazon has provided an update that most services are recovering, see https://health.aws.amazon.com/health/status?path=service-history: "Oct 20 9:13 AM PDT We have taken additional mitigation steps to aid the recovery of the underlying internal subsystem responsible for monitoring the health of our network load balancers and are now seeing connectivity and API recovery for AWS services. We have also identified and are applying next steps to mitigate throttling of new EC2 instance launches. We will provide an update by 10:00 AM PDT." We have restarted automatic integration tasks and will continue to monitor them as the system comes back online.

  4. identified Oct 20, 2025, 04:54 PM UTC

    After restarting integrations, we are still seeing errors from many of our integration partners (specifically Amazon, ShipStation, and Shopify). Integration tasks can be triggered manually, but we are disabling automatic integration tasks again until Amazon has resolved the incident on their end.

  5. monitoring Oct 20, 2025, 05:56 PM UTC

    We have re-enabled integrations and are not seeing errors. We will continue to monitor the system as it comes back online to full capacity.

  6. monitoring Oct 20, 2025, 06:39 PM UTC

    We have observed several delays in our job processing code, used for UI imports and our Android scanner. We are still investigating, but are restarting customer accounts to mitigate this issue. Also, we are still seeing increased latency for several integration partners as well as our cloud provider, AWS. To mitigate the impact of this on our system, we have restarted integration tasks again which will throttle integration task runs over the next hour.

  7. resolved Oct 20, 2025, 09:52 PM UTC

    All systems appear to have returned to normal operation. Please reach out to support ([email protected]) if you continue to experience disruptions with your account.

Read the full incident report →

Notice October 18, 2025

Temporary Pause in Integrations

Detected by Pingoru
Oct 18, 2025, 03:19 PM UTC
Resolved
Oct 18, 2025, 05:06 PM UTC
Duration
1h 46m
Timeline · 3 updates
  1. identified Oct 18, 2025, 03:19 PM UTC

    We've identified one of our replica databases in an unhealthy state, which began causing application slowness. To prevent a broader impact, we have temporarily paused all integration tasks and are rebooting the affected database. Integrations will resume shortly, and we are actively monitoring the situation.

  2. monitoring Oct 18, 2025, 04:13 PM UTC

    We have resumed the integration tasks and continue monitoring the system.

  3. resolved Oct 18, 2025, 05:06 PM UTC

    This incident has been resolved.

Read the full incident report →