Skip to content

System status: how we report incidents and maintenance

This page describes the procedure: where an incident or maintenance is reported, who we notify, which deadlines apply and how you report an incident to us. It does not show a current status per service, histories or metrics.

Customers can see ongoing and announced reports in the customer account under “Maintenance and incidents”. How availability is measured and credited is governed by the SLA: externally, through checkpoints outside our network, with service credits according to a scale.

Initial response P1
15 min
in tier Critical
Included in the price
8 h
Initial response P1, Mon–Fri 08:00–18:00
Maintenance announced
5 calendar days
in advance, without expected interruption
Maintenance per month
8 hours
per resource; anything above this counts as downtime

How we report incidents

Incidents are reported, not concealed. A platform notification always takes the same route: to the customer account of the affected customers and to their technical contacts. This page does not show a live status per service — what affects your services is stated in your customer account.

  1. Notification in the customer account

    An incident or maintenance affecting your services appears as a banner above the content of your customer account and on the “Maintenance and incidents” page. Each notice states the timeframe and the affected locations and product lines, along with the expected impact, as far as it is foreseeable. An account whose services are not affected sees no notice.

    Maintenance and incidents in the customer account

  2. E-mail to your technical contacts

    Maintenance and incidents are additionally sent by e-mail to the technical contacts saved in the customer account, and an incident also to the emergency contact — regardless of which channels you have set up. Anyone who already receives the notification via their own channel will not receive it twice.

  3. The status is updated

    A notice goes through the statuses “announced”, “in progress” and “resolved”. We report each new status via the same channels as the first. Resolved notices remain readable in the customer account history for 90 days.

  4. Security-related incidents

    Security-relevant incidents do not appear as platform notifications. Affected customers receive them directly, according to the procedure and timeframes described under Security and Compliance.

    Reporting channels for a security incident

Subscribe to notifications

You define which notifications you receive per channel in the customer account. A channel is an e-mail address or a webhook; you select the topics “Maintenance” and “Incidents” individually for each channel.

Independently of this, the registered technical contacts receive every maintenance and every incident, the emergency contact every incident.

  • Email

    An address of your choice, such as the distribution list of your operations team. You define which topics the channel receives when creating it; the saved technical contacts receive maintenance and incidents even without their own channel.

    Customer account → Profile → Channels

  • Webhook

    An HTTP POST with JSON to an https address of your choice, signed with HMAC-SHA256 so you can verify that the notification comes from us. The customer account shows the secret for this exactly once during creation.

    Customer account → Profile → Channels

Aisle between two rows of black server cabinets, cable trays under the ceiling, grazing light on the doors.

Planned maintenance

A maintenance window is a previously announced period during which we work on our systems. The rules for this are in the “Maintenance window” section of the SLA and apply to every contract: fixed windows, notice periods and a maximum limit per month. You can see announced windows that affect your services in the customer account and receive them by email.

Maintenance rules in the SLA
Fixed windows
Tue and Thu, 01:00–05:00
Notice without interruption
5 calendar days
Notice with interruption
14 calendar days
Upper limit per month
8 hours
Postponement on request
up to 14 days
Emergency maintenance
counts at 50%

Announced maintenance does not count as downtime, provided it was announced at least five calendar days in advance and does not exceed eight hours per calendar month and resource; any time exceeding this counts fully as downtime.

What the SLA promises

Promises with a deadline, not with an adjective: the SLA specifies the initial response per support level and priority, the availability per product class and the service credit if we fail to keep a promise. You classify the priority of an incident yourself when reporting it; we only change it after consultation and with justification.

The complete SLA

Initial response times per support level and priority

  1. Basic (included in the price)

    P1 critical
    8 h
    P2 significant
    12 h
    P3 minor
    24 h
    P4 request
    48 h
    Availability
    Mon–Fri 08:00–18:00
  2. Business

    P1 critical
    2 h
    P2 significant
    4 h
    P3 minor
    8 h
    P4 request
    24 h
    Availability
    P1 24/7, otherwise Mon–Sat
  3. Enterprise

    P1 critical
    30 min
    P2 significant
    2 h
    P3 minor
    4 h
    P4 request
    12 h
    Availability
    24/7, telephone
  4. Critical

    P1 critical
    15 min
    P2 significant
    1 h
    P3 minor
    2 h
    P4 request
    8 h
    Availability
    24/7, dedicated phone number

The initial response is the first substantive reply from a responsible person; an automatic acknowledgement of receipt does not count. The SLA does not promise a resolution time because it depends on the cause.

P1 — critical
Production operations are completely down, there is no workaround.
P2 — significant
Production operations are significantly impaired or a workaround can only be used with noticeable effort.
P3 — minor
A single function is disrupted, operations essentially continue.
P4 — request
Questions about usage, change requests, quotes, billing.

Where to reach us

If everything is running within the target range for us but not for you, report the incident with the details that allow for quick assignment. We give priority to tickets from the customer account because the account and resources are already assigned there.

All channels and responsibilities

Technical support

Incidents, configuration questions, hardware replacement, recovery. Please always include the resource ID, timestamp with time zone and error description.

Email
support@entronyx.cloud
Available
Basic: Mon – Fri 08:00 – 18:00 · Business, Enterprise and Critical: 24/7
Initial response
Initial response 15 minutes to 8 hours, depending on support level and priority — commitment from the SLA

Tickets from the customer panel are processed with priority because the account and resources are already assigned there.

These details help with every report

A service credit request under the SLA requires the same details — sending them along saves a follow-up question.

  • Identifier of the affected resource and region
  • Start and end of the disruption with date, time and time zone
  • Description of the error, with log excerpts where possible
  • Your own measurement data, if available — it is helpful, but not a prerequisite

If the cause is not on our end, we will say so

An incident that we are aware of is listed as a report in your customer account. If everything is running within the target range on our end but not on yours, a resource ID, timestamp with time zone and an extract from the log help the most.

Initial response P1
15 min
Fixed windows
Tue and Thu, 01:00–05:00
Notice without interruption
5 calendar days
Upper limit per month
8 hours