Live  /  Solace Cloud  /  Incident

Solace Cloud: Service Degradation in AWS ME-Central-1 (UAE) Region

Solace Cloud · solace.cloudMinor incidentidentified2026-03-04 01:25 UTC
Public — what happened

Summary

Solace Cloud reported a minor service degradation affecting its offerings in two Amazon Web Services regions in the Middle East: ME-South-1 in Bahrain and ME-Central-1 in the UAE. The company posted the issue at 01:25 UTC on March 4, 2026, and said it stemmed from a problem on the AWS side, pointing customers to Amazon's own status page for details. Solace Cloud asked affected customers to reach out to its support team for help. As of the latest update, the issue was listed as identified but not yet resolved.

Affected

AWS - ME-Central-1 (UAE)

As listed on Solace Cloud’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Solace Cloud against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Solace Cloud: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Solace Cloud report →

More from Solace Cloud

The full archive is on the Solace Cloud status & history page.

Related: Solace Cloud status & history. SquidGrid is not affiliated with Solace Cloud.