Upscope had 16 outages in the last 2 years totaling 3h 24m of downtime — averaging 0.7 incidents per month.
There were 16 Upscope outages since October 12, 2025 totaling 3h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some users might be experiencing degraded performance on some co-cobrowsing sessions as we make some adjustments following an infrastructure problem yesterday.
The issue has now been fixed. Please let our team know at [email protected] if you experience any further problems.
We are witnessing an elevated latency on the us-east region. A scaling fix is being implemented.
Co-browsing (California) went down
REST API went down
Integrations went down
LiveDocument went down
Co-Browsing API dashboard went down
HelloScreen went down
UserView went down
Upscope dashboard went down
Some active co-browsing sessions might have been interrupted for around 2 minutes and will require both sides to reload the page to be restarted.
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.
The issue has now been resolved.
Co-browsing (North Virginia) recovered
The search functionality is fully restored in all regions.
Search functionality is experiencing issues in our US - East region. We are investigating the issue.
The search functionality is fully restored in all regions.
We have now solved the issue. We are working to backfill statuses for other sessions.
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.
We have now solved the issue. We are working to backfill statuses for other sessions.
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.
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.