Temporary issue with co-browsing sessions
The issue has been fixed
Home
/
Status
/
Service
Real-time cobrowsing for seamless teamwork and enhanced customer support.
Source
auto
Category
Communication
Adapter
HUND STATUS
Verified
Pending review
Current state
Major Outage
Checked 6m ago
0
Components
14
Active incidents
0
Maintenance
0%
90d uptime
Temporary issue with co-browsing sessions
Jun 14, 10:14 PM
Normalized official status-page data for incidents, maintenance, components, and history.
0%
Known uptime
2 known history days
0
Components tracked
0 outage, 0 degraded
16
Incidents indexed
14 active right now
1
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
No component impact has been recorded yet.
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
0
operational days
0
degraded days
2
outage days
0
maintenance days
88
unknown days
Latest outages and degradations detected from the official status page.
The issue has been fixed
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 (California) went down
The issue has now been resolved.
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.
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
The issue has now been fixed. Please let our team know at team@upscope.com if you experience any further problems.
Some users might be experiencing degraded performance on some co-cobrowsing sessions as we make some adjustments following an infrastructure problem yesterday.
We are investigating an issue with a load balancer failing in the North Virginia region for some requests.
The search functionality is fully restored in all regions.
Scheduled and completed maintenance windows are separated from incidents.
Maintenance completed
Uptimus tracks the official Upscope status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.upscope.com
Adapter
HUND STATUS
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 0 to 0 of 0 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Components are pending verification for this status page. | |||
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Upscope is currently marked as Major Outage in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.