Incidents reported on status page for Upscope https://status.upscope.com/ https://d1lppblt9t2x15.cloudfront.net/logos/0260bdf6a8af876a57865d4f03e3d31e.svg https://status.upscope.com/ en https://status.upscope.com/ Thu, 21 May 2026 16:04:50 +0000 https://status.upscope.com/#4043bdaae971483ea4af28da58eed12a2ad69e529b9d9ebeb01fef323d41d066 Co-browsing (California) recovered https://status.upscope.com/ Thu, 21 May 2026 15:56:58 +0000 https://status.upscope.com/#4043bdaae971483ea4af28da58eed12a2ad69e529b9d9ebeb01fef323d41d066 Co-browsing (California) went down https://status.upscope.com/incident/853734 Fri, 20 Mar 2026 16:38:00 -0000 https://status.upscope.com/incident/853734#86d54bebf3132d2c9a57d84d9650ea6c410cfa5bf9515c2ad94b01b8f048baca The issue has now been resolved. https://status.upscope.com/incident/853734 Fri, 20 Mar 2026 16:00:00 -0000 https://status.upscope.com/incident/853734#fe6aaf7ecd078f0ada4aff7a6fd8a463d8211efa3de07e691f3e912c209ed4f5 Co-Browsing sessions have problems starting for some teams that have HIPAA protected data and an active BAA with Upscope. We have identified the issue and a fix will be online in the next 15 minutes. https://status.upscope.com/incident/718547 Thu, 04 Sep 2025 19:53:00 -0000 https://status.upscope.com/incident/718547#45f45059b92e374cbbd4c024ae315316a38c5ed09411cb06f7cbff27a24420bc A quick note to let you know we’re transitioning to new monitoring endpoints for our status page. This change will reduce noise from false incidents and provide a more accurate picture of our service status. Previously: - We reported downtime for any canary issues across most services, including when canary servers went down. This happened fairly often due to limited scaling, Kubernetes pod swaps, or during deploys. (Canary servers only handle a tiny fraction of traffic to validate new versions before rollout, ensuring we can safely roll back if needed). - We also reported downtime when servers in co-browsing regions were overwhelmed with connections. This sometimes occurred at peak times (e.g. 9 a.m. in certain time zones if pre-scaling predictions were off). In reality, co-browsing wasn’t affected: only low-priority connections were rate-limited, search performance slightly degraded, or background jobs like recordings slowed down. Now: - Canary monitoring will only trigger internal alerts. You’ll only see downtime reported if it actually affects usage. - Overload monitoring is now handled exclusively by our DevOps team, since it does not impact client usage. We hope these updates make the status page more meaningful by cutting unnecessary noise and focusing only on issues that impact you. If you’d like to discuss these changes, feel free to reach out at team@upscope.com https://status.upscope.com/incident/435770 Fri, 27 Sep 2024 13:51:00 -0000 https://status.upscope.com/incident/435770#f77add83e28fb80076a18de97bdbe97a217f2bde3a4fa40ae222fdb4a864b7e6 The issue has now been fixed. Please let our team know at team@upscope.com if you experience any further problems. https://status.upscope.com/incident/435770 Fri, 27 Sep 2024 13:30:00 -0000 https://status.upscope.com/incident/435770#8e701ad076b4175a176034c1906e18ee029fb5d4790ab0650a1b3edf1667b06a Some users might be experiencing degraded performance on some co-cobrowsing sessions as we make some adjustments following an infrastructure problem yesterday. https://status.upscope.com/incident/435238 Thu, 26 Sep 2024 15:20:00 -0000 https://status.upscope.com/incident/435238#80e02020efbc67cbfa50584b4c3911180dc8d00ea07a9e54e8ac10f20b071987 We are investigating an issue with a load balancer failing in the North Virginia region for some requests. https://status.upscope.com/incident/323719 Wed, 07 Feb 2024 22:16:00 -0000 https://status.upscope.com/incident/323719#916ad07e610461f9d3bdee29e2a9630a67a3c937ad30c81c864129cd9f9619e8 The search functionality is fully restored in all regions. https://status.upscope.com/incident/323719 Wed, 07 Feb 2024 20:56:00 -0000 https://status.upscope.com/incident/323719#f318c6f0ca129951fbf85029cce352533e8f3d13c4be0571797a5f76f0171ffc Search functionality is experiencing issues in our US - East region. We are investigating the issue. https://status.upscope.com/incident/223194 Thu, 22 Jun 2023 02:00:00 -0000 https://status.upscope.com/incident/223194#e09cc618903bb017299738d32ee0024363dededeb49d5faeec0185c27aad1fdb Maintenance completed https://status.upscope.com/incident/223194 Thu, 22 Jun 2023 00:00:00 -0000 https://status.upscope.com/incident/223194#ca49e7e76a020b089c7429320682c0aec1ae00623a765cd9231800c8fb4d5460 We are undergoing a major migration of our main authentication system, which will split the main application into different products. We expect no more than 5 minutes of downtime. https://status.upscope.com/incident/129646 Tue, 25 Oct 2022 18:25:00 -0000 https://status.upscope.com/incident/129646#2f5bf57531830e1d4eaec1649ad721e6afe51e4e7597a33a7b66f94618e27f4c We have now solved the issue. We are working to backfill statuses for other sessions. https://status.upscope.com/incident/129646 Tue, 25 Oct 2022 18:07:00 -0000 https://status.upscope.com/incident/129646#d3dabaf3ddc4a580d3df4b5cd21316cfe59153d1502b10ca9dc8a6e297f9564e Some Sessions will look unauthorized or failed on the dashboard and REST API due to an issue. We are currently working on a fix. Sessions are unaffected and keep working as normal. https://status.upscope.com/incident/125908 Wed, 12 Oct 2022 16:00:00 -0000 https://status.upscope.com/incident/125908#9b28034e51e7eafaf73af75942574457c54b50a190ad7d7c08d9909f48627858 Some of our customers reported seeing errors with the rendering of some pages. This was due to an update to support more encoding types, which caused an issue with some minified CSS. We have now solved this issue.