Live  /  Solace Cloud  /  Incident

Solace Cloud: Service Degradation in AWS ME-South-1 (Bahrain) Region

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

Summary

Solace Cloud reported reduced service performance affecting its offerings in two Amazon Web Services regions, Bahrain (ME-South-1) and the UAE (ME-Central-1), starting at 16:23 UTC on March 3, 2026. The company said the trouble stemmed from a problem on the AWS side and directed affected customers to its support team and to Amazon's own status page. In an update at 01:26 UTC on March 4, Solace Cloud said work on a fix was still underway, and the incident had not been marked resolved.

Affected

AWS - ME-South-1 (Bahrain), 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.