RetailNext Outage History

RetailNext is up right now

RetailNext had 3 outages in the last 2 years totaling 17h 16m of downtime — averaging 0.1 incidents per month.

There were 3 RetailNext outages since April 28, 2026 totaling 17h 16m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://retailnext.instatus.com

Minor September 25, 2026

Some Aurora Sensors Offline Following Firmware Update

Detected by Pingoru
Sep 25, 2026, 01:30 PM UTC
Resolved
Sep 26, 2026, 06:02 AM UTC
Duration
16h 32m
Affected: RetailNext Global Platform
Timeline · 6 updates
  1. monitoring Sep 25, 2026, 01:30 PM UTC

    A small number of Aurora sensors went offline after a recent firmware update. We found the cause and stopped the update from reaching any more sensors. Many of the affected sensors have already reconnected, and our team is testing a fix for the rest. You don't need to do anything, and no hardware needs to be replaced. We'll post another update once the fix is rolled out.

  2. identified Sep 25, 2026, 03:57 PM UTC

    We've confirmed the cause. The new firmware doesn't handle slow or unreachable DNS servers well, so some sensors lose their cloud connection instead of switching to a backup DNS server. To keep your data safe, please don't restart any sensor that shows as offline. Offline sensors keep collecting data, but restarting one before it reconnects can cause data loss. Our team is getting a firmware fix ready and working directly with affected customers to bring their sensors back online. If your sensors are affected, we may contact your IT team for a small network change. No hardware needs to be replaced. We'll post another update once the fix is rolled out.

  3. identified Sep 25, 2026, 06:02 PM UTC

    $1c

  4. identified Sep 25, 2026, 11:02 PM UTC

    The permanent fix has passed our internal testing and is now going out to a first group of sensors. Once we've confirmed it's working well in the field, we'll expand it to all affected sensors. **What you need to do** * **Nothing for the fix itself.** It installs automatically on sensors that are online and connected. No site visit or hardware change is needed. * **Sensors still offline:** these won't receive the fix until they're back online. If you haven't already, apply one of the workarounds from our earlier update. * **If you already made the DNS change:** keep it in place for now. We'll let you know when it's safe to switch back. If you have questions or need help bringing a sensor back online, contact RetailNext Support. We'll post another update when the fix is rolling out to all sensors.

  5. monitoring Sep 26, 2026, 03:18 AM UTC

    $20

  6. resolved Sep 26, 2026, 06:02 AM UTC

    $24

Read the full incident report →

Minor August 31, 2026

Video Playback Issues

Detected by Pingoru
Aug 31, 2026, 09:00 AM UTC
Resolved
Aug 31, 2026, 09:42 AM UTC
Duration
42m
Affected: RetailNext Global Platform
Timeline · 2 updates
  1. identified Aug 31, 2026, 09:00 AM UTC

    We're currently investigating an issue causing some video sessions to be rejected. Our engineering team identified the cause and are scaling up capacity now to restore normal service. We'll share another update as soon as we have more information on resolution timing. We apologize for the disruption and appreciate your patience.

  2. resolved Aug 31, 2026, 09:42 AM UTC

    The issue affecting video session loading has been resolved. All services are back to normal operation. The team is in the process of conducting a full post mortem with actions to prevent this from happening in future. We apologize for the disruption and thank you for your patience.

Read the full incident report →

Minor April 28, 2026

Identified: Cloud services disruption

Detected by Pingoru
Apr 28, 2026, 11:40 PM UTC
Resolved
Apr 28, 2026, 11:42 PM UTC
Duration
2m
Affected: RetailNext Global Platform
Timeline · 2 updates
  1. identified Apr 28, 2026, 11:40 PM UTC

    We have identified and are investigating an issue that may impact cloud services and affect the UI and API endpoints. We apologize for any inconvenience and are working on this with the utmost priority to resolve the issue as soon as possible. Thank you for your patience

  2. resolved Apr 28, 2026, 11:42 PM UTC

    This incident has been resolved. All services are fully operational. Please reach out to [[email protected]](mailto:[email protected]) if you have any questions or concerns. Thanks again for your patience.

Read the full incident report →