Chat messages and invites delayed
Timeline · 1 update
- resolved Jul 20, 2026, 05:03 PM UTC
From 11:36 AM to 12:35 PM ET chat messages and invites were delayed.
Roam had 7 outages in the last 2 years totaling 231h 54m of downtime — averaging 0.3 incidents per month.
There were 7 Roam outages since August 12, 2025 totaling 231h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.
From 11:36 AM to 12:35 PM ET chat messages and invites were delayed.
We are currently investigating an issue where Roam lobby pages are slow to load and sometimes showing errors. This is also impacting the ability to configure lobbies in the Roam application.
We have mitigated the issue and are actively monitoring.
This incident has been resolved.
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.
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.
All traffic has been moved to other regions.
We are investigating an issue where some users may be unable to resolve our domain.
We have confirmed with our third-party cloud provider that they are investigating a possible issue on their end.
AWS, our third party cloud provider, has confirmed that a global issue affecting CloudFront is causing our service interruption.
AWS is seeing early signs of recovery, and we are seeing a decrease in the number of affected users.
We have observed significant recovery, but some users may continue to experience issues as caches clear. Users who continue to experience issues should restart their apps.
This incident has been resolved.
An issue has been identified with Roam's lobby functionality, and we are working on a fix.
We are continuing to work on a fix for this issue.
A fix has been implemented, and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified the root cause to issues with sending in Roam's chat system and are deploying a fix.
This incident has been resolved.
Some customers that use Telecom Argentina S.A. are having trouble joining Roam meetings. We are currently working on a mitigation.
We have applied a mitigation. Once Argentina-based users restart their Roam application, this issue should be resolved. We identified that some other Argentina-based users may have been affected by this issue.