DNS response history for ns2.yescall.com

ns2.yescall.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 33 DNS check records, 33 successful responses, 0 failed responses, and 708 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 ns2.yescall.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

708 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.108.182.4

Most recently resolved hosting IP on selected date

Successful Responses

33

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 ns2.yescall.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
33 2026-08-25 11:34 639232535349285207
4 ms 210.108.182.4
32 2026-08-25 11:16 639232524938080723
1199 ms 210.108.182.4
31 2026-08-25 10:22 639232492740373468
4 ms 210.108.182.4
30 2026-08-25 10:05 639232482235303141
1153 ms 210.108.182.4
29 2026-08-25 09:48 639232471861770303
1171 ms 210.108.182.4
28 2026-08-25 09:31 639232461630217327
1188 ms 210.108.182.4
27 2026-08-25 09:13 639232451282965990
1174 ms 210.108.182.4
26 2026-08-25 08:56 639232440814614938
1180 ms 210.108.182.4
25 2026-08-25 08:39 639232430410720425
1146 ms 210.108.182.4
24 2026-08-25 08:21 639232420003096185
1163 ms 210.108.182.4
23 2026-08-25 08:04 639232409467287444
2 ms 210.108.182.4
22 2026-08-25 07:47 639232399077195997
3 ms 210.108.182.4
21 2026-08-25 07:29 639232388731528337
1151 ms 210.108.182.4
20 2026-08-25 07:12 639232378288598612
3 ms 210.108.182.4
19 2026-08-25 06:18 639232346196373643
1174 ms 210.108.182.4
18 2026-08-25 06:01 639232336112370741
1176 ms 210.108.182.4
17 2026-08-25 05:44 639232326146508970
3 ms 210.108.182.4
16 2026-08-25 05:28 639232316189381720
3 ms 210.108.182.4
15 2026-08-25 05:11 639232306217998913
3 ms 210.108.182.4
14 2026-08-25 04:55 639232296255744174
2 ms 210.108.182.4
13 2026-08-25 04:38 639232286095760789
1171 ms 210.108.182.4
12 2026-08-25 04:21 639232276086186273
1150 ms 210.108.182.4
11 2026-08-25 04:04 639232265900986425
4 ms 210.108.182.4
10 2026-08-25 03:47 639232255723518075
1167 ms 210.108.182.4
9 2026-08-25 03:30 639232245484452890
1160 ms 210.108.182.4
8 2026-08-25 03:13 639232235157175331
3 ms 210.108.182.4
7 2026-08-25 02:20 639232203197189095
2 ms 210.108.182.4
6 2026-08-25 02:03 639232192844564298
1155 ms 210.108.182.4
5 2026-08-25 01:45 639232182496008942
1184 ms 210.108.182.4
4 2026-08-25 01:28 639232172197053132
3 ms 210.108.182.4
3 2026-08-25 00:35 639232140250307418
1162 ms 210.108.182.4
2 2026-08-25 00:18 639232129927860324
1160 ms 210.108.182.4
1 2026-08-25 00:01 639232119551972438
1152 ms 210.108.182.4