## System Status Page for ScreenMeet.com ### Partial Beam Service Disruption **July 21, 2026 3:04PM EDT** **Investigating** - We have identified an issue with our Beam product. This is for customers that are launching Beam from the ScreenMeet console and is not affecting our ServiceNow experience. We are investigating the issue. **July 21, 2026 3:37PM EDT** **Identified** - We have determined the cause of the disruption and are developing a resolution now. We expect this to be done by approximately 7:00 PM Eastern. **July 21, 2026 7:18PM EDT** **Resolved** - The Beam issue has been resolved. Thank you for your patience as we worked this through to resolution. ### ScreenMeet Beam Service Disruption **July 15, 2026 8:47AM EDT** **Investigating** - We are aware of an issue impacting Beam device connectivity and are investigating. Some sessions may fail to connect or reconnect. Next update within 30 minutes. **July 15, 2026 9:09AM EDT** **Identified** - Our team has identified what appears to be the root cause of the service degradation. Our engineering leadership is currently remediating the degradation. The next update will be provided in 30 minutes or less. **July 15, 2026 9:31AM EDT** **Monitoring** - The Beam service is recovering now and devices are coming back online. **July 15, 2026 10:11AM EDT** **Monitoring** - Beam has recovered. We'll continue to monitor throughout the day. We are also actively investigating the root cause. **July 15, 2026 12:51PM EDT** **Resolved** - Our team has resolved a Beam service disruption that prevented devices from loading in the console and CRM Beam Groups pages, blocking device connections. Beam behavior recovered as of 7/15 9:20 AM ET, with full stability confirmed by 10:00 AM ET. ### MyHelpScreen.com Issue **April 21, 2026 12:02AM EDT** **Identified** - We have isolated the issue and are currently deploying a resolution. It should be resolved within 30 minutes. We apologize for the inconvenience. **April 21, 2026 12:13AM EDT** **Resolved** - Issue is resolved. Thank you for your patience as we resolved the issue. ### ScreenMeet Beam Maintenance, March 24, 2026 **March 23, 2026 5:02PM EDT** **Scheduled** - Scheduled Maintenance for ScreenMeet Beam Date: Tuesday, March 24, 2026, 8:00 PM Eastern Time Duration: Up to 60 minutes Impact: Agents will be unable to start ScreenMeet sessions via Beam during the maintenance window. ScreenMeet will be performing a one time maintenance exercise of the Beam services. During this time, sessions that are already started will continue. However, agents will be unable to start new sessions and the Beam counts will go to zero. Once the maintenance is complete, the Beam counts will gradually reset and agents can start Beam sessions. The maintenance will take less than one hour to complete. **March 24, 2026 7:59PM EDT** **Active** - The scheduled Beam maintenance is underway. **March 24, 2026 8:13PM EDT** **Completed** - The schedule maintenance is complete and Beam is now available. ### ScreenMeet Beam Service Disruption **February 10, 2026 12:36PM EST** **Investigating** - Currently the Device Count for Beam is showing zero and sessions are unable to be started. We are investigating now. **February 10, 2026 12:47PM EST** **Monitoring** - The underlying issue has been resolved and we are moving towards full service availability now. **February 10, 2026 12:59PM EST** **Monitoring** - Beam sessions can now be started. Device count is still in recovery mode. **February 10, 2026 1:17PM EST** **Resolved** - Beam is now fully functional. ### ScreenMeet Documentation Page Unavailable Due to Cloudflare Outage **November 18, 2025 9:41AM EST** **Monitoring** - Due to the Cloudflare outage today, the ScreenMeet documentation is temporarily unavailable. We do not yet have an ETA on resolution, but will post when known. **November 18, 2025 10:00AM EST** **Resolved** - The ScreenMeet documentation pages are now back online and accessible. ### ScreenMeet Live Video on New Chrome Version **September 4, 2025 3:47PM EDT** **Identified** - We’ve identified an issue where video feeds may not render for ScreenMeet Live participants using Chrome version 140.0.7339.81. The issue is limited to this Chrome version, and participants can use another browser as an interim solution while our engineering team investigates a permanent fix. **September 4, 2025 4:01PM EDT** **Identified** - Our engineering team has found the root cause of the issue and has built a resolution that is now proceeding through testing. The updates should make their way to production later today. **September 4, 2025 6:34PM EDT** **Resolved** - The issue was resolved with an update that supports the new version of Chrome. ### ScreenMeet Console Data Exports for Admins Currently Unavailable **April 9, 2025 5:32PM EDT** **Identified** - We have discovered an issue with our data exports (available to ScreenMeet admins via the ScreenMeet console). We have identified the cause and working on a solution. We hope to reenable service soon. **April 10, 2025 11:59AM EDT** **Resolved** - We have reenabled the data export utility. ### ScreenMeet Live Screen Sharing Performance Issue Detected **February 12, 2025 11:54AM EST** **Monitoring** - Our team identified a performance issue with the screen sharing functionality of ScreenMeet Live on a specific cloud server. The engineering team has deployed a fix, and the issue should no longer occur. We are continuing to monitor the situation to ensure stability. **February 12, 2025 12:42PM EST** **Resolved** - The performance issue with the screen sharing functionality of ScreenMeet Live has been resolved following adjustments to our server infrastructure. The issue should no longer occur, and we will continue to monitor the situation to ensure ongoing stability. Additionally, we are implementing further improvements to enhance performance and prevent similar issues in the future. ### ScreenMeet Beam Degradation – Limited Device Loading Issue Identified **December 6, 2024 10:54AM EST** **Identified** - We’ve identified an issue that limits Beam groups to loading only a single page of devices. As a temporary workaround, agents can search for a device by its name, provided it is online and connected to the internet, to establish a connection. This primarily affects the ability to navigate and view multiple pages of Beam devices. Our team is actively working on a permanent resolution and will share updates promptly. **December 6, 2024 1:00PM EST** **Monitoring** - Our team has deployed a hotfix to remediate the issue. The issue encountered should no longer persist. We will close out this incident once we have verified that customers impacted are no longer encountering the issue. **December 6, 2024 2:39PM EST** **Resolved** - The issue has been resolved.