Glossary
Transport Error
A failure below HTTP: the request never produced a complete response.
Definition
A transport error is a probe failure that occurs before an HTTP status could be exchanged - DNS resolution failure, TCP refusal or reset, TLS handshake failure, or a timeout past the probe deadline. It is categorically different from receiving a 4xx or 5xx status.
The problem
Monitoring that collapses “no response” and “server returned 500” into one red dot destroys the distinction between an unreachable service and a reachable-but-failing one - two incidents with different owners, symptoms and fixes.
Why it matters
Transport errors localize: persistent failures from one origin but not another suggest a path or edge problem; failures from every origin suggest the target; timeouts under load can precede outright refusal and mark a degradation arc.
Practical example
RELIASTRA stores each observation with its outcome: status code and latency when a response arrived; an explicit error type when it did not. Availability counts “no expected response,” so the taxonomy stays visible in every aggregate.
How RELIASTRA approaches it
Probes run under a fixed deadline (15 seconds on public records) with bounded redirect handling, and the security policy can refuse a target before any request leaves - recorded as a policy block, a RELIASTRA-side fact, never as vendor downtime.
Know what you depend on. Prove what it did.
RELIASTRA observes the external services your product relies on, attributes their failures, and produces evidence you can act on. Every new organization starts on a 14-day Pro trial.