Upscope Outage History

Upscope is up right now

Pingoru has recorded 9 incidents for Upscope: 3 in the last 12 months and 1 in the last 90 days.

Source: status.upscope.com

9incidents recorded
3last 12 months
1last 90 days
28 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking Upscope in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202611 of 720 (0%)
July 202600 of 744 (0%)
August 202610 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 479 (0%)

Upscope reliability, month by month

In the last 12 months, Upscope posted 3 incidents on its official status page. Since Pingoru began tracking it in April 2026, at least one incident was open less than 1% of the time. Half of the incidents with a known end in the last 12 months were over within 38 minutes; the longest, "Temporary issue with co-browsing sessions" on June 14, 2026, lasted 38 minutes. The components affected most often were UserView (2 incidents), Co-browsing (North Virginia) (1) and REST API (1).

  • November 2026 (so far): no incidents.
  • October 2026: no incidents.
  • September 2026: no incidents.
  • August 2026: 1 incident, an incident was open less than 1% of the time, the longest lasted 9 minutes.
  • July 2026: no incidents.
  • June 2026: 1 incident, an incident was open less than 1% of the time, the longest lasted 38 minutes.
  • May 2026: no incidents.
  • April 2026 (tracking began this month): no incidents.

Incidents, newest first

Minor August 31, 2026 Errors in cobrowsing North Virginia errors 9m Co-browsing (North Virginia)

Started Aug 31, 2026, 09:37 PM UTC· resolved Aug 31, 2026, 09:46 PM UTC

  1. investigating Aug 31, 2026, 09:37 PM UTC

    We are witnessing an elevated latency on the us-east region. A scaling fix is being implemented.

  2. resolved Aug 31, 2026, 09:46 PM UTC

    The issue with our cache has been fixed.

Read the full incident report →

Minor June 14, 2026 Temporary issue with co-browsing sessions 38m UserView, REST API

Started Jun 14, 2026, 09:36 PM UTC· resolved Jun 14, 2026, 10:14 PM UTC

  1. investigating Jun 14, 2026, 09:36 PM UTC

    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.

  2. resolved Jun 14, 2026, 10:14 PM UTC

    The issue has been fixed

Read the full incident report →

Minor March 20, 2026 Issues co-browsing for teams with active BAAs 38m UserView

Started Mar 20, 2026, 04:00 PM UTC· resolved Mar 20, 2026, 04:38 PM UTC

  1. investigating Mar 20, 2026, 04:00 PM UTC

    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.

  2. resolved Mar 20, 2026, 04:38 PM UTC

    The issue has now been resolved.

Read the full incident report →

Minor September 4, 2025 New monitoring system –

Started Sep 04, 2025, 07:53 PM UTC· resolved Sep 04, 2025, 07:53 PM UTC

  1. investigating Sep 04, 2025, 07:53 PM UTC

    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 [email protected]

  2. investigating Sep 04, 2025, 07:53 PM UTC

    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 [email protected]

Read the full incident report →