SalesScreen Outage History
SalesScreen is up right nowPingoru has recorded 36 incidents for SalesScreen: 3 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 2 of 720 (0%) |
| May 2026 | 1 | 116 of 744 (16%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 548 (0%) |
Incidents, newest first
Notice May 7, 2026 Action Required: Salesforce Integration Security Update 4d 19h API
Started May 07, 2026, 12:25 PM UTC· resolved May 12, 2026, 08:15 AM UTC
- monitoring May 07, 2026, 12:25 PM UTC
To comply with updated Salesforce security requirements, some users are required to re-authenticate their connection. Please visit your Settings -> Integrations and re-link your Salesforce account to ensure uninterrupted data syncing.
- resolved May 12, 2026, 08:15 AM UTC
This incident has been resolved.
Notice April 2, 2026 Issues with integrations 1h 58m
Started Apr 02, 2026, 09:50 AM UTC· resolved Apr 02, 2026, 11:48 AM UTC
- investigating Apr 02, 2026, 09:50 AM UTC
We are currently investigating an issue with some of our integrations, including Salesforce and Hubspot
- identified Apr 02, 2026, 10:00 AM UTC
We have identified the issue, and are working on remediating the issue
- resolved Apr 02, 2026, 11:48 AM UTC
This incident has been resolved.
Critical October 29, 2025 Connectivity Issues 16h 4m Web, Mobile, API
Started Oct 29, 2025, 03:56 PM UTC· resolved Oct 30, 2025, 08:00 AM UTC
- investigating Oct 29, 2025, 03:56 PM UTC
We are investigating an issue affecting connectivity to our services.
- identified Oct 29, 2025, 04:03 PM UTC
We have identified an issue with our provider and are actively working on a fix.
- identified Oct 29, 2025, 06:16 PM UTC
We have failed over some of our services, which means the Mobile app and API should start recovering shortly. Microsoft, our cloud provider, has identified the source of the issue and expects recovery within the next 30 minutes. We will continue to monitor the situation and provide updates as needed. Thank you for your patience.
- monitoring Oct 29, 2025, 08:32 PM UTC
We are now seeing clear signs of recovery across all our services. We will continue to monitor the situation to ensure full stability.
- resolved Oct 30, 2025, 08:00 AM UTC
This incident has been resolved, all services are back to normal.
Major March 27, 2025 Outreach Integration Issue 3d 22h API
Started Mar 27, 2025, 12:35 PM UTC· resolved Mar 31, 2025, 11:03 AM UTC
- investigating Mar 27, 2025, 12:35 PM UTC
We are currently investigating an issue with our integration towards Outreach. No activities are currently being synced to SalesScreen, all customers using this integration appears to be affected.
- identified Mar 27, 2025, 08:10 PM UTC
The issue has been identified and we are working with Outreach to resolve it.
- identified Mar 28, 2025, 10:22 AM UTC
A temporary solution is now available. To restore functionality, customers need to re-authenticate the Outreach integration from the SalesScreen web dashboard. This solution uses a development version of the Outreach integration. We are actively working with Outreach to get a production version approved.
- resolved Mar 31, 2025, 11:03 AM UTC
This incident has been resolved. Affected customers can now re-authenticate the integration to resume operation.
Notice March 10, 2025 SalesScreen Integration API Down 5h 25m
Started Mar 10, 2025, 03:30 AM UTC· resolved Mar 10, 2025, 08:55 AM UTC
- resolved Mar 10, 2025, 09:26 AM UTC
At 03:30 UTC, the SalesScreen Integration API became unavailable due to the accidental deletion of a required Docker image. As a result, the service failed to start. The issue was reported to the SalesScreen Engineering team at 08:45 UTC, and the team immediately began investigating. The root cause was quickly identified, and a new deployment was initiated. By 08:55 UTC, the service was fully restored. Any events sent to the API between 03:30 and 08:55 UTC were not processed and should be resent. We sincerely apologize for the disruption and appreciate your understanding. We are taking steps to prevent this type of issue from happening again.