Flow Documentation
Company PagePlatform Status
  • Overview
  • Platform
    • Release Notes
    • Pricing
      • Compute
      • Kubernetes
      • App Engine
      • Object Storage
      • Mac Bare Metal
      • CI Engine
      • DevOps Services
      • Volumes & Snapshots
      • Load Balancers
      • Elastic IPs
      • VPN & Peering
      • Licenses
      • Support
      • Billing FAQ
    • Account
      • Sign Up
      • Closing account
    • Cashback Program
    • Support
      • Case severity and initial response times
    • Service Level Agreement (SLA)
    • Security & Compliance
      • Log4j Vulnerability
    • Regions
      • ALP1
      • ALP2
      • ZRH1
  • Products
    • Compute
      • Instances
        • How-to
          • Connect to instances
          • Destroy Instances
      • Volumes
      • Keypairs
      • ▫️Networking
        • Private Networks
        • Routers
        • Security Groups
        • Elastic IPs
        • Load Balancers
          • Balancing Pools
        • Certificates
        • VPN & Peering
    • Kubernetes
      • Clusters
      • Resources
        • Volumes Features (CSI)
        • External Load Balancers
        • Cluster Autoscaler
        • Traefik upgrade and tests
        • Update custom resource definitions (CRDs) for VolumeSnapshots
    • Object Storage
      • Instances
      • How-to
        • Access Storage with AWS S3 SDKs
        • Access Storage with Cyberduck
        • Access Storage with Mountainduck
      • Ressources
        • Supported Amazon S3 features
        • Replication Management
          • GET service replication
          • PUT service replication
          • DELETE service replication
    • App Engine
      • Accounts
    • Mac Bare Metal
      • Devices
      • How-to
        • Connect via Remote Desktop
        • Connect via SSH
        • Change Display Resolution
        • Connect local USB devices
      • Resources
        • Deprovisioning
    • CI Engine
      • Subscriptions
      • How-to
        • Setup GitHub Actions Integration
        • Setup Buildkite Integration
        • Customise Image
        • Enable Debug Mode
        • Change Image of Integration
      • Resources
        • Runners & Concurrency
        • Vanilla Images
          • macOS 15.2 - Vanilla
        • Golden Images
          • macOS 15.2 - Golden
        • Custom Images
  • Developer Center
    • Overview
    • API
      • Product Entities
      • Location Entities
    • CLI
    • Terraform
Powered by GitBook
On this page
  • Severity Level Definition
  • Initial Response Time Objectives
  1. Platform
  2. Support

Case severity and initial response times

PreviousSupportNextService Level Agreement (SLA)

Last updated 2 years ago

How quickly your support cases are addressed depends on the assigned severity. You assign the severity of the issue when you open the case. With your agreement, the support team adjusts the assigned severity if an incorrect severity level is selected. For more information about Support plans and pricing, see Support plans.

The following table lists some common examples of support issues, suggested severity levels, and the initial response time objectives. The initial response time objectives are used to describe our goals only and don't represent a performance guarantee.

Severity Level Definition

Severity
Priority
Details

1

Critical

Represents a business-critical incident or scenarios like a complete loss of service or a significant feature that is completely unavailable, and no workaround exists.

2

Normal

Represents a non-business-critical incident and intermittent issues and reduced quality of service. A workaround may be available.

3

Low

Represents general service-related questions, feature requests, and other requests for information.

Initial Response Time Objectives

Initial response time means the maximum time for a technical support team member to get back to the customer. Initial response time objectives do not apply to any billing, invoice, or sales-related inquiry or cases.

Economy Support Plan

Priority
Business Hours°
Non-Business Hours°¹

Standard (Best effort)

Usually response time within 12 hours

Usually response time within 48 hours

Business Support Plan

Priority
Business Hours°
Non-Business Hours°¹

Critical

Within 2 hours

Within 4 hours

Normal

Within 4 hours

Within 12 hours

Low

Within 12 hours

Within 24 hours

First Support Plan

Priority
Business Hours°
Non-Business Hours°¹

Critical

Within 30 minutes

Within 1 hour

Normal

Within 2 hours

Within 6 hours

Low

Within 6 hours

Within 12 hours

° Business Hours Monday till Friday, 08:00 - 18:00 CET/CEST (excl. Saturday, Sunday, and common holidays) °¹ Non-Business Hours Monday till Friday, 18:00 - 08:00 CET/CEST (incl. Saturday, Sunday, and common holidays)

Economy, Business, and First