CloudAMQP Status

Monitoring: We are still experiencing issues with this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.

Monitoring: AWS has an ongoing issue with multiple services in region me-south-1. Shared server hummingbird-01 affected.

Resolved: The Management UI SSO shortcut is back to service.

Impacted Clusters: All customers with clusters created more than 6 months ago

Cause: Some code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up.

Impact: Only the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API. Logging into the Management UI via Credentials and all Authentications Backends was functioning normally.

Identified: We are continuing to work on a fix for this issue.

Identified: The Management UI and brokers are serving traffic normally. You can still use the Management UI by using the Broker URL and properly typing User and Password.

The impact is related to our backend service logs into Management UI via CloudAMQP SSO.

Identified: Customers are experiencing Management UI being unavailable with 502 Bad Gateway.

Timeline:

• 14:16 UTC -> The issue was identified
• 14:30 UTC -> Recent code changes were reverted. No relationship with incident noted.

Monitoring: We are still experiencing issues with all AZ's in this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.

Monitoring: We are continuing to monitor. The outage is in regards to the AZ mec1-az2

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: AWS has an ongoing issue with multiple services in region me-central-1.

Monitoring: We are still experiencing issues with this region. If your services are impacted, we recommend you create a new cluster in a different region. When creating, use the copy config option, but do not copy plugin settings as this requires the source cluster to be running. Instead, enable once cluster is configured.

Monitoring: AWS has an ongoing issue with multiple services in region me-south-1. Shared server hummingbird-01 affected.

Resolved: The Management UI SSO shortcut is back to service.

Impacted Clusters: All customers with clusters created more than 6 months ago

Cause: Some code changes unexpectedly changed the communication schema between our backend services and the SSO component on the clusters. The proxy configuration conflicted with those changes causing the 502 Bad Gateway error to show up.

Impact: Only the SSO via CloudAMQP Console was impacted given it required communication with our backend components. The AMQP Clusters were healthy and servicing traffic via both AMQP and HTTP on Management UI and API. Logging into the Management UI via Credentials and all Authentications Backends was functioning normally.

Identified: We are continuing to work on a fix for this issue.

Identified: The Management UI and brokers are serving traffic normally. You can still use the Management UI by using the Broker URL and properly typing User and Password.

The impact is related to our backend service logs into Management UI via CloudAMQP SSO.

Identified: Customers are experiencing Management UI being unavailable with 502 Bad Gateway.

Timeline:

• 14:16 UTC -> The issue was identified
• 14:30 UTC -> Recent code changes were reverted. No relationship with incident noted.