История сбоев Demandbase

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.

We are currently experiencing issues with DB1 for Sales, Chrome extension and ULB due to underlying AWS issues.

Team is working on a few mitigation strategies

We are continuing work on this issue. It is also impacting DB1 for Marketing in addition to Sales. Ads data visibility is also affected.

We are recovering our infrastructure in a new availability zone while we wait for Amazon to recover the failed availability zone

We are continuing to work on a fix for this issue.

We have recovered from the errors we were experiencing previously. We are working on getting the data caught up.

We are continuing to work on refreshing DB1 with the latest data.

DB1 data is up to date.

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.

All tenants are up to date.

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.

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.

This incident has been resolved.

We are aware of the issue and investigating.

We are continuing to investigate this issue.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

We are investigating slowness in the Demandbase platform.

The latency has improved. We are continuing to investigate the root cause.

This incident has been resolved.

We are aware of performance issues in the Demandbase application. The team is investigating.

The site performance has returned to normal. We will continue to monitor it.

This incident has been resolved.

We are aware of an issue with logging into Demandbase and are working with our vendor to fix it.

We are continuing to investigate this issue.

The incident has been resolved.

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.