Zum Inhalt springen

You see the problem before the phone rings

Internet and WAN Monitoring

By the time a site reports that nothing works, the outage has already started. Anexum measures your internet and WAN connections around the clock and makes degradation visible before it turns into long downtime. You get dashboards and reports, with escalation by your SLA.

Define monitoring requirements

What is Internet and WAN Monitoring?

Business internet monitoring should measure more than uptime. Anexum can collect latency, jitter, packet loss, bandwidth, signal, router health, and failover state. Prometheus and Grafana provide an open and auditable monitoring foundation.

Service scope

  • Uptime, latency, jitter, and packet loss
  • Bandwidth and mobile signal
  • Router and failover state
  • Prometheus and Grafana
  • Dashboards, reports, and SLA evidence

Know before the site does

Latency, packet loss, and signal degrade measurably before a site notices anything. You act on measurements, before the first complaint arrives.

Auditable data

Dashboards and reports create a shared evidence base for the customer, Anexum, and carriers.

Clear ownership

Anexum coordinates manual carrier escalation within the agreed service scope.

What is the difference between monitoring and support?

Monitoring collects measurements and generates alerts. Support evaluates the incident, coordinates action, and escalates to the carrier. Response and availability are governed by the selected SLA.

What do customers see in the portal?

The portal can combine dashboards, reports, invoices, and offers, bringing technical and commercial information together.

Why test several external targets?

A single gateway test can miss faults beyond the local access circuit. Multiple targets help distinguish local, carrier, and wider internet problems.

Which alert thresholds are used?

Thresholds are not applied universally. The application, baseline, access type, region, and SLA determine which deviation matters and when an alert is generated.

How are false alerts reduced?

Multiple targets, time windows, retries, maintenance periods, and dependencies help distinguish measurement errors from real incidents. Changes are assessed against alert quality.

How are carrier tickets supported?

Measurements, timestamps, affected paths, router state, and comparison targets can provide evidence for manual escalation. Ticket creation follows the agreed support process.

How long is measurement data retained?

Retention and aggregation depend on the package, data volume, and contractual requirement. The exact period is documented rather than promised universally on this page.

Can existing monitoring be integrated?

Depending on interfaces, existing systems, Prometheus exporters, Grafana dashboards, SNMP, APIs, or webhooks can be integrated. Scope and ownership are agreed in advance.

Review your current contracts and connections

Define monitoring requirements