Aruba Networks incident

Multiple customers are reporting issues authenticating credentials on Orchestrator

Major Resolved View vendor source →

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

Started
Mar 16, 2025, 01:00 AM UTC
Resolved
Mar 16, 2025, 08:00 AM UTC
Duration
6h 59m
Detected by Pingoru
Mar 16, 2025, 01:00 AM 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 Mar 17, 2025, 02:17 AM 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 Mar 17, 2025, 02:18 AM UTC

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

  3. monitoring Mar 17, 2025, 02:18 AM UTC

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

  4. resolved Mar 17, 2025, 02:19 AM UTC

    The issue that was identified has now been fully resolved.