Roam incident
AWS incident in me-central-1 impacting some customers
Affected components
Update timeline
- investigating Mar 10, 2026, 04:31 PM UTC
We are currently tracking an issue some customers are having connecting to Roam meetings. AWS's issue with one of their availability zones is causing intermittent problems with many services. https://health.aws.amazon.com/health/status?path=open-issues Roam customers that are geographically close or have connections that route through that region may be impacted. We are in the process of removing this region from our active configuration, and will complete that process by 10 PM Eastern US time 2026-03-10.
- monitoring Mar 11, 2026, 06:06 PM UTC
We are unable to modify our servers in the me-central-1 region due to the AWS outage so we can't implement a server side fix. A client fix has been made, it is in version 204.0.1. The client caches data for up to 30 minutes, after updating if you are still having problems after 30 minutes please restart your client and it should be resolved.
- resolved Mar 19, 2026, 07:03 PM UTC
All traffic has been moved to other regions.
Looking to track Roam downtime and outages?
Pingoru polls Roam's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Roam reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Roam alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required