Is Periscope down?
Last checked 4m agoNo incidents right now.
Periscope is operational right now. Last checked 4m ago; the most recent incident resolved 12d ago.
Real-time Periscope status, recent outages, and incident history — pulled directly from Periscope's official status page at https://status.periscopedata.com every 5 minutes. Pingoru tracks 3 Periscope services and has captured 5 incidents in the last 90 days (98.33% uptime). Get email, Slack, Discord, or webhook alerts the moment Periscope reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Sisense Managed Service
Timeline · 4 updates
- investigating · Jun 01, 2026, 02:30 PM UTC
Unfortunately, an ongoing incident with an upstream provider (Red Hat / Quay.io) has degraded again, affecting container registry push/pull operations (https://status.redhat.com/incidents/jn6r256zc62c). As a precaution, customers may experience intermittent slowness or delays with some Sisense services that depend on this provider. We are actively monitoring the situation and assessing any potential impact to our platform.
- monitoring · Jun 01, 2026, 04:44 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring · Jun 01, 2026, 05:01 PM UTC
We are continuing to monitor for any further issues.
- resolved · Jun 01, 2026, 09:06 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Sisense Managed Service
Timeline · 3 updates
- investigating · Jun 01, 2026, 10:16 AM UTC
We are aware of an ongoing incident with an upstream provider (Red Hat / Quay.io) that is reporting degraded performance on container registry push/pull operations https://status.redhat.com/incidents/jn6r256zc62c. As a precaution, customers may experience intermittent slowness or delays with some Sisense services that depend on this provider. We are actively monitoring the situation and assessing any potential impact to our platform.
- monitoring · Jun 01, 2026, 10:26 AM UTC
RedHat have restored manifest pushes and are monitoring the environment for stability.
- resolved · Jun 01, 2026, 10:54 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Sisense for Cloud Data TeamsSisense Managed Service
Timeline · 4 updates
- investigating · May 13, 2026, 10:42 AM UTC
Please be aware that on May 11, starting at 10:30 AM EEST, we experienced a service outage affecting the AI Assistant. During this window, users across all accounts may have experienced non-responsive behavior when attempting to create charts or submit general queries to the Assistant.
- identified · May 13, 2026, 10:44 AM UTC
Following a technical investigation, the issue was traced back to the Shared Gateway Service, which was preventing requests from reaching the AI processing engine.
- monitoring · May 13, 2026, 10:46 AM UTC
Our engineering team applied mitigation steps and re-applied configuration to clear the gateway bottleneck and restore the flow of traffic.
- resolved · May 13, 2026, 10:47 AM UTC
2:00 PM EEST The fix was verified, and the service was confirmed as fully operational. Root Cause: The outage was corrupted configuration in the AI Shared Gateway Service, affecting its ability to handle Assistant-specific traffic. We sincerely apologize for the impact this had on your workflow. We are currently reviewing our gateway capacity and alerting thresholds to prevent a recurrence of this specific issue.
Latest: 2:00 PM EEST The fix was verified, and the service was confirmed as fully operational. Root Cause: The outage was corrupted configuration in the AI Shared Gateway Service, affectin…
-
- Sisense Managed Service
Timeline · 5 updates
- investigating · May 08, 2026, 01:11 AM UTC
Please be aware that AWS (Amazon Web Services) is currently reporting significant hardware and power issues in the US-EAST-1 (N. Virginia) region. For the most up-to-date information on their infrastructure recovery, please follow the official AWS Health Dashboard https://health.aws.amazon.com/health/status . Unfortunately, our Sisense servers are also severely impacted by this event. As a result, users may experience total loss of access, dashboard loading failures, or significant latency. Our engineering team is actively monitoring the AWS recovery process and is working to restore Sisense services as quickly as hardware availability allows. We apologize for this disruption and will provide further updates here as soon as we have more information.
- identified · May 08, 2026, 01:21 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring · May 08, 2026, 01:22 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring · May 08, 2026, 11:40 AM UTC
We have observed a stabilization in our system metrics, and Sisense services have returned to normal operation. This coincides with progress made by AWS in restoring cooling and power to the affected infrastructure in the US-EAST-1 region. While our services are currently performing as expected, we are keeping this incident in Monitoring status as AWS continues their final recovery efforts. We will continue to verify data integrity and performance throughout the day. For the latest on the underlying AWS infrastructure, please refer to: https://health.aws.amazon.com/health/status
- resolved · May 09, 2026, 09:40 AM UTC
AWS has officially resolved the thermal and power event in the US-EAST-1 region. All underlying infrastructure supporting our Sisense servers has been stabilized and is performing at pre-event levels. Our engineering team has verified that our services are fully operational. We will continue to perform routine checks to ensure long-term stability, but we consider this incident fully resolved. Thank you for your patience while we navigated this external disruption. https://health.aws.amazon.com/health/status
Latest: AWS has officially resolved the thermal and power event in the US-EAST-1 region. All underlying infrastructure supporting our Sisense servers has been stabilized and is performing …
-
- Sisense Managed Service
Timeline · 4 updates
- investigating · Mar 21, 2026, 12:49 AM UTC
We’re currently observing a partial outage affecting Sisense managed instances. Our team is actively investigating the issue and working to identify the root cause. We’ll share updates as soon as we have more information. Thank you for your patience.
- identified · Mar 21, 2026, 02:45 AM UTC
The issue has been identified and we are actively working on a fix.
- monitoring · Mar 21, 2026, 03:02 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Mar 21, 2026, 03:26 AM UTC
The incident has been resolved.
Latest: The incident has been resolved.
-
- Started Jun 01, 2026, 02:30 PM UTC · Resolved Jun 01, 2026, 09:06 PM UTC · 6h 35m
- Started Jun 01, 2026, 10:16 AM UTC · Resolved Jun 01, 2026, 10:54 AM UTC · 37m
- Started May 13, 2026, 10:42 AM UTC · Resolved May 13, 2026, 10:47 AM UTC · 5m
- Started May 08, 2026, 01:11 AM UTC · Resolved May 09, 2026, 09:40 AM UTC · 1d 8h
- Started Mar 21, 2026, 12:49 AM UTC · Resolved Mar 21, 2026, 03:26 AM UTC · 2h 36m