Skip to content

Monitoring system and incident detection of Cloud-IAM

Cloud-IAM employ a multi-faceted alerting approach to monitor and detect incident on your managed Keycloak. This process ensures timely detection and swift resolution of incidents, minimizing downtime and maintaining highly available Keycloak.

Location of the monitoring

All our deployment are monitored with an external solution, spread across four geographically diverse locations.

  • Australia
  • North America
  • Europe
  • Asia

Each of this location performs health checks by generating tokens every 30 seconds to verify deployment status.

Monitoring system in case of incident

If all monitors fail to retrieve a token for 2 consecutive minutes, an incident is automatically triggered.

This can occur due to:

  • Response times exceeding 5 seconds
  • Unexpected status codes

In response to the incident, our on-call team (24/7) is notified and will proceed to resolve the incident. Once our on-call team has successfully resolved the issue and our all monitors have been recovered for a minimum of 5 consecutive minutes, the incident will be automatically resolved.

Notification and status

Deployment page on the Cloud-IAM console

You can track the status of your Keycloak deployment directly from your deployment information page on :

By email and support Ticket

Depending on the criticality of the incident and your support level, the on-call team may contact you by email and support ticket for the incident, copied to all members of your organization. More information on Cloud-IAM SLA.

Status Page

Global

A global status page provides real-time visibility into the availability and performance of Cloud-IAM services, allowing you to track any issues or maintenance activities. Learn more about global status page here.

Dedicated

If you have an Expert plan, you will have a dedicated status page for your organization and its associated deployments. Learn more about dedicated status page here.

Report an incident to Cloud-IAM

To report an incident on your Keycloak deployment, please refer to the dedicated Support pages.