Daniel Österhof
Oct 1, 2013
  5140
(2 votes)

Service Health Dashboard

Today i can announce the release of a Service Health Dashboard for EPiServer SaaS and Infrastructure services. 

This is a way for us to become more transparent and let you easily view the status of services and follow incidents throughout their lifetime.

 

You will be able to subscribe to updates and get notified every time an incident is created, updated or closed. As well as when we schedule maintenance work on any of our services.


You can be notified of status changes through two channels.

E-Mail will keep you updated throughout the lifetime of an incident (creation, updates, resolution, postmortem etc.)

SMS will notify you of creation and resolution of incidents.

 

Check out the dashboard and sign up for notifications: 

EPiServer Service Health Dashboard

 

For questions, detailed information regarding incidents, changes or problems contact EPiServer Support through the channels listed below:

 

E-Mail:
support@episerver.com

 

Telephone:
Worldwide: +46 855 58 2750
Australia: +61 280 363 161
United States: +1 888 670 5066 (toll free)
United Kingdom: +44 800 066 4784 (toll free)


Oct 01, 2013

Comments

Oct 2, 2013 08:31 AM

Nice, Good job

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |