Demandbase had 22 outages in the last 2 years totaling 176h 17m of downtime — averaging 0.9 incidents per month.
There were 22 Demandbase outages since September 27, 2024 totaling 176h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are aware of an issue with the performance of Ad Campaigns and we are investigating.
We are continuing to investigate this issue.
The issue is resolved.
We are currently investigating this issue.
This incident has been resolved.
We are aware of the increase in errors in DB1 and we are investigating.
The errors are resolved. We are monitoring.
This incident has been resolved.
The overnight data refresh is behind schedule. We have fixed the issue and are working on getting caught up. The most recent data is from May 13th.
The system is on track to fully catch up by ~5PM Pacific. Tenant data such as yesterday's site analytics and CRM/MAS updates should surface in the next few hours.
We are expecting to be fully caught up in the next 2 to 3 hours.
The data is now up to date.
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.
We are aware that Bombora intent is not appearing in customer accounts and we are investigating.
We have identified the issue and intent should being to appear over the next 2 to 3 hours.
This incident has been resolved.
We are currently investigating this issue.
All customer data is now up to date.
We are aware of an issue with Demandbase One for Sales and are investigating.
Requests to DB One for Sales are starting to recover. We are continuing to monitor the recovery.
Demandbase One for Sales is working normally now.
We are experiencing issues with refreshing customer tenants this morning. We are looking into it.
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.
Last nights refresh was successful and customer data is up to date.
We are currently investigating this issue.
We are continuing to investigate this issue.
We believe we have identified the root cause. We expect all the tenants to be up to date after tonight's refresh.
We have identified additional issues and are continuing to work on the issue.
All tenants are up to date.
We are currently investigating an issue with slack notification delivery.
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.
The issue has been identified and fix will be pushed tomorrow morning.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to an issue with our authentication provider some users are unable to log in. We are investigating
For the remaining users who are still experiencing issues our authentication vendor will roll back the upgrade that is causing the issue tomorrow morning. We will post an update at that time.
The roll back was successful. We are following up with a handful of users who may still be experiencing issues.
This issue is resolved. A handful of users may be asked to reset their passwords before logging in.
We are aware of authentication issues for some users. We have identified the issue and preparing a fix.
The fix has been applied and the issue has been resolved.
DB1 Marketing customers integrated with Salesforce may be experiencing a higher than normal volume of API calls. We are currently investigating
The issue has been found and a hotfix is being applied.
A configuration change has been applied and has resolved the issue.
We are investigating an issue with our LinkedIn integration
The issue has been identified and we are working on a fix.
The fix has been deployed and we will continue to watch to make sure the issue doesn't return.
We are currently investigating this issue.
We have identified the issue and applied the fix.
We are currently experiencing DB1M application load time issues and are working to resolve the issue.
The application load times have returned to normal. We are still investigating the root cause.
We continue to experience performance issues but we have identified the issue and are working on a fix.
We have implemented a fix and are monitoring the results.
This incident has been resolved.