---
title: "Get the network summary"
method: GET
path: "/v1/network"
tags: ["Network"]
---

# Get the network summary

`GET /v1/network`

## Request

- Base URL: `https://api.peppolstatus.com`
- URL: `https://api.peppolstatus.com/v1/network`
- Auth: none required

Current host verdict counts, open incidents and anomalies in the last 24h, plus how fresh the Peppol Directory export behind every other endpoint is.

## Response `200`

The network-wide rollup.

- NetworkSummary
  - `hosts` object, required
    - `up` integer, required
    - `degraded` integer, required
    - `down` integer, required
  - `open_incidents` integer, required
  - `anomalies_24h` integer, required
  - `directory_export_at` string, date-time, nullable, required: When the Peppol Directory published the participant export this API serves (its `Last-Modified`, or the export envelope's `creationdt` when upstream sent no header). This is the age of the participant data: an ID registered after this instant is not yet visible here. Null until the first sync records one — treat null as 'unknown', never as 'fresh'.
  - `directory_checked_at` string, date-time, nullable, required: When we last asked the Directory for a newer export, whether or not one existed. Stays current while `directory_export_at` does not when upstream has simply not republished, so compare the two: a recent check with an old export means the Directory is quiet, while both going stale means our sync has stopped. Null when no sync has run.
  - `generated_at` string, date-time, required: When this response was built. Not a data-freshness signal — use `directory_export_at` for that.

---

[API](https://skmtc.dev/peppolstatus/apis/peppolstatus-api.md) · [All operations](https://skmtc.dev/peppolstatus/apis/peppolstatus-api/llms.txt) · [OpenAPI document](https://skmtc.dev/peppolstatus/apis/peppolstatus-api/revisions/7e74fb32f23c?raw)