---
slug: stoerung-erkennen
title: "How do I tell there is an incident?"
category: grenzen
locale: en
updated: 2026-10-13
keywords: ["status","incident","availability","uptime","outage","SLA"]
questions: ["Where do I see whether Metrunio is available, and how reliable is that figure?","Do you have a status page?","Is Metrunio down right now?","What is your availability?","How do you measure uptime?","Do you measure from outside or only internally?","Why are there two availability figures next to each other?","How do I know the figures are real?"]
url: https://bench.metrunio.com/en/help/stoerung-erkennen
---

# How do I tell there is an incident?

**Where do I see whether Metrunio is available, and how reliable is that figure?**

The status page at /status shows measured availability for four components over the last 90 days, calculated from samples. We measure twice: from the inside through our own processing, and from the outside through an independent service that calls our addresses from several parts of the world. Both figures sit side by side, along with since when we have been measuring and how many samples each is based on.

## What is measured

- Event intake, the critical part. If it fails, measurement time is lost.
- Processing and attribution, measured by the age of the oldest waiting event, not by whether the process is running.
- Customer portal.
- Read API.

## Measured twice, and why

The large figure is measured from the inside: our own processing checks the other components every minute. If it fails too, no sample is written at all, not even an “unavailable” one. That is why we calculate against the expected number of samples, so a gap counts as downtime. Otherwise a total outage would look like a perfect week.

The smaller figure below it is measured from the outside: an independent service calls our addresses at short intervals from several parts of the world. A minute counts as available only once the majority of locations got through. That way a network fault somewhere in the world does not become an outage at our end, while an outage stays one even if a single location still gets through.

Neither replaces the other. The inside measurement sees the backlog in the queue, which no call from outside can detect. That is why “processing and attribution” carries no second figure. The outside measurement sees everything between you and our application: network, load balancing and certificate.

> **Note:** What the outside measurement still does not answer: whether the path out of your own network was clear. If nothing arrives at your end while both figures are green, the problem is probably between us. Support can help from there. Where the two figures differ noticeably, the cause lies between the services rather than inside them; that too is worth telling support.

## What happens during an incident

An outage in processing causes delay, not loss: events wait in a queue and are caught up. Measurement time is only lost if intake itself fails, which is why it runs separately from the portal and reporting.

> **Legal note:** The figures on the status page are a measurement, not a guaranteed level of availability. A contractual commitment (SLA) is negotiated separately.

## Also asked

- Do you have a status page?
- Is Metrunio down right now?
- What is your availability?
- How do you measure uptime?
- Do you measure from outside or only internally?
- Why are there two availability figures next to each other?
- How do I know the figures are real?

## Related

- https://bench.metrunio.com/en/help/roadmap-phase-2
- https://bench.metrunio.com/en/help/support-erreichen
- https://bench.metrunio.com/en/help/wie-lange-bis-daten