Is Alkira down?

Last checked 9m ago
Current status
Alkira has degraded performance

Active incident: Issues with AWS services in the ME-CENTRAL-1 Region

Official status page: https://status.alkira.com · Polled every 5 minutes · 77 components tracked

Alkira is reporting degraded performance right now (last checked 9m ago). Services are up but slower or partially failing.

Real-time Alkira status, recent outages, and incident history — pulled directly from Alkira's official status page at https://status.alkira.com every 5 minutes. Pingoru tracks 77 Alkira services and has captured 6 incidents in the last 90 days (99.90% uptime). Get email, Slack, Discord, or webhook alerts the moment Alkira reports a new incident — free for 5 monitors, no credit card.

Users who monitor Alkira also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Alkira uptime 99.90% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incident 1

  1. Ongoing ● 104d 4h
    Started Mar 01, 2026, 02:23 PM UTC
    ME-CENTRAL-1 (UAE)ME-SOUTH-1 (Bahrain)
    Timeline · 7 updates
    • investigating · Mar 01, 2026, 02:23 PM UTC

      AWS is investigating issues with AWS services in the ME-CENTRAL-1 Region. Issue is related to connectivity and power affecting APIs and instances in a single Availability Zone (mec1-az2) in the ME-CENTRAL-1 Region due to a localized power issue. Issue started at Mar 01 4:51 AM PST. For more details: https://health.aws.amazon.com/health/status

    • investigating · Mar 01, 2026, 02:24 PM UTC

      We are continuing to investigate this issue.

    • identified · Mar 01, 2026, 03:05 PM UTC

      Update from AWS: A localized power outage is impacting one Availability Zone (mec1-az2) in the ME-CENTRAL-1 region. As a result, EC2 instances, databases, EBS volumes, and other resources in that zone are unavailable or experiencing connectivity issues. Some AWS services are also seeing increased errors and latency. For more details: https://health.aws.amazon.com/health/status

    • identified · Mar 01, 2026, 08:25 PM UTC

      AWS continues to work on restoring services. For more details: https://health.aws.amazon.com/health/status

    • identified · Mar 02, 2026, 05:06 PM UTC

      AWS continues to work on restoring services. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status

    • identified · Mar 02, 2026, 05:11 PM UTC

      AWS started seeing increased API error rates in ME-SOUTH-1 Region from Mar 01 9:56 PM PST. Current issues are affecting both ME-SOUTH-1 and ME-CENTRAL-1. Recovery is expected to take at least a day due to required facility, power, and safety assessments. For more details: https://health.aws.amazon.com/health/status

    • identified · Mar 24, 2026, 02:01 AM UTC

      We started noticing issue with services from AWS ME-SOUTH-1 for AZ0 at 13:07:27 UTC. AZ1 had been out of service from Mar 01. While we work with AWS on status, AWS has strongly recommend that customers with workloads running in the Middle East take action now to migrate those workloads to alternate AWS Regions. For more details: https://health.aws.amazon.com/health/status

    Latest: We started noticing issue with services from AWS ME-SOUTH-1 for AZ0 at 13:07:27 UTC. AZ1 had been out of service from Mar 01. While we work with AWS on status, AWS has strongly rec…

Recent outages & incidents

Past 90 days
  1. Resolved 16h 55m
    Started May 29, 2026, 06:02 AM UTC · Resolved May 29, 2026, 10:57 PM UTC
    USWEST-AZURE-2 (Washington)
    Timeline · 3 updates
    • identified · May 29, 2026, 06:02 AM UTC

      Starting at 04:16 UTC on 29 May 2026, a subset of customers using Azure services (including Virtual Machines) in West US 2 region may be experiencing connectivity issues. Azure has reported that a network device it manages has experienced a fault, resulting in the loss of network connectivity to some downstream resources. The unhealthy network device is being isolated from the network by Azure, and traffic is being rerouted to healthy infrastructure. Alkira's services are not impacted during this time due to active redundancy.

    • monitoring · May 29, 2026, 08:02 AM UTC

      The issue seems to be resolved. We are awaiting updates from Azure.

    • resolved · May 29, 2026, 10:57 PM UTC

      This incident is resolved.

    Latest: This incident is resolved.

  2. Resolved 3h 54m
    Started May 13, 2026, 09:45 AM UTC · Resolved May 13, 2026, 01:39 PM UTC
    Management Portal
    Timeline · 3 updates
    • investigating · May 13, 2026, 09:45 AM UTC

      We are currently investigating an issue with the portal being inaccessible.

    • monitoring · May 13, 2026, 10:01 AM UTC

      The management portal is now accessible. We are monitoring it.

    • resolved · May 13, 2026, 01:39 PM UTC

      Access to the management portal remains fully operational. Our internal investigation confirmed that all system components are healthy, and the issue was resolved automatically without intervention. We suspect a transient network or provider-level disruption and will continue to monitor performance closely. No customer traffic was impacted during this issue.

    Latest: Access to the management portal remains fully operational. Our internal investigation confirmed that all system components are healthy, and the issue was resolved automatically wit…

  3. Resolved 2h 38m
    Started Apr 23, 2026, 10:59 AM UTC · Resolved Apr 23, 2026, 01:38 PM UTC
    USWEST-AZURE-3 (Arizona)
    Timeline · 2 updates
    • monitoring · Apr 23, 2026, 10:59 AM UTC

      Starting at 09:37 UTC on 23 April 2026, a subset of customers using Azure services (including Virtual Machines) in West US 3 may experience connectivity issues and intermittent failures, which could affect the availability and operation of resources hosted in the region. Alkira services were not impacted during this time due to active redundancy.

    • resolved · Apr 23, 2026, 01:38 PM UTC

      Azure has resolved the issue. No Alkira services were impacted due to active redundancy built into the design. Details as provided by Azure - Between 09:37 UTC and 10:39 UTC on 23 April 2026, a network-related issue affected a subset of Azure workloads whose traffic traverses the West US 3 region. Impacted customers may have experienced connectivity issues and intermittent failures, which affected the availability and operation of resources in the region. The impact was limited to customers whose resources relied on the affected regional infrastructure.

    Latest: Azure has resolved the issue. No Alkira services were impacted due to active redundancy built into the design. Details as provided by Azure - Between 09:37 UTC and 10:39 UTC on 23 …

  4. Resolved
    Started Apr 23, 2026, 10:52 AM UTC · Resolved Apr 23, 2026, 09:32 AM UTC
    Timeline · 1 update
    • resolved · Apr 23, 2026, 10:52 AM UTC

      We observed degraded performance in UAENORTH-AZURE-1 CXP. Between 09:32 UTC on 23 Apr 2026 and 10:31 UTC on 23 Apr 2026, Virtual Machines in the UAE North region experienced connectivity issues. Alkira services were not impacted during this time. Updates from Service Provider: AZURE https://azure.status.microsoft/en-us/status

    Latest: We observed degraded performance in UAENORTH-AZURE-1 CXP. Between 09:32 UTC on 23 Apr 2026 and 10:31 UTC on 23 Apr 2026, Virtual Machines in the UAE North region experienced connec…

See the full Alkira outage history

1 more incident in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Alkira outage history →

Or sign up free to get alerts when Alkira breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 4 incidents View full outage history →