Is BitTitan Down Right Now? Check if there is a current outage ongoing.

We are currently investigating an issue affecting document migrations involving Google Drive, OneDrive, and SharePoint. Customers may experience intermittent authentication or connectivity errors when running migrations in these areas. As a temporary workaround, re-running the affected migration items typically resolves the issue. Our engineering team is actively working toward a permanent resolution. We appreciate your patience and will provide additional updates as soon as they become available.

We are currently investigating an issue affecting document migrations involving Google Drive, OneDrive, and SharePoint. Customers may experience intermittent authentication or connectivity errors when running migrations in these areas.As a temporary workaround, re-running the affected migration items typically resolves the issue.Our engineering team is actively working toward a permanent resolution. We appreciate your patience and will provide additional updates as soon as they become available.

We’re pleased to confirm that the issue causing migration failures with the error “The method or operation is not implemented” has been fully resolved. We apologize for any inconvenience this may have caused, and appreciate your patience as we worked to implement a fix

We are aware that some migrations are failing with the error: “The method or operation is not implemented.” in some Microsoft Teams and SharePoint migrations. Our engineering team has identified a solution and is actively working on developing the fix. We are targeting deployment by Friday, May 2, and will continue to provide updates as progress is made.

We are currently investigating migrations that are failing with the error: “The method or operation is not implemented.” in some Microsoft Teams and Sharepoint migrations. Our engineering team is actively working to identify the root cause and implement a resolution. We will update this status again no later than Tuesday, April 22.

As of March 31, 2025, Microsoft has ended support for app-only authentication in the OneNote API. To maintain functionality, users must switch to delegated authentication. This is a Microsoft platform change, and MigrationWiz cannot mitigate this. Microsoft’s Official Announcement(https://learn.microsoft.com/en-us/graph/api/resources/onenote-api-overview?view=graph-rest-1.0) Using Delegated Permissions for OneDrive, SharePoint, and Teams migrations(https://help.bittitan.com/hc/en-us/articles/360038153373-Using-Delegated-Permissions-for-OneDrive-SharePoint-and-Teams-migrations)

As of March 31, 2025, Microsoft has ended support for app-only authentication in the OneNote API. To maintain functionality, users must switch to delegated authentication.This is a Microsoft platform change, and MigrationWiz cannot mitigate this. Microsoft’s Official Announcement(https://learn.microsoft.com/en-us/graph/api/resources/onenote-api-overview?view=graph-rest-1.0)Using Delegated Permissions for OneDrive, SharePoint, and Teams migrations(https://help.bittitan.com/hc/en-us/articles/360038153373-Using-Delegated-Permissions-for-OneDrive-SharePoint-and-Teams-migrations)

Microsoft has announced a change to Exchange Web Services (EWS) access in Exchange Online, effective at some point in April 2025 (Microsoft has not provided a specific date for this change). Once this change has been made, EWS access will only be allowed if both the organization-level and user-level EWSEnabled flags are set to True. To avoid any service disruptions, please ensure that EWS is enabled at both levels in your Microsoft 365 tenant. If either flag is set to False, EWS requests will be denied, and your migrations or services relying on EWS may fail. We strongly recommend reviewing your settings in advance. For more information, refer to Microsoft’s official announcement: 👉 [The way to control EWS usage in Exchange Online is changing.](https://techcommunity.microsoft.com/blog/exchange/the-way-to-control-ews-usage-in-exchange-online-is-changing/4383083) If you need assistance, please contact our support team.

Microsoft has announced a change to Exchange Web Services (EWS) access in Exchange Online, effective at some point in April 2025 (Microsoft has not provided a specific date for this change). Once this change has been made, EWS access will only be allowed if both the organization-level and user-level EWSEnabled flags are set to True.To avoid any service disruptions, please ensure that EWS is enabled at both levels in your Microsoft 365 tenant. If either flag is set to False, EWS requests will be denied, and your migrations or services relying on EWS may fail.We strongly recommend reviewing your settings in advance.For more information, refer to Microsoft’s official announcement: 👉 [The way to control EWS usage in Exchange Online is changing.](https://techcommunity.microsoft.com/blog/exchange/the-way-to-control-ews-usage-in-exchange-online-is-changing/4383083)If you need assistance, please contact our support team.

This incident has been resolved.

We are aware that some customers are receiving a credential verification error for OneDrive migrations. The team is working to resolve this issue.

This incident has been resolved.

You may see an informational message noting that your destination region is outside of Germany but this message is in error. In fact your migration will run in the correct location, based on your settings. You can safely ignore this message.

The certificate issue for OneDrive, SharePoint and Teams migrations has been fixed. Please resubmit any failed migrations.

BitTitan is aware of a Certificate issue impacting all OneDrive, SharePoint, and Teams migrations. We are actively working to resolve the error.

After a successful MigrationWiz release on 12/4, we are no longer seeing issues with Stalling Mailboxes.

We believe we have located the root cause of the stalling O365 mailbox migrations, which was amplified by the Microsoft Service Health issue last week. We are preparing a code fix, with a target release for today 12/4 in the late afternoon US time, which we anticipate will resolve the Stalling Mailbox issue.

Due to an ongoing Microsoft service degradation, some O365 Mailbox Migrations may become stuck in the migrating phase. These mailboxes will appear not to be moving any data for an extended period. The workaround at this time is to Stop the migration and Resubmit the mailbox. In most cases, the new connection will bypass the issue, and the mailbox migration will be complete. In some cases, specific mailboxes may need to be Stopped and Resubmitted again.

We have collaborated with Google and implemented the necessary algorithms to mitigate the throttling issue. The Google API endpoint is now stable and can be used for all new migration projects. Please note, for mailboxes that have already been migrated using the Gmail IMAP connector, continue using that connector to avoid any potential data inconsistencies. The Google API endpoint should be used for new mailbox migrations only.

We are currently experiencing a known issue with the Google API due to recent changes made by Google. These changes are causing extreme throttling and slowness in our services. To mitigate this issue, we recommend using the Google (IMAP) connector for all Google Mail migrations until we can resolve the problem. We apologize for any inconvenience this may cause and appreciate your understanding as we work to address this issue.

This incident has been resolved, the Advanced Options from the left panel works as expected.

Identified - Users are reporting an issue with editing or saving Advanced Options using the left panel. Mailbox, Public Folder, and Teams Private Chat projects are not impacted. Please modify the Advanced Options screen by selecting the down arrow next to the Edit Project Button and then selecting Advanced Options from the drop-down menu. Before you submit any migrations, please confirm your Advanced Options are in place and valid.

Users are reporting an issue with editing or saving Advanced Options using the left panel. Please modify the Advanced Options screen by selecting the down arrow next to the Edit Project Button and then selecting Advanced Options from the drop-down menu. Before you submit any migrations, please confirm your Advanced Options are in place and valid.

This incident has been resolved.

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

MigrationWiz no longer supports Teams private chat history as part of Mailbox migrations due to Microsoft's restriction on Teams data access through EWS. For more information please review this article here -https://learn.microsoft.com/en-us/exchange/troubleshoot/send-emails/ews-not-support-access-teams-data We are currently developing a replacement feature utilizing updated APIs. However, we do not have an estimated time for the return of Teams Private Chat migration at this moment. Please note that Teams to Teams migrations (excluding Teams Private Chat) are supported as they utilize Microsoft Graph API.

This incident has been resolved.

BitTitan is aware of an issue that is impacting certain OneDrive to OneDrive migrations, and we are reviewing this issue with Microsoft Support. At this time, the recommended solution is to add the following Advanced Option in your project, if you are migrating metadata and versioning for OneDrive. OneDriveProSkipSourceEmailValidation=true

Investigating - BitTitan is aware of an issue that is impacting certain OneDrive to OneDrive migrations, and we are reviewing this issue with Microsoft Support. The recommended solution is to add the following advanced option in your project. OneDriveProSkipSourceEmailValidation=true

BitTitan is aware of an issue that is impacting certain OneDrive to OneDrive migrations, and we are reviewing this issue with Microsoft Support. The issue is transient, and the recommended solution is to resubmit your migration first and then try an alternate region within advanced options.

The issue has been resolved and the Help Center form is now functioning correctly. Customers can create the tickets through Help Center now.

The issue has been identified and fix is being implemented. Meanwhile, please submit the support ticket via email to support@bittitan.com

Customers are not able to create new tickets using the form from help.bittitan.com Customer can reach support by emailing support@migrationwiz.com or support@bittitan.com Our teams are currently working on getting the Help Center form back online

This issue now stands resolved. We regret for the inconvenience you might had because of this and thanks you for your kind cooperation.

Some MigrationWiz customers may be experiencing slow migration speeds. Our teams are working hard to identify the cause and resolve. We will keep you updated as we have more details. ETA for next Update : 2Hrs

The reported issue with UMB licenses stands resolved now. We regret the inconvenience you might have experienced because of this and thanks you for your kind co-operation as always.

We are continuing to investigate this issue. We will post an update as we have more details. ETA for next update: 2Hrs

We are currently seeing issues being reported that UMB licenses are not being applied to projects in MigrationWiz. This is currently affecting the UMB licenses only – There are no workarounds at this time. Our tech teams are working to get this sorted at the earliest. We will post an update as we have more details. ETA for next Update : 2Hrs

This incident has been resolved.

This issue stands resolved now. We are extremely sorry for the inconvenience caused during this period and thank you for your patience and kind cooperation.

Our teams are actively working on getting this issue resolved. Meanwhile, to create a new support incident, please email our support team at Support@migrationwiz.com

While this issue is being actively worked upon to get fixed by our engineering teams, please drop an email to Support@migrationwiz.com for creating the support tickets

While this issue is being actively worked upon to get fixed by our engineering teams, please drop an email to Support@migrationwiz.com for creating the support tickets

While this issue is being actively worked upon to get fixed by our engineering teams, please drop an email to Support@migrationwiz.com for creating the support tickets

We are continuing to investigate this issue, will keep posting with further updates as we learn more. Meanwhile, to create a new support incidents please email our support team at Support@migrationwiz.com

Support Portal is currently not accessible from the Help Center (https://help.bittitan.com/hc/en-us/requests/new) Customers are not able to access the Support Portal in order to create new tickets and check the status of existing tickets. The issue is currently being investigated and we will be posting updates as we learn more. At this time, new support incidents can be opened by emailing support at Support@migrationwiz.com

All the Data Centers are caught up and are processing migrations normally. The issue is now resolved and customers should be able to use MigrationWiz as usual. This Notification is now being set to Resolved. Please reach out to Support, in case of any issues.

We are currently experiencing higher-than-usual Data congestion in our Data Centers. This may result in performance degradation of customer migrations. Performance improvement steps have been taken and this is currently restoring queue status back to a stable condition. The situation will continue to improve and we expect it to reach a normal status.

Our Data Centers are currently experiencing higher-than-usual Data congestion. This may result in performance degradation of migrations, including delays when trying to start/stop a migration. This is affecting both bittitan.com and bittitan.de data centers. Our DevOps team is currently working towards a resolution. There is no ETA as of now but we will post updates as we get more information.

We are currently experiencing higher than usual Data congestion in our Data Centers. This may result in performance degradation of customer migrations. This is affecting both bittitan.com and bittitan.de data centers. Our Devops team is diligently working on resolving these issues. There is no ETA as of now but we will update this status as we progress.

All the Data Centers are caught up and are processing migrations normally. The issue is now resolved and customers should be able to use MigrationWiz as usual. This Notification is now being set to Resolved. Please reach out to Support, in case of any issues.

We are seeing performance degradation of customer migrations, which are caused by higher than usual data congestion seen in our MigrationWiz Data Centers. The backlogged queues at the Data centers are currently being cleared and are getting back to normal, post extensive performance improvement steps taken by our engineers. We are currently monitoring the situation and are seeing the queue status improve and we expect it to reach a normal status.

Our Data Centers are currently experiencing a higher than usual congestion which is causing potential performance degradation of customer migrations. Our DevOps engineers have taken significant performance improvement steps and the backlogged migration queues are currently getting back to normal. We will continue to monitor the situation as it continues to improve and we expect it to reach a normal status.

We are currently experiencing higher-than-usual Data congestion in our Data Centers. This may result in performance degradation of customer migrations. Performance improvement steps have been taken and this is currently restoring queue status back to a stable condition. The situation will continue to improve and we expect it to reach a normal status.

We are seeing performance degradation of customer migrations, which are caused by higher than usual data congestion seen in our MigrationWiz Data Centers. The backlogged queues at the Data centers are currently being cleared and are getting back to normal, post extensive performance improvement steps taken by our engineers. We are currently monitoring the situation and are seeing the queue status improve and we expect it to reach a normal status.

Our Data Centers are currently experiencing a higher than usual congestion which is causing potential performance degradation of customer migrations. Our DevOps engineers have taken significant performance improvement steps and the backlogged migration queues are currently getting back to normal. We will continue to monitor the situation as it continues to improve and we expect it to reach a normal status.

We are currently experiencing higher-than-usual Data congestion in our Data Centers. This may result in performance degradation of customer migrations. Performance improvement steps have been taken and this is currently restoring queue status back to a stable condition. The situation will continue to improve and we expect it to reach a normal status.

Performance improvement steps have been taken and this is currently restoring queue status back to a stable condition. The situation will continue to improve and we expect it to reach a normal status.

We are currently experiencing higher than usual Data congestion in our Data Centers. This may result in performance degradation of customer migrations. This is affecting both bittitan.com and bittitan.de data centers. Our Devops team is diligently working on resolving these issues. There is no ETA as of now but we will update this status as we progress.

The Microsoft 365 mailbox migration error "Error: ErrorInternalServerError" isn't observed anymore. The issue is now marked as resolved.

The Microsoft 365 mailbox migration error "Error: ErrorInternalServerError" observed to be transient and likely self resolved at Microsoft end. The workaround to reset and resubmit the migrations helped customer who reported the error. We will continue to monitor the issue while working with the Microsoft support.

Issue Description: Microsoft 365 Mailbox migrations are experiencing intermittent issues that return the error: `Your migration failed while checking destination credentials. An internal server error occurred. The operation failed. Error: ErrorInternalServerError. Destination Server`` when starting a migration Affected customers: Mailbox migrations with “Microsoft 365” (Exchange Online) as the Source or Destination endpoint. Current status: The issue is due to the Microsoft 365 tenant EWS response. Our teams are currently working with Microsoft Support to resolve the issue. Potential workaround: This is a transient issue. Resubmitting the migration may solve the issue.

The issue has been identified to cause due to the Microsoft 365 tenant EWS response, the developer is working with Microsoft support.

We are currently investigating Microsoft 365 Mailbox migrations fail intermittently with "Error: ErrorInternalServerError".

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Our team is investigating the issue that is causing error for submitting migrations under .DE environment.

This incident has been resolved.

We have reports of availability being impacted for our MigrationWiz.bittitan.de site at this time. Our teams are actively investigating the cause to resolve the issue. Please note this does not affect MigrationWiz, MSPComplete, or DeploymentPro, and no other sites are impacted. The ongoing migrations in Germany Data Center are not affected as well.

This incident is resolved.

Our teams are continuing to work on the issue. However, MigrationWiz and MSPComplete have been restored and are online. As we continue to work through the issue, please begin with testing your migration scenario to ensure it works as expected for your environment. At this time, we ask that you begin all migration projects with small batches as we are continuing to work through this issue with Microsoft. We will provide more information as it becomes available.

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

Our team is making progress on testing the solution - however our latest ETA on recovery is approximately another 3 hours

The recovery process is delayed. Latest ETA for fix is 3 - 5 hours.

The recovery process is delayed. Latest ETA for fix is 2 - 4 hours.

We are engaged with Microsoft and working on a fix ETA 2-6 hours

Our teams are still working towards the resolution of the issue.. At this time we do not have an ETA but this is being treated as critical and all resources available are working towards the quickest resolution possible

Our teams are still working towards the resolution of the issue.

INTERNATIONAL INSTANCE of MigrationWiz and MSPComplete is currently not accepting connections or processing submissions. Our engineering team is currently investigating the issue. ETA to resolution is currently unknown. Please continue to monitor this page for updates. (Germany and China instances are not effected) International instance includes : United States, Netherlands, Western Europe, Singapore, Asia Pacific, Australia, Japan, Brazil, South America, Canada, Ireland, Northern Europe, France, South Africa

We are experiencing slower then usual migrations and delay in submission of jobs for "United States" Data center. Our engineering team is currently investigating on the issue.

This incident has been resolved.

The App Certification issue is confirmed resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

"We are currently experiencing an issue that is preventing Document migrations from running. Our development team is aware of the issue and has identified the cause as well as the necessary steps to resolve this. They are actively working toward a solution."

This incident has been resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

We are aware of a current issue with applying User Migration Bundle licenses to users within MigrationWiz. This is being caused by an issue with certain workflows on the MigrationWiz back-end. This would also be affecting users ability to request project statistics from their migrations. Our team has identified the cause of the issue and is currently working on a solution to get everything back to normal.

We are aware of a current issue with applying User Migration Bundle licenses to users within MigrationWiz. This is being caused by an issue with certain workflows on the MigrationWiz back-end. Our team is actively investigating and is working to resolve this as quickly as possible. This would also be affecting users ability to request project statistics from their migrations.

We are aware of a current issue with applying User Migration Bundle licenses to users within MigrationWiz. This is being caused by an issue with certain workflows on the MigrationWiz back-end. Our team is actively investigating and is working to resolve this as quickly as possible.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

We have reports of performance/availability being impacted for MigrationWiz and BitTitan.com at this time. This may also cause submitted migrations to take longer than usual to get started Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident has been resolved.

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

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

The issue has been identified and a fix is being implemented.

Some customers are facing errors when starting a migration.

This incident has been resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved. If any users are still affected after 60 minutes, please respond to or create a support ticket for further assistance.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We are continuing to investigate this issue.

We have reports of performance/availability being impacted for DeploymentPro at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

We are pleased to confirm that this incident is now resolved.

The fix for this issue has now been deployed. We will be monitoring this issue to verify that this incident has been fully resolved

Our dev team are continuing to work on this problem. They have identified the fix and are planning the deployment of a patch to resolve this issue. We are expecting the deployment to be completed in approximately 3 hours time. Thank you

We are aware of an issue at present concerning Teams migrations where the Advanced Option UserMapping/RecipientMapping is used for Teams permissions. This Advanced Option is not functioning and therefore permissions remapping will not be correct. The problem affects ALL Teams Migrations in all our of our portals but note that this does not affect other migration types nor does it affects if Teams Permission is not selected during migration. Our advice to customers at present is not to run a Teams permission migration. Our dev team are working on an emergency patch to resolve this issue and this is expected to be deployed in approx. 4 hours time. We will provide a further update shortly. We apologise for any inconvenience caused by this problem

All indications show that the deployment of the fix has been completed by Microsoft and that this issue has been resolved for our customers.

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take 1 more day from now for this to be 100% deployed to all tenants. We have had reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. We will provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 3 days from now for this to be 100% deployed to all tenants. We have had some reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 4 days from now for this to be 100% deployed to all tenants. We have had some reports where this has been deployed to tenants already and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft are continuing to deploy the fix for this issue to affected tenants. This could take a further 5 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and has resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 6 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 6 days from now for this to be 100% deployed to all tenants. Although we have had some reports where this has been deployed to tenants earlier and resolved the issue. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

Microsoft have provided an update that the fix for this issue is in the process of being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will continue to provide any further information as soon as we receive it from Microsoft. Thank you for your understanding.

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

The fix from Microsoft for this issue is still being deployed to affected tenants at this time. Note that it is expected to take up to 7 days from now for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092 We will continue to provide further updates as soon as possible.

The fix from Microsoft for this issue is still being deployed to affected tenants at this time. Note that it is expected to take up to 8 days for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092 We will continue to provide further updates as soon as possible.

We have had confirmation from Microsoft that a fix is in the process of being deployed to affected tenants. Note that it is expected to take up to 8 days for this to be 100% deployed to all tenants. If you have been affected by this problem please continue to retry the migration to verify that the fix has been deployed. In the meantime we will provide any further information as soon as we receive it from Microsoft Microsoft released an advisory earlier with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092 We will continue to provide further updates as soon as possible.

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. Microsoft have released an advisory with further information (EX257082) and this can be downloaded from the following: https://bittitan.sharefile.com/d-s9150a59c5da74ef5a4a9a1fb8ce9b092 We will be providing further updates as soon as possible

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

The cause of the issue has been identified by Microsoft and we are working with them to develop a deployment plan for resolution as soon as possible and will provide further updates as information becomes available. We appreciate this is impacting our customers and apologize for any inconvenience caused

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We appreciate this is impacting our customers and apologize for any inconvenience caused

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We appreciate this is impacting our customers and apologise for any inconvenience caused

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are still working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible

We are aware that some customers are experiencing the following error when migrating mailboxes to an O365 destination. "An internal server error occurred. The operation failed., Object reference not set to an instance of an object." Microsoft is aware of this issue and is working towards a fix. We are working urgently with Microsoft to seek guidance and an ETA on a permanent resolution and to ascertain any workaround available for customers. We will be providing further updates as soon as possible. We sincerely apologize for any inconvenience caused. Some affected customer admins may be able to see Microsoft's advisory in the MS Office Portal with incident number EX257082. This affects all of our MigrationWiz portals.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

The issue have been identified as a SSL certificate issue. We are working to get this resolved. As a work around, when accessing help.bittitan.com, please click on "Advanced" button in the page encountered and then on the link that is displayed to proceed to the desired page.

We are currently investigating reports of the BitTitan Help Center being inaccessible.

This incident has now been resolved.

Impact was regional to United States datacenters. Migration projects stalled in submitted state have been mitigated and will start processing shortly. Our teams continue to monitor system status.

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

Impact was regional to United States datacenters. Migration projects stalled in submitted state have been mitigated and will start processing shortly. Our teams continue to monitor system status.

We are continuing to investigate this issue.

We have reports of migration performance being impacted and migrations may take longer to start running Our teams are actively investigating the cause so mitigation steps can be implemented

This incident is now resolved.

This incident is now resolved.

Site performance has returned to normal. We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We have identified the issue, and have implemented periodic manual mitigation procedures and a workaround in order to eliminate the impact of service degradations.

We have identified the issue, and have implemented periodic manual mitigation procedures and a workaround in order to eliminate the impact of service degradations.

This incident has been resolved.

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

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We are continuing to investigate this issue.

We have reports of performance/availability being impacted for MigrationWiz and BitTitan.com at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams are still working towards mitigation steps.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We are currently experiencing issues with our website. Customers are unable login to MSPComplete and MigrationWiz. Our teams are actively investigating the cause so that mitigation steps can be implemented.

This incident is now resolved.

Our teams are still actively monitoring to verify this incident is resolved.

Our teams are still actively monitoring to verify this incident is resolved.

Our teams are still actively monitoring to verify this incident is resolved.

Our teams are still actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We are aware of the ongoing performance issues with the MigrationWiz site. Our engineers are still actively investigating this and are working to get this resolved as quickly as possible"

We have reports of performance being impacted for MigrationWiz and MSPComplete at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We have reports of availability being impacted for Submitting Migrations at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident has been resolved.

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

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We have reports of performance being impacted for Migrations while in a "Submitted" or "Stopping" state at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident has been resolved.

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

The issue have been identified and we are working on fixing the issue.

We have reports of not being able to apply UMB licenses for the MigrationWiz project line items. Our developer team is actively investigating the cause so mitigation steps can be implemented.

This issue has been addressed. As a reminder, please use only BitTitan.com for any login purposes.

Alert: BitTitan discovered the existence of an illegal website that mimics our website and could be used by threat actors to steal credentials as part of a broader phishing scheme. Please DO NOT enter your BitTitan credentials into any website other than our official website (https://bittitan.com). We are not aware of any breaches in our environment at this time.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

The original issue with the errors in mailbox projects should be resolved. However, as a part of this investigation, it was found that there is also impact which is causing migrations to remain in a submitted status for a long period of time. We are still investigating this additional impact.

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

The issue has been identified and a fix is being implemented.

We have received reports that many users are getting the error "Authentication Error: Bad username or password. You must call the Connect-MsolService cmdlet before calling any other cmdlets." When performing mailbox migrations to Office 365 endpoints. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident is now resolved.

We are continuing to monitor for any further issues.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We have reports of performance being impacted for the Migrationwiz site at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved

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

We have created a fix for this issue, were are testing the fix now.

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

Our team has identified the cause of this incident, and are working towards mitigation steps.

Our team has identified the cause of this incident, and are working towards mitigation steps.

We have reports of availability being impacted for Teams migrations at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We have reports of availability being impacted for submitted migrations. Our teams have identified the cause of this incident, and are working towards mitigation steps.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

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

We looked into this issue and have identified that only a small number of projects are affected. Our team is working on steps to resolve this issue. If you have any users that are stuck in submitted please open a support ticket.

This incident is now resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Mitigation steps have been implemented, and our teams are actively monitoring to verify this incident is resolved.

Our team is working on steps to resolve this issue.

We looked into this issue and have identified that only a small number of projects are affected. We will continue to monitor this issue. If you have any users that are stuck in submitted please open a support ticket.

We have our developers actively investigating this issue.

This incident has been resolved.

We are currently investigating the issue.

Our engineering team has resolved this issue. All systems are currently operational.

Databases maintenance has completed. Website performance is back to normal.

Our team is performing maintenance of our databases. Website performance will be slow and occasional backend error may occurs when you access your projects. Please wait for some time and refresh the web page to retry. The error will not impact your migrations. Website performance will be restored once the maintenance is completed.

This incident is now resolved.

Our teams have identified the cause of this incident, and have implemented mitigation steps. We are actively monitoring to verify this incident is resolved.

We have reports of availability being impacted for our BitTitan.de site at this time. Our teams are actively investigating the cause so mitigation steps can be implemented. Please note this does not affect MigrationWiz, MSPComplete, or DeploymentPro, and no other sites are impacted. You may use the following link to login directly to our services in the BitTitan.de system: https://www.bittitan.de/account/login

Microsoft has confirmed that all services are restored, and our engineers have confirmed that Teams migrations are able to operate as normal at this time. This incident is now resolved.

We are monitoring this issue.

We are monitoring this issue.

We are monitoring this issue.

We are monitoring this issue.

Per Microsoft advisory ID TM203682, their teams have identified a system-wide code regression preventing admins from managing Teams and Channels through the Microsoft Teams admin portal. Admins will also not be able to use cmdlets to access and manage Teams. This regression is currently blocking the basic functions around MigrationWiz Teams assessments and migrations. Microsoft is targeting a deployment fix completion across the next 2 days. Until that time as Microsoft gives the "all clear", we advise not attempting a migration. We will be actively monitoring the status of this regression to provide an update here when one is available.

This incident has been resolved.

Our teams have identified the cause of this incident, and are working towards mitigation steps.

We have reports of availability being impacted for United States datacenters at this time. Our teams are actively investigating the cause so mitigation steps can be implemented.