Inriver service status page

This article provides an overview of the inriver Service Status page. It also contains detailed information about the information available on the Service Status page and how to interpret it. 

To access the Service Status page, click here. 

About the inriver service status page

The inriver Service Status page provides timely and up-to-date information about the state of the inriver services across the board. It communicates planned maintenances as well as unexpected downtime and provides information about the core and add-on functionalities, as well as the APIs.

You can quickly check recorded outages and maintenance for the last 30 days for our global regions and products.

If you want to get an email notification about the current status of the inriver services, make sure to hit the subscribe button.

Overview

Below is a screenshot of the inriver Service Status page. 

Components

Below are the components of the inriver service that the service status page provides information about.

Overview details

1. Click the Settings icon to change time zone or language.
2. Click the Subscribe button to get status-update notifications via email.
3. The Component Summary field contains up-to-date information about the inriver services in the Europe and US clusters.
   • Click the cluster names to expand the list and see the service status for each component.
     • Asset API: API that connects inriver with the system where your digital assets are stored.
     • Content Store: inriver add-on capability where end users can access product information, images, and videos. 
     • Contribute: inriver add-on capability where external users can provide product information.
     • Control Center: Core capability where system-related inriver functionality is managed. 
     • Portal:  Core capability that provides access to the inriver functionalities you're using during the PIM process. 
     • Remoting API: API that connects inriver with external applications/integrations.
     • Rest API: API that connects inriver with external applications/integrations.
     • Supplier Onboarding: inriver add-on capability where suppliers and the onboarding of their product information is managed.
     • xConnect API: API that connects inriver to Content Store, Contribute, and Supplier Onboarding.
4. Use the Component Status History field to view information about recorded outages and maintenance for the last 30 days.
5. The Incident History field lists the details for recorded incidents.

Updating the service status page

The information on the Service Status page is updated by the inriver CloudOps team.

Incidents updates are provided on an hourly basis, except for Major Outage where updates are provided on a 30-minute basis.

Incident states

An incident can go through the following states:

• Investigating - We have acknowledged a potential incident and have started an investigation.
• Identified - We have identified the problem and we are working on a solution or workaround.
• Observing - A mitigation or solution has been applied and we expect the problem to be resolved but we are observing just in case something new happens.
• Resolved - The incident is now considered solved completely.

Incident levels

Depending on the severity, incidents are classified based on the following levels:

• Operational – Everything is working as expected.
• Informational – Everything is working as expected but information provided for the indicated component.
• Under Maintenance – Maintenance is being performed in the indicated component.
• Degraded Performance – The incident has minimal or no customer or business impact, not causing any customer errors. There may however be some performance degradation.
• Partial Outage – The incident has partial impact on this component or multiple components where functionality is impacted. The majority of customers can continue to use the system.
• Major Outage – The incident has a significant impact on the majority or all customers in such a way that the system is seriously disrupted.

Note! The incident levels can be applied both to the whole system or to a single component.

Further reading

Inriver support process

Creating a support ticket

Getting automatic updates inriver service status