Partner Connect Service Outage

This incident has been resolved.

Update:
The underlying storage account issue has been successfully resolved by our support team at Databricks who have been working with our engineering team. Partner Connect service is now fully operational and all affected tables are once again accessible.

What You Need to Do:
-You can resume your normal data refresh processes immediately
-If you had modified your scripts to exclude affected tables, you can restore them and rerun your pipelines

Affected Tables (Now Available):
derogatory_summary
company_info
trade_summary
credit_report
public_record
cc_specific_loan_info
spouse
applicants_address_ssn
consumer_vehicle_processings

Ongoing Monitoring:
Our engineering team will continue to actively monitor the system to ensure stability and detect any potential issues.

Support:
If you experience any issues when rerunning your pipelines, please reach out via support if you have any questions or concerns.

We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible.

Our engineering team is working directly with Microsoft Azure and Databricks support to diagnose and remediate the storage account issue. We will prioritize this resolution and provide updates as we make progress.

We sincerely apologize for this disruption to your operations. If you have questions, concerns, or need assistance implementing the workaround, please contact our support team.

We are currently experiencing an outage with our Partner Connect service due to an issue affecting our source storage account. Our engineering team is actively working to resolve this issue.

What's happening:
Partner Connect is temporarily unavailable

What's Affected:
Delta Share access to the following tables:
derogatory_summary
company_info
trade_summary
credit_report
public_record
cc_specific_loan_info
spouse
applicants_address_ssn
consumer_vehicle_processings

Workaround:
While we work to resolve the underlying storage account issue, you can continue your data refresh process by modifying your scripts to exclude the tables listed above. Your pipeline should complete successfully once these tables are removed from your pull requests.

We apologize for this disruption and appreciate your patience as we work to resolve this as quickly as possible. Please reach out via support if you have any questions or concerns.