DNS response history for echo2.core-dns.net

echo2.core-dns.net is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-26. For this date, NameServerHistory found 35 DNS check records, 34 successful responses, 1 failed responses, and 334 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for echo2.core-dns.net.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.102.46.201

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for echo2.core-dns.net

Showing DNS history for 2026-08-26 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
35 2026-08-26 11:44 639233414056832719
10 ms 199.102.46.201
34 2026-08-26 11:26 639233403515141099
8 ms 199.102.46.201
33 2026-08-26 10:32 639233370841350248
2034 ms 199.102.46.201
32 2026-08-26 10:14 639233360361507238
7 ms 199.102.46.201
31 2026-08-26 09:57 639233350067824371
12 ms 199.102.46.201
30 2026-08-26 09:39 639233339545274518
8 ms 199.102.46.201
29 2026-08-26 09:22 639233329214918079
38 ms 199.102.46.201
28 2026-08-26 09:05 639233318749762337
2039 ms 199.102.46.201
27 2026-08-26 08:47 639233308387917838
74 ms 199.102.46.201
26 2026-08-26 08:30 639233297961740122
49 ms 199.102.46.201
25 2026-08-26 08:13 639233287487159094
7 ms 199.102.46.201
24 2026-08-26 07:55 639233276995531707
14 ms 199.102.46.201
23 2026-08-26 07:38 639233266521568229
7 ms 199.102.46.201
22 2026-08-26 07:20 639233256081047431
520 ms 199.102.46.201
21 2026-08-26 06:26 639233223620132921
6 ms 199.102.46.201
20 2026-08-26 06:09 639233213287814244
9 ms 199.102.46.201
19 2026-08-26 05:52 639233202925983161
36 ms 199.102.46.201
18 2026-08-26 05:35 639233192644780696
5 ms 199.102.46.201
17 2026-08-26 05:17 639233182401183833
24 ms 199.102.46.201
16 2026-08-26 05:00 639233172074181051
12 ms 199.102.46.201
15 2026-08-26 04:43 639233161808421455
4022 ms 199.102.46.201
14 2026-08-26 04:26 639233151357344052
2024 ms 199.102.46.201
13 2026-08-26 04:09 639233141034116946
47 ms 199.102.46.201
12 2026-08-26 03:52 639233130828334142
-
11 2026-08-26 03:34 639233120373450007
55 ms 199.102.46.201
10 2026-08-26 03:17 639233110066216193
6 ms 199.102.46.201
9 2026-08-26 02:24 639233078065410564
31 ms 199.102.46.201
8 2026-08-26 02:06 639233067787457832
12 ms 199.102.46.201
7 2026-08-26 01:49 639233057501801162
16 ms 199.102.46.201
6 2026-08-26 01:32 639233047089431703
4 ms 199.102.46.201
5 2026-08-26 01:15 639233036754790688
44 ms 199.102.46.201
4 2026-08-26 00:57 639233026412602472
54 ms 199.102.46.201
3 2026-08-26 00:40 639233016064066127
31 ms 199.102.46.201
2 2026-08-26 00:23 639233005922655772
72 ms 199.102.46.201
1 2026-08-26 00:06 639232995672256907
33 ms 199.102.46.201