| Sitecore via Azure Marketplace | Service is operating normally |
| Sitecore via AppSource | Service is operating normally |
| Device Detection | Service is operating normally |
| IP Geolocation | Service is operating normally |
| App Center UI | Service is operating normally |
Jun 18, 2019
Sitecore Azure Marketplace Core services update
Sitecore Cloud Operations team is preparing a planned update on the Azure Marketplace infrastructure with new release packages & product packages.
Affected Sitecore Cloud Service: Sitecore Azure Marketplace.
Expected impact on customers: No impact to the existing Sitecore Customer's Cloud resources.
Release Highlights:
- Sitecore 9.2.0 with modules
- CDN 1.0.0
- JSS 12.0.0
- SXA 1.9.0
- Salesforce 1.0.0
Resolved: The scheduled Azure Marketplace update is succesfully completed.
In Progress:
The update has been started
Scheduled: This upgrade has been scheduled
Jun 14, 2019
Sitecore Package Management Service Update
New version of Package Management Service with new PackageRepository for Azure Storage account.
Update center will be unavailable for short term.
Impact on Customers: No downtime and no impact on live customer solutions expected.
Resolved: Package management service was successfully updated
In Progress: The update has been started
Scheduled: The update has been sceduled
Jun 14, 2019
Sitecore App Center access issue
Issue: The Sitecore App center is unavailable, due to issues with login functionality.
Impact on Customers: Sitecore customers/partners will not be able to access App center.
Actual impact is that the customers/partners/sitecore account managers will not be able to view the consumption details of IP Geolocation, Sitecore Email Cloud & Sitecore Managed cloud.
Also, purchasing of a new pricing plan / subscribing to a new Sitecore cloud service / changing the existing price plan is affected.
Resolved: App center backend issues are now resolved & we have verified that the login now works fine.
Identified: Unable to login to the Sitecore App center, due to issues with login functionality. Sitecore engineers are working on resolve the issue.
Jun 13, 2019
Sparkpost Sending Domains service maintenance for EU customers
The "Sparkpost" will perform maintenance on the Sending Domains service for customers provisioned in the EU region on Thursday June 13th.
During the 4 hour maintenance window, the Sending Domains API will be in read-only mode. This maintenance window is only for customers provisioned in the EU.
Affected Sitecore Cloud Service: Email Cloud
Impact on Customers: In that period of time creating, editing, deleting, or verifying sending domains via the Sending Domain API will not be available for customers provisioned in the EU.
Completed: The upgrade has been successfully completed.
In Progress: The upgrade has been started
Scheduled: Sparkpost sending domains service maintenance for EU customers
May 12, 2019
Sitecore Email Cloud (Sparkpost) - Transition from Message Events API to Events API
During daily monitoring activities, Sitecore Cloud Operations engineers noticed an operational notice from the Email cloud vendor "Sparkpost" which communicates that the Message Events API will be replaced by the Events API
Affected Sitecore Cloud Service: Sitecore Email Cloud customers
Customer identification: Sitecore Email Cloud customers
Impact: Starting on October 1, 2019, all the API calls made to Sparkpost must use the Events API. The Message Events API will be discontinued, and hence customers using the Message Events API will not be able to get the required data from Sparkpost.
Additional references: The Events Search which is part of the Events API has robust searching capabilities that provide ready access to the raw event data associated with the messages that are sent via SparkPost.
In order to help the customers with the transition, Sparkpost has also come up with a migration aid for node.js or python.
UPDATE:
It has been confirmed that this update/change will NOT impact any of the Sitecore Email cloud customers.
And Sitecore Cloud Operations have taken necessary internal actions regarding this API change.
Identified: