Aruba Networks Outage History

Aruba Networks is up right now

Pingoru has recorded 15 incidents for Aruba Networks: 1 in the last 12 months and 0 in the last 90 days.

Source: status.silverpeak.cloud

15incidents recorded
1last 12 months
0last 90 days
63 daystypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Aruba Networks in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Major March 2, 2026 Selective Cloud Orchestrators are affected on ME-Central-1 (UAE) 63d 6h Orchestrator As a Service(UAE)

Started Mar 02, 2026, 02:26 PM UTC· resolved May 04, 2026, 08:48 PM UTC

  1. investigating Mar 02, 2026, 07:40 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 02, 2026, 07:45 AM UTC

    We are following with the current situation with ME-Central-1. The last few updates from AWS are as below - https://health.aws.amazon.com/health/status?path=open-issues Increased Error Rates Mar 01 10:46 PM PST We can confirm that a localized power issue has affected another Availability Zone in the ME-CENTRAL-1 Region (mec1-az3). Customers are also experiencing increased EC2 APIs and instance launch errors for the remaining zone (mec1-az1). At this point it is not possible to launch new instances in the region, although existing instances should not be affected in mec1-az1. Other AWS Services, such as DynamoDB and S3 are also experiencing significant error rates and latencies. We are actively working to restore power and connectivity, at which time we will begin to work to recover affected resources. As of this time, we expect recovery is multiple hours away. For customers that can, we recommend failing away to another AWS Region at this time. We will provide an update by 12:00 AM PST, or sooner if we have additional information to share. Mar 01 9:59 PM PST We are investigating additional connectivity issues and error rates in the ME-CENTRAL-1 Region.

  3. investigating Mar 02, 2026, 11:23 AM UTC

    Mar 02 2:53 AM PST We wanted to provide more information on Amazon S3 given that there are two impaired Availability Zones (mec1-az2 and mec1-az3) in the ME-CENTRAL-1 Region. Amazon S3 is a regional service and designed to withstand the total loss of a single Availability Zone while maintaining S3's durability and availability. When the mec1-az2 AZ was powered off at approximately 4:00 AM PST on Sunday, March 1, S3 continued to operate normally. As the second AZ became impaired, S3 error rates increased. With two Availability Zones significantly impacted, customers are seeing high failure rates for data ingest and egress. We strongly advise customers to update their applications to ingest S3 data to an alternate AWS Region. As soon as practically possible, we will begin the restoration of our two Availability Zones which will include a careful assessment of data health and any repair of storage if necessary. In addition, we can confirm that the AWS Management Console and command line interface (CLI) are disrupted by the failure of two Availability Zones. We continue to work towards recovery across all services, and we will provide an update by 6:00 AM PST on March 2, or sooner if we have additional information to share. Mar 02 12:52 AM PST We continue to work on a localized power issue affecting multiple Availability Zones in the ME-CENTRAL-1 Region (mec1-az2 and mec1-az3). Customers are experiencing increased EC2 API errors and instance launch failures across the region, and it is not currently possible to launch new instances; existing instances in mec1-az1 should not be affected. Amazon DynamoDB and Amazon S3 are also experiencing significant error rates and elevated latencies. We are actively working to restore power and connectivity, after which we will begin recovery of affected resources; full recovery is still expected to be many hours away. We recommend that affected customers failover, and backup any critical data, to another AWS Region. We will provide an update by 2:00 AM PST, or sooner if the situation changes.

  4. investigating Mar 02, 2026, 02:26 PM UTC

    AWS is expecting to address the issue in another day as per their communication at Mar 02 6:22 AM PST

  5. investigating Mar 05, 2026, 10:25 AM UTC

    Monitoring AWS ME-Central-1 region incident. Waiting for AWS resolution. Services may be impacted. Updates to follow.

Read the full incident report →

Major October 20, 2025 Major AWS Outage causing disruption to multiple Cloud Services 17h 56m Orchestrator As a Service(Northern Virginia), Orchestrator Service Provider(Northern Virginia), Orchestrator Global Enterprise(Northern Virginia)

Started Oct 20, 2025, 10:08 AM UTC· resolved Oct 21, 2025, 04:05 AM UTC

  1. monitoring Oct 20, 2025, 10:08 AM UTC

    https://health.aws.amazon.com shows major AWS DNS outage affecting multiple services like login, MFA. HPE Networking team is monitoring the situation and will update the status once services are back to normal.

  2. monitoring Oct 20, 2025, 09:29 PM UTC

    We are continuing to monitor for any further issues.

  3. monitoring Oct 20, 2025, 09:36 PM UTC

    We've started seeing continued product experience improvement.

  4. resolved Oct 21, 2025, 04:05 AM UTC

    The incident has been resolved and all services are back to normal

Read the full incident report →

Major September 26, 2025 Multiple customers are reporting issues authenticating credentials on Orchestrator 13h 33m Orchestrator As a Service(Northern Virginia), Orchestrator Service Provider(Northern Virginia), Orchestrator Global Enterprise(Northern Virginia), Orchestrator As a Service(Frankfurt) and 11 more

Started Sep 26, 2025, 10:00 AM UTC· resolved Sep 26, 2025, 11:34 PM UTC

  1. investigating Sep 26, 2025, 06:31 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 Sep 26, 2025, 06:31 PM UTC

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

  3. monitoring Sep 26, 2025, 06:32 PM UTC

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

  4. resolved Sep 26, 2025, 11:34 PM UTC

    The issue that was identified has now been fully resolved.

Read the full incident report →