| Sitecore via Azure Marketplace | Service is operating normally |
| Sitecore via AppSource | Service is operating normally |
| App Center UI | Service is operating normally |
Feb 22, 2019
Deployment - Consumption Repository “CRepo” V2 - “CRepo” V2 Service Update & Data Migration from Consumption Repo V1 to Consumption Repo V2
Estimated time frame: Feb 19, 08:02 - Feb 28, 23:30 UTC
Sitecore Cloud Operations team is preparing the following planned release to Sitecore Cloud Services.
Affected Sitecore Cloud Service: Consumption Repository “CRepo” V2
Release summary:
Sitecore Cloud Operations team is preparing the planned Release upgrade of the Consumption Repository Service and also Data Migration from Consumption Repo V1 to Consumption Repo V2.
After the upgrade & the switch from CRepoV1 to CRepoV2, the Sitecore Contact Enrichment services such as the IP Geolocation & the Device Detection will now post their consumption details to the CRepoV2 DB through the CRepoV2 consumption service.
EXM application continues to post to the CRepoV2 as usual, no changes there.
Expected impact on customers:
No known impact to the existing Sitecore Customers anticipated.
Release details:
- Adding Crepo1 to Crepo2.
- Optimize performance of ConsumptionRepo (CRepo)
- Update migration scripts to migrate data from Crepo 1 to Crepo 2.
- Bug Fixes.
- Features:
- Optimizing DB for ApplicationStatistic posting
- Switching CRepo1 to CRepo2
- Optimize Crepo fetching consumption performance
- Update V1 Authorization Ioc support for CRepo1 to CRepo2
STARTED: Upgrade has been commenced
Identified:
Feb 28, 2019
Sitecore Azure AppSource - App Source Sitecore Customer Instances VM Maintenance
Estimated time frame: Feb 28, 00:00 - Mar 06, 23:59 UTC
As part of cloud infrastructure monitoring activities, Sitecore Cloud Operations team identified an alert, which we would like to bring to your attention.
Affected Sitecore Cloud Service:Sitecore Azure AppSource - App Source Sitecore Customer Instances
Customer identification: Sitecore AppSource customers
Issue description:As per Azure communication on the upcoming Azure Maintenance, the Azure Virtual Machines (VMs) associated with Sitecore AppSource customer’s deployments subscription, require an important maintenance update. This update will require a reboot of the VM’s. This specific maintenance is required to migrate these VMs to newer hardware.
Impact: The affected Azure Virtual Machines (VMs) will be rebooted & unavailable for up to 15 minutes after initiating the maintenance. This scheduled maintenance will be performed one update domain at a time, to limit impact to environments configured for high availability. The OS and data disks will be retained, but temporary disks will be reset.
Additional references: https://app.azure.com/h/RXB3-JXZ/0aba87
Date identified : 01-Feb-2019
Date resolved: Not yet
Planned further actions: Azure will automatically initiate maintenance on the VM’s, sometime between February 28, 2019 (00:00 UTC) to March 06, 2019 (23:59 UTC).
Who performs further actions: Microsoft Azure
IDENTIFIED: This planned maintenance has been identified.
Identified:
Feb 22, 2019
Azure Intermittent Network Related Timeouts for xDB Cloud
As part of cloud infrastructure monitoring activities, Sitecore Cloud Operations team identified an alert which we would like to bring to your attention.
During daily monitoring activities, Sitecore Cloud Operations engineers found an issue with Microsoft Azure due to which some of the xDB Cloud customers in North Europe may experience failures/high latency.
Affected Sitecore Cloud Service: Sitecore xDB Cloud - Customers
Additional references: https://azure.microsoft.com/en-us/status
MITIGATED: Azure Engineers scaled out the Front End service by adding more instances, which mitigated the issue.
Identified: During daily monitoring activities, Sitecore Cloud Operations engineers found an issue with Microsoft Azure .
Feb 21, 2019
Email Cloud (Sparkpost) - Scheduled Maintenance - Metrics and Message Events
During daily monitoring activities, Sitecore Cloud Operations engineers determined a Scheduled Maintenance at the Sitecore Email Cloud Vendor, aka Sparkpost Infrastructure due to which some Email Cloud customers might be affected.
Affected Sitecore Cloud Service: Sitecore Email Cloud (Sparkpost)
Issue Description: The Sitecore Email cloud SMTP vendor , i.e Sparkpost will be performing maintenance on the Metrics API and the Message Events API starting on Wednesday, February 20 at 10am Eastern and continuing until 10am Eastern on Thursday, February 21.
Impact: During this maintenance period, some of the Sitecore Email Cloud customers may experience an increase in latencies when calling the Metrics API and elevated levels of timeouts.
The increased latency might also effect the Email cloud metrics Reporting via Sitecore EXM and Email Cloud solutions.
There is no impact on the customer's data as such.
Message injection and outbound message delivery through Sitecore EXM and Email Cloud solutions will not be impacted.
Additional references: https://status.sparkpost.com/incidents/jg78k5qyjxkz
Sitecore engineers will closely follow up on the Maintenance event and post further updates under this event article on status page.
COMPLETED: The schedule maintenance has now been completed by the SMTP vendor (Sparkpost).
IN PROGRESS: The scheduled maintenance is in progress.
Identified:
Feb 01, 2019
Email Cloud - High Sending Errors
Our underlying Email Cloud vendor, Sparkpost, has reported that they are seeing elevated SMTP injection errors that might cause issues in dispatching mails via Sitecore EXM and Email Cloud solutions. This is not affecting customers based in Europe.
Please see additional details: https://status.sparkpost.com/incidents/l6hhbsyhhsbw
Resolved: Email Vendor has identified that the issue has now been resolved.
Monitoring: Vendor is continuing to monitor the situation. No resolution yet.
Identified: High sending error rates were identified by the Email Cloud vendor.
Jan 31, 2019
Sitecore Managed Cloud Customers - Azure Intermittent Network Related Timeouts
As part of cloud infrastructure monitoring activities, Sitecore Cloud Operations team identified an alert which we would like to bring to your attention.
During daily monitoring activities, Sitecore Cloud Operations engineers found an issue with Microsoft Azure due to which some of the Managed Cloud & xDB Cloud customers in West US might be affected.
Affected Sitecore Cloud Service: Sitecore Managed Cloud - Customers, Sitecore xDB Cloud - Customers
Customer identification: A subset of Managed Cloud and xDB Cloud Customers resources hosted in the West US Azure Data Center.
Impact: A subset of customers connecting to their managed cloud environment resources such as App services, Azure SQL Databases, Application Insights, Azure SQL servers, storage accounts, etc in West US may have experienced intermittent network related timeouts or high latency.
Additional references: https://azure.microsoft.com/en-us/status/history/
Date identified: Between 00:45 and 03:30 UTC on 30 Jan 2019
Sitecore engineers will closely follow up on the issue and post further updates under this event article on status page.
Identified:
MITIGATED: Sitecore Cloud Operations discussed this issue with the Microsoft Azure and have heard back from Microsoft support that they have taken actions to mitigate this issue on the Azure infrastructure.
IDENTIFIED: During daily monitoring activities, Sitecore Cloud Operations engineers found an issue with Microsoft Azure due to which some of the Managed Cloud & xDB Cloud customers in West US might be affected.
Jan 30, 2019
Deployment - Managed Cloud Core Update
Sitecore Cloud Operations team is preparing the following planned Release 1.7.1.0 to Sitecore Managed Cloud Services.
Affected Sitecore Cloud Service: Sitecore Managed Cloud Core service.
Expected impact on customers: No downtime and no impact on live customer solutions expected.
Completed: Production deployment has been completed successfully, including the post deploy validations.
In progress: This upgrade has now been started & is in progress.
Scheduled: This upgrade has been scheduled.
Identified: