ROUTING · UPSTREAM · NETWORK PATH

When the service slows down, follow the path.

Combine continuous service validation with network-path evidence to see whether degradation coincides with unusual routing, upstream changes or different network paths.

Don't stop at “the service is slow.” Find out what else changed.

See routing evidence in Degust Explore Degust

Degust analysis showing service degradation, affected targets, AI-assisted analysis and network route comparison.

REAL-WORLD EXAMPLE

Follow the evidence.

Degust observed higher RTT to ebay.de while customers reported: “ebay.de feels slow.”

Expected path

Observed path

Finding: The network path changed.

Service validation and routing evidence from the same time context make it possible to investigate whether unusual paths coincide with degraded service behaviour.

COMPARE NETWORK PATHS

One affected group is useful. A comparable normal group is stronger evidence.

Compare locations with the same relevant environment and different network paths.

AFFECTED GROUP

DEGRADED

RegionNorthern Germany

TechnologyDOCSIS

CPEFRITZ!Box

CarrierCarrier B

RouteRoute B

COMPARABLE NORMAL GROUP

NORMAL

RegionNorthern Germany

TechnologyDOCSIS

CPEFRITZ!Box

CarrierCarrier A

RouteRoute A

Same environment. Different route. Different validation result.

The comparison identifies evidence for further investigation without assigning cause.

NETWORK EVIDENCE

A route change is evidence — not automatically a root cause.

TracerouteObserve the path used during service validation.

Time contextCompare path changes with degradation in the same period.

Comparison groupsCheck whether comparable locations using another route remain normal.

Historical viewLook back at the network state during the reported incident.

Related insights

REAL PRODUCT

See service degradation and routing evidence together.

Degust brings service validation, AI-assisted analysis and path comparison into one operational view.

01Service degradation See when RTT or service behaviour changed.

02AI-assisted analysis Summarize relevant observations without inventing certainty.

03Route comparison Compare network paths from the same incident window.

ROUTING ANALYSIS QUESTIONS

Questions ISPs ask about routing and upstream evidence.

Network-path evidence narrows investigation without turning correlation into unsupported certainty.

How can an ISP determine whether slow Internet is related to routing?

Correlate service degradation with traceroute or path evidence from the same period, then compare affected locations with similar locations using other paths. The result can focus investigation without treating correlation as proof of cause.

How can traceroute data help explain service degradation?

Traceroute records the network path visible during validation. Changes in hops, geography or intermediate networks can provide evidence to compare with latency or service degradation.

How can an ISP compare affected and unaffected network paths?

Group locations by relevant context and compare affected results with a normal group. Differences in carrier or route can identify where further investigation should begin.

How can an ISP investigate whether degradation is related to an upstream provider?

Compare the same service across locations and upstream paths in the same time window. If degradation repeatedly coincides with one upstream path while comparable paths remain normal, the upstream deserves investigation, but the evidence does not by itself prove cause.

Does a changed route prove that the route caused the problem?

No. A route change is evidence and may correlate with degradation, but additional measurements and comparison are needed before assigning cause.

How can historical routing evidence help investigate a past incident?

Historical path and service results let operators examine the network state from the incident window instead of relying only on the current, recovered state.

How can service validation and network-path analysis be correlated in the same time context?

Record service results and supporting route evidence with aligned timestamps, then compare changes across the same incident window and affected population.

How can an ISP compare different carriers or upstream routes?

Use comparable validation locations and group results by carrier, route or other metadata while holding relevant environment characteristics as consistent as possible.

Can AI help summarize routing-related service incidents?

AI-assisted analysis can summarize anomalies, service results and route observations. It should preserve uncertainty and must not invent a root cause when the evidence is insufficient.

Know which path your customers were actually using.

Combine continuous service validation with routing evidence to focus investigation on the paths and providers that deserve attention.

See routing analysis in Degust Explore Broadband