MICRO-OUTAGES · INTERMITTENT CONNECTIVITY
A two-second outage can disappear before your investigation even starts.
Continuously validate service availability and responsiveness so short interruptions, latency spikes and intermittent degradation remain visible after the network appears normal again.
If customers can notice it, your validation should be able to record it.

SHORT DOES NOT MEAN IRRELEVANT
A brief degradation across 6% of your customers is still a network event.
437 of 8,000 validation locations
≈ 5.5%
WHAT SHORT INCIDENTS LOOK LIKE
Intermittent problems leave different traces.
Related insights
CAPTURE THE INCIDENT
Validate frequently enough to preserve what the customer experienced.
OBSERVE
Run continuous or scheduled validations from distributed locations.
DETECT
Identify short changes in reachability, latency or service outcome.
CORRELATE
Compare affected locations and supporting network evidence from the same time.
REVIEW
Look back at the incident after the network has returned to normal.
ONE CUSTOMER OR MANY?
Find out whether the interruption was isolated or shared.
AFFECTED
DEGRADEDCOMPARISON
NORMALShort incidents become operationally useful when affected locations can be compared with similar locations that remained normal.
REAL PRODUCT
Keep the incident visible after it has disappeared.
HISTORICAL INVESTIGATION
Go back to the moment the customer noticed the problem.
Finding: investigation should use the network and service evidence from the incident window, not only the current state.
Degust retains validation results so operators can inspect what distributed locations experienced during a previous incident. Retention duration depends on the applicable subscription and configuration.
MICRO-OUTAGE QUESTIONS