Core Assurance Failure Codes

Core Assurance is currently in beta. Features may change, documentation may be out of date, and performance may be inconsistent. Use at your own discretion.

When a run fails, the Test Results page shows the reason in the Error Detail column, and the Test Details page shows the reason in the Error column. Each reason corresponds to one of the failure codes in the following sections. Some codes apply only when you set the related optional value in the test profile, such as Max Response Time (ms).

To see the codes for a test type while you create or edit a test profile, click Show Possible Failure Codes on the Pass Criteria tab.

Failure codes for more than one test type

The following codes can occur for more than one test type.

Failure code

When it occurs

TEST_ALREADY_ACTIVE

The same test was already running on the endpoint when the next run was due. Applies to every test type.

CONCURRENT_LIMIT_EXCEEDED

The endpoint was already running the maximum number of tests allowed at the same time. Applies to every test type.

DNS_LOOKUP_FAILED

The target host name could not be resolved to an IP address. Applies to every test type except DNS Lookup.

Ping failure codes

For the fields and pass criteria of a Ping test, see Ping Tests.

Failure code

When it occurs

HOST_UNREACHABLE

The network reports that the destination is unreachable.

TEST_TIMED_OUT

No ICMP reply arrived before the timeout.

MAX_RTT_EXCEEDED

The round-trip time was longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value.

TCP Port failure codes

For the fields and pass criteria of a TCP Port test, see TCP Port Tests.

Failure code

When it occurs

HOST_UNREACHABLE

The network is unreachable, or there is no route to the host.

PORT_UNREACHABLE

The host refused the connection because nothing is listening on the port.

CONNECT_TIMED_OUT

The TCP connection did not complete within the timeout.

CONNECT_FAILED

Another connection error occurred. For example, a firewall dropped the connection without a response.

MAX_CONNECT_TIME_EXCEEDED

The connection succeeded but took longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value.

HTTP URL failure codes

For the fields and pass criteria of an HTTP URL test, see HTTP URL Tests.

Failure code

When it occurs

CONNECT_FAILED

The TCP connection failed because it was refused, the host was unreachable, or the connection timed out.

TLS_FAILED

The TLS (Transport Layer Security) handshake failed, or the server certificate is not valid.

TEST_TIMED_OUT

A complete response did not arrive within the timeout.

HTTP_STATUS_MISMATCH

The status code did not match Expected Status Code. For example, the server returned 503 when the profile expects 200 to 299.

TOO_MANY_REDIRECTS

The server sent the request through more redirects than the test allows. The redirect limit is fixed and cannot be changed in the profile.

HTTP_PROTOCOL_ERROR

An HTTP/2 framing or protocol error occurred.

CONNECTION_RESET

The connection dropped during the request or the response.

MAX_RESPONSE_TIME_EXCEEDED

The response took longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value.

DNS Lookup failure codes

For the fields and pass criteria of a DNS Lookup test, see DNS Lookup Tests.

Failure code

When it occurs

DNS_SERVER_UNRESPONSIVE

The DNS server did not respond within the timeout.

NAME_NOT_FOUND

The domain name does not exist.

NO_RECORDS_RETURNED

The query succeeded, but no records of the requested type were returned.

QUERY_TIMED_OUT

No response arrived before the query timeout.

EXPECTED_IP_MISMATCH

Records were returned, but the records do not satisfy the comparison with Expected Resolved IPs (optional).

SERVFAIL

The DNS server returned a server failure.

REFUSED

The DNS server refused the query, usually because of a policy or access list.

Traceroute failure codes

For the fields and pass criteria of a traceroute test, see Traceroute Tests.

Both traceroute types share the following codes. The last two codes in the table apply only to Traceroute TCP.

Failure code

When it occurs

PATH_DISCOVERY_FAILED

No hops were discovered, and the target was not reached.

MAX_HOPS_EXCEEDED

The test reached Max Hops without confirming the target.

GAP_LIMIT_EXCEEDED

More hops in a row were silent than Hop Gap Limit allows, so the test stopped.

TEST_TIMED_OUT

The whole run took longer than Path Timeout (ms).

MAX_E2E_RTT_EXCEEDED

The target was reached, but the end-to-end round-trip time was longer than the Max Response Time (ms) set in the profile. The code applies only when Max Response Time (ms) has a value.

PORT_CLOSED

Traceroute TCP only. The target reported that the port is unreachable, but the profile requires the port to be open.

TARGET_SILENT

Traceroute TCP only. The target sent no response at all, and Requires Target Reached is set to Yes.