Axis Communications incident

SRA v1

Minor Resolved View vendor source →

Axis Communications experienced a minor incident on May 2, 2025, lasting 10d 11h. The incident has been resolved; the full update timeline is below.

Started
May 02, 2025, 09:00 PM UTC
Resolved
May 13, 2025, 08:03 AM UTC
Duration
10d 11h
Detected by Pingoru
May 02, 2025, 09:00 PM UTC

Update timeline

  1. investigating May 02, 2025, 09:00 PM UTC

    We are seeing intermittent performance issues in Secure Remote Access version 1 in the Americas. This will affect connecting to AXIS Camera Station over the internet. We apologize for the inconvenience this may cause.

  2. investigating May 05, 2025, 03:11 PM UTC

    Investigating - We are seeing intermittent performance issues in Secure Remote Access version 1 in the Americas. This will affect clients connecting remotely to AXIS Camera Station 5 and Pro using SRAv1. We apologize for the inconvenience this may cause and we are working on solving the issue. You may also use an alternate method for remote access: - Upgrade to AXIS Camera Station Pro 6.8 and enable Secure Remote Access version 2. This available at no cost for AXIS Camera Station 5 and Pro systems. More details can be found here: https://www.axis.com/support/secure-remote-access - The Axis Cloud Portal (https://acs.mysystems.axis.com) provides web client access to AXIS Camera Station Pro systems with version 6.0 and above. - Implement VPN access or similar networking solution for remote access.

  3. monitoring May 07, 2025, 08:04 AM UTC

    A solution is implemented and we are monitoring the services.

  4. investigating May 08, 2025, 05:42 PM UTC

    The implemented solutions did not reach expected results, investigating different solutions. We apologize for the inconvenience, we will update the status page when we have more information.

  5. monitoring May 08, 2025, 06:13 PM UTC

    An additional fix has been implemented and the solution is working as expected. We are monitoring the service and will update this status if there are any changes. We apologize for the inconvenience.

  6. resolved May 13, 2025, 08:03 AM UTC

    This incident has been resolved.