Demandbase Outage History

Feb 19, 14:39 PST Resolved - All tenants are up to date. Feb 19, 07:33 PST Monitoring - We identified an issued that caused a delay in refreshing today's data. We have a handful of tenants we are still processing and expect them to be caught up by this afternoon.

Feb 7, 21:26 PST Resolved - This incident has been resolved. Feb 6, 17:50 PST Monitoring - We have identified the cause of the issue.and we are confirming a fix. We will need to work with the affected customers to fix their tenants. Salesforce is enforcing a new security policy that impacts a small number of tenants. Feb 6, 15:50 PST Investigating - We are aware of an issue with syncing between Demandbase and Salesforce. The issue is currently limited to a handful of tenants. We are investigating the root cause.

Jan 27, 12:31 PST Resolved - This incident has been resolved. Jan 27, 08:59 PST Monitoring - A fix has been implemented and we are monitoring the results. Jan 27, 08:43 PST Update - We are continuing to investigate this issue. Jan 27, 08:43 PST Investigating - We are aware of the issue and investigating.

Oct 21, 06:10 PDT Resolved - This incident has been resolved. Oct 20, 05:53 PDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 20, 05:52 PDT Investigating - AWS making progress on resolving the issue with new EC2 instance launches in the US-EAST-1 Region and are now able to successfully launch new instances in some Availability Zones. We are applying similar mitigations to the remaining impacted Availability Zones to restore new instance launches. As we continue to make progress, customers will see an increasing number of successful new EC2 launches. We continue to recommend that customers launch new EC2 Instance launches that are not targeted to a specific Availability Zone (AZ) so that EC2 has flexibility in selecting the appropriate AZ.

Sep 24, 09:30 PDT Resolved - This incident has been resolved. Sep 24, 09:08 PDT Monitoring - The latency has improved. We are continuing to investigate the root cause. Sep 24, 09:05 PDT Investigating - We are investigating slowness in the Demandbase platform.

Sep 14, 15:59 PDT Resolved - The incident has been resolved. Sep 14, 15:33 PDT Update - We are continuing to investigate this issue. Sep 14, 15:33 PDT Investigating - We are aware of an issue with logging into Demandbase and are working with our vendor to fix it.

Aug 29, 21:28 PDT Resolved - This incident has been resolved. Aug 29, 13:27 PDT Monitoring - We have identified the issue and intent should being to appear over the next 2 to 3 hours. Aug 29, 10:44 PDT Investigating - We are aware that Bombora intent is not appearing in customer accounts and we are investigating.

Aug 22, 13:04 PDT Resolved - All customer data is now up to date. Aug 22, 06:07 PDT Investigating - We are currently investigating this issue.

Jul 11, 12:09 PDT Resolved - Demandbase One for Sales is working normally now. Jul 11, 11:47 PDT Monitoring - Requests to DB One for Sales are starting to recover. We are continuing to monitor the recovery. Jul 11, 10:48 PDT Investigating - We are aware of an issue with Demandbase One for Sales and are investigating.

Jun 25, 08:17 PDT Resolved - Last nights refresh was successful and customer data is up to date. Jun 24, 14:30 PDT Identified - We belieive we have identified the issue. Data will be refreshed at the next opportunity which will be tomorrow morning. We will be watching the jobs to make sure they are successful. Jun 24, 07:52 PDT Investigating - We are experiencing issues with refreshing customer tenants this morning. We are looking into it.

Jun 19, 13:58 PDT Resolved - All tenants are up to date. Jun 19, 07:42 PDT Update - We have identified additional issues and are continuing to work on the issue. Jun 18, 13:00 PDT Identified - We believe we have identified the root cause. We expect all the tenants to be up to date after tonight's refresh. Jun 18, 09:27 PDT Update - We are continuing to investigate this issue. Jun 18, 09:27 PDT Investigating - We are currently investigating this issue.

Jun 3, 09:01 PDT Resolved - This incident has been resolved. Jun 3, 08:40 PDT Monitoring - A fix has been implemented and we are monitoring the results. Jun 3, 03:23 PDT Identified - The issue has been identified and fix will be pushed tomorrow morning. Jun 3, 02:34 PDT Update - We are aware of issues. It was due to a bad workspaceId lookup that was pushed to prod as part of last week's release. Jun 2, 20:13 PDT Investigating - We are currently investigating an issue with slack notification delivery.

The roll back was successful. We are following up with a handful of users who may still be experiencing issues.

We have implemented a fix and are monitoring the results.

We are aware of an issue with DB1 and believe it has been resolved.

Our email provider is experiencing delays in delivering subscription emails.