Identified
After a thorough investigation, we have identified the root cause of the problem affecting the CloudConnexa regions. We are working to deploy a solution as soon as possible.
Posted Jul 15, 2025 - 16:00 UTC
Investigating
We are investigating reports about issues in CloudConnexa Regions.
Posted Jul 12, 2025 - 13:06 UTC
This incident affects: CloudConnexa Regions (CloudConnexa - Region Ashburn, Virginia, USA, CloudConnexa - Region Atlanta, Georgia, USA, CloudConnexa - Region Boston, Massachusetts, USA, CloudConnexa - Region Chicago, Illinois, USA, CloudConnexa - Region Columbus, Ohio, USA, CloudConnexa - Region Dallas, Texas, USA, CloudConnexa - Region Kansas City, Missouri, USA, CloudConnexa - Region Los Angeles, California, USA, CloudConnexa - Region Miami, Florida, USA, CloudConnexa - Region Newark, New Jersey, USA, CloudConnexa - Region Portland, Oregon, USA, CloudConnexa - Region San Jose, California, USA, CloudConnexa - Region Montreal, Canada, CloudConnexa - Region Toronto, Canada, CloudConnexa - Region Vancouver, Canada, CloudConnexa - Region Brussels, Belgium, CloudConnexa - Region Heisinki, Finland, CloudConnexa - Region Paris, France, CloudConnexa - Region Frankfurt, Germany, CloudConnexa - Region Dublin, Ireland, CloudConnexa - Region Milan, Italy, CloudConnexa - Region Amsterdam, Netherlands, CloudConnexa - Region Warsaw, Poland, CloudConnexa - Region Madrid, Spain, CloudConnexa - Region Stockholm, Sweden, CloudConnexa - Region Zurich, Switzerland, CloudConnexa - Region London, United Kingdom, CloudConnexa - Region Johannesburg, South Africa, CloudConnexa - Region Mumbai, India, CloudConnexa - Region Tel Aviv, Israel, CloudConnexa - Region Tokyo, Japan, CloudConnexa - Region Singapore , Singapore, CloudConnexa - Region Sydney, Australia, CloudConnexa - Region São Paulo, Brazil).