- Detected by Pingoru
- Aug 04, 2026, 05:30 AM UTC
- Resolved
- Aug 04, 2026, 11:43 AM UTC
- Duration
- 6h 13m
Affected: HIPAA4 (Backup & Recover)HIPAA4 (Archive)HIPAA4 (Data Mask & Seed)CA4 (Backup & Recover)CA4 (Archive)CA4 (Data Mask & Seed)EMEA4 (Backup & Recover)EMEA4 (Archive)EMEA4 (Data Mask & Seed)
Timeline · 4 updates
-
investigating Aug 04, 2026, 05:30 AM UTC
Customers may currently experience disruptions to the user interface of our products. Backups, scheduled jobs, and API traffic are not impacted and continue to operate normally. We are actively working to restore the UI to full service and will provide updates as the situation progresses.
-
investigating Aug 04, 2026, 07:38 AM UTC
We are currently investigating this incident.
-
monitoring Aug 04, 2026, 08:00 AM UTC
We implemented a fix and are currently monitoring the result.
-
resolved Aug 04, 2026, 11:43 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 21, 2026, 08:45 AM UTC
- Resolved
- Jun 21, 2026, 08:45 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 21, 2026, 08:45 AM UTC
Type: Incident Duration: 8 hours and 3 minutes Affected Components: Archive Jun 21, 08:45:00 GMT+0 - Investigating - We are currently investigating this incident. Customers may experience high latency while using Archive on Azure CA4 Jun 21, 11:04:00 GMT+0 - Investigating - We're currently experiencing an issue affecting the Archive service. Customers may be unable to search archived data, and the UI for accessing and managing archive policies is unavailable. We are continuing to work on a fix for this incident Jun 21, 16:25:39 GMT+0 - Monitoring - The incident has been resolved. We are closely monitoring the service to verify its full recovery. Jun 21, 16:47:44 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 07:30 AM UTC
- Resolved
- Jun 15, 2026, 07:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 15, 2026, 07:30 AM UTC
Type: Maintenance Duration: 3 hours Affected Components: Data Mask & Seed, Backup & Recover, Data Mask & Seed, Data Mask & Seed, Backup & Recover, Salesforce Discover, Salesforce Discover, Backup & Recover, Data Mask & Seed, Backup & Recover, Salesforce Discover Jun 10, 15:17:25 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jun 15, 07:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 15, 10:30:00 GMT+0 - Completed - Maintenance has completed successfully
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 09:30 AM UTC
- Resolved
- Jun 10, 2026, 09:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 10, 2026, 09:30 AM UTC
Type: Maintenance Duration: 3 hours Affected Components: Backup & Recover, Salesforce Discover, Data Mask & Seed, Salesforce Discover, Backup & Recover, Data Mask & Seed Jun 10, 09:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Jun 10, 09:30:01 GMT+0 - Identified - Maintenance is now in progress Jun 10, 12:30:00 GMT+0 - Completed - Maintenance has completed successfully
Read the full incident report →
- Detected by Pingoru
- May 29, 2026, 05:04 AM UTC
- Resolved
- May 29, 2026, 05:04 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- May 18, 2026, 01:00 PM UTC
- Resolved
- May 18, 2026, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 18, 2026, 01:00 PM UTC
Type: Maintenance Duration: 2 hours Affected Components: Archive, Archive May 18, 13:00:01 GMT+0 - Identified - Maintenance is now in progress May 18, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully May 18, 13:00:00 GMT+0 - Identified -
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 01:00 PM UTC
- Resolved
- May 11, 2026, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 11, 2026, 01:00 PM UTC
Type: Maintenance Duration: 2 hours and 30 minutes Affected Components: Archive, Archive May 11, 13:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. May 11, 13:00:01 GMT+0 - Identified - Maintenance is now in progress May 11, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully
Read the full incident report →
- Detected by Pingoru
- Apr 01, 2026, 10:00 AM UTC
- Resolved
- Apr 01, 2026, 10:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 01, 2026, 10:00 AM UTC
Type: Incident Duration: 5 hours and 5 minutes Affected Components: Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover Apr 1, 13:39:36 GMT+0 - Identified - We have identified the cause and are working on a resolution. We anticipate a resolution within the next hour. Apr 1, 13:55:23 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 1, 15:04:50 GMT+0 - Resolved - This incident has been resolved. Apr 1, 10:00:00 GMT+0 - Investigating - We are currently investigating this incident.
Read the full incident report →
- Detected by Pingoru
- Feb 17, 2026, 03:11 AM UTC
- Resolved
- Feb 17, 2026, 03:11 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Feb 17, 2026, 03:11 AM UTC
Type: Incident Duration: 6 hours and 58 minutes Affected Components: Backup & Recover, Backup & Recover, , Backup & Recover, Backup & Recover, Backup & Recover, Backup & Recover, APP1 → Feb 17, 03:11:00 GMT+0 - Monitoring - Own Recover backups are currently affected by a widespread Salesforce service disruption that may result in login failures and intermittent service unavailability. The issue is primarily impacting backup services in US Regions. Technical teams are actively investigating the root cause and implementing remediation measures, with more details available via Salesforce Incident 20003707\. Feb 17, 10:08:44 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 28, 2026, 09:19 AM UTC
- Resolved
- Jan 28, 2026, 09:19 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 28, 2026, 09:19 AM UTC
Type: Incident Duration: 1 hour and 45 minutes Affected Components: Archive Jan 28, 09:19:00 GMT+0 - Identified - We working on a fix. Jan 28, 11:03:49 GMT+0 - Resolved - This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 18, 2026, 10:04 AM UTC
- Resolved
- Jan 18, 2026, 10:04 AM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 07:30 PM UTC
- Resolved
- Nov 18, 2025, 07:30 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 04:28 PM UTC
- Resolved
- Nov 17, 2025, 04:28 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Oct 24, 2025, 01:15 AM UTC
- Resolved
- Oct 24, 2025, 01:15 AM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 02:30 AM UTC
- Resolved
- Oct 22, 2025, 02:30 AM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 08:36 AM UTC
- Resolved
- Oct 20, 2025, 08:36 AM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2025, 04:01 PM UTC
- Resolved
- Oct 09, 2025, 04:01 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2025, 03:27 PM UTC
- Resolved
- Sep 29, 2025, 03:27 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2025, 04:20 PM UTC
- Resolved
- Sep 23, 2025, 04:20 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2025, 04:00 PM UTC
- Resolved
- Sep 21, 2025, 04:00 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Aug 29, 2025, 04:11 PM UTC
- Resolved
- Aug 29, 2025, 04:11 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 07:34 PM UTC
- Resolved
- Aug 25, 2025, 07:34 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 06:55 AM UTC
- Resolved
- Aug 22, 2025, 06:55 AM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 03:25 PM UTC
- Resolved
- Aug 19, 2025, 03:25 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →
- Detected by Pingoru
- Aug 05, 2025, 08:53 PM UTC
- Resolved
- Aug 05, 2025, 08:53 PM UTC
- Duration
- —
Affected: Own from Salesforce
Read the full incident report →