Aruba Networks incident

Multiple customers are reporting issues authenticating credentials on Orchestrator

Critical Resolved View vendor source →

Aruba Networks experienced a critical incident on May 22, 2025 affecting Orchestrator As a Service(Northern Virginia) and Orchestrator Service Provider(Northern Virginia) and 1 more component, lasting 1h 45m. The incident has been resolved; the full update timeline is below.

Started
May 22, 2025, 03:00 PM UTC
Resolved
May 22, 2025, 04:45 PM UTC
Duration
1h 45m
Detected by Pingoru
May 22, 2025, 03:00 PM UTC

Affected components

Orchestrator As a Service(Northern Virginia)Orchestrator Service Provider(Northern Virginia)Orchestrator Global Enterprise(Northern Virginia)Orchestrator As a Service(Frankfurt)Orchestrator Service Provider(Frankfurt)Orchestrator Global Enterprise(Frankfurt)Orchestrator As a Service(Ohio)Orchestrator Service Provider(Ohio)Orchestrator Global Enterprise(Ohio)Orchestrator As a Service(Mumbai)

Update timeline

  1. investigating May 22, 2025, 09:46 PM UTC

    We're currently investigating an issue that is preventing users from logging onto Cloud Orchestrator, as well as downloading software. We hope to resolve this issue quickly.

  2. identified May 22, 2025, 09:46 PM UTC

    We have identified the issue preventing users from logging into Cloud Orchestrator and downloading software and are working to resolve it.

  3. identified May 22, 2025, 09:46 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring May 22, 2025, 09:47 PM UTC

    We are currently monitoring the issue and hope to resolve it quickly.

  5. resolved May 22, 2025, 09:47 PM UTC

    The issue that was identified has now been fully resolved.