DNS response history for ns1.resolutioncall.com

ns1.resolutioncall.com 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-25. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 239 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 ns1.resolutioncall.com.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

239 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.210.80.131

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.resolutioncall.com

Showing DNS history for 2026-08-25 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
31 2026-08-25 11:04 639232524938080723
35 ms 62.210.80.131
30 2026-08-25 10:11 639232492740373468
38 ms 62.210.80.131
29 2026-08-25 09:53 639232482235303141
65 ms 62.210.80.131
28 2026-08-25 09:36 639232471861770303
50 ms 62.210.80.131
27 2026-08-25 09:19 639232461630217327
35 ms 62.210.80.131
26 2026-08-25 09:02 639232451282965990
2028 ms 62.210.80.131
25 2026-08-25 08:44 639232440814614938
27 ms 62.210.80.131
24 2026-08-25 08:27 639232430410720425
2046 ms 62.210.80.131
23 2026-08-25 08:09 639232420003096185
57 ms 62.210.80.131
22 2026-08-25 07:52 639232409467287444
59 ms 62.210.80.131
21 2026-08-25 07:35 639232399077195997
77 ms 62.210.80.131
20 2026-08-25 07:17 639232388731528337
38 ms 62.210.80.131
19 2026-08-25 07:00 639232378288598612
69 ms 62.210.80.131
18 2026-08-25 06:06 639232346196373643
59 ms 62.210.80.131
17 2026-08-25 05:50 639232336112370741
2039 ms 62.210.80.131
16 2026-08-25 05:33 639232326146508970
51 ms 62.210.80.131
15 2026-08-25 05:16 639232316189381720
38 ms 62.210.80.131
14 2026-08-25 05:00 639232306217998913
17 ms 62.210.80.131
13 2026-08-25 04:43 639232296255744174
62 ms 62.210.80.131
12 2026-08-25 04:26 639232286095760789
48 ms 62.210.80.131
11 2026-08-25 04:09 639232276086186273
23 ms 62.210.80.131
10 2026-08-25 03:53 639232265900986425
55 ms 62.210.80.131
9 2026-08-25 03:36 639232255723518075
30 ms 62.210.80.131
8 2026-08-25 03:19 639232245484452890
33 ms 62.210.80.131
7 2026-08-25 03:01 639232235157175331
38 ms 62.210.80.131
6 2026-08-25 02:08 639232203197189095
135 ms 62.210.80.131
5 2026-08-25 01:51 639232192844564298
49 ms 62.210.80.131
4 2026-08-25 01:34 639232182496008942
10 ms 62.210.80.131
3 2026-08-25 01:16 639232172197053132
35 ms 62.210.80.131
2 2026-08-25 00:23 639232140250307418
32 ms 62.210.80.131
1 2026-08-25 00:06 639232129927860324
30 ms 62.210.80.131