DNS response history for ns2.mkto-sj050032.com

ns2.mkto-sj050032.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 246 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.mkto-sj050032.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.164.160.5

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.mkto-sj050032.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:49 639232545839529039
71 ms 95.164.160.5
32 2026-08-25 11:32 639232535349285207
166 ms 95.164.160.5
31 2026-08-25 11:14 639232524938080723
171 ms 95.164.160.5
30 2026-08-25 10:20 639232492740373468
166 ms 95.164.160.5
29 2026-08-25 10:03 639232482235303141
162 ms 95.164.160.5
28 2026-08-25 09:46 639232471861770303
160 ms 95.164.160.5
27 2026-08-25 09:29 639232461630217327
164 ms 95.164.160.5
26 2026-08-25 09:11 639232451282965990
105 ms 95.164.160.5
25 2026-08-25 08:54 639232440814614938
163 ms 95.164.160.5
24 2026-08-25 08:37 639232430410720425
168 ms 95.164.160.5
23 2026-08-25 08:19 639232420003096185
558 ms 95.164.160.5
22 2026-08-25 08:02 639232409467287444
187 ms 95.164.160.5
21 2026-08-25 07:45 639232399077195997
153 ms 95.164.160.5
20 2026-08-25 07:27 639232388731528337
237 ms 95.164.160.5
19 2026-08-25 07:10 639232378288598612
96 ms 95.164.160.5
18 2026-08-25 06:16 639232346196373643
151 ms 95.164.160.5
17 2026-08-25 05:59 639232336112370741
147 ms 95.164.160.5
16 2026-08-25 05:43 639232326146508970
3 ms 95.164.160.5
15 2026-08-25 05:26 639232316189381720
527 ms 95.164.160.5
14 2026-08-25 05:09 639232306217998913
147 ms 95.164.160.5
13 2026-08-25 04:53 639232296255744174
98 ms 95.164.160.5
12 2026-08-25 04:36 639232286095760789
155 ms 95.164.160.5
11 2026-08-25 04:19 639232276086186273
2180 ms 95.164.160.5
10 2026-08-25 04:02 639232265900986425
145 ms 95.164.160.5
9 2026-08-25 03:45 639232255723518075
244 ms 95.164.160.5
8 2026-08-25 03:28 639232245484452890
94 ms 95.164.160.5
7 2026-08-25 03:11 639232235157175331
183 ms 95.164.160.5
6 2026-08-25 02:18 639232203197189095
520 ms 95.164.160.5
5 2026-08-25 02:01 639232192844564298
159 ms 95.164.160.5
4 2026-08-25 01:43 639232182496008942
149 ms 95.164.160.5
3 2026-08-25 01:26 639232172197053132
152 ms 95.164.160.5
2 2026-08-25 00:33 639232140250307418
186 ms 95.164.160.5
1 2026-08-25 00:16 639232129927860324
161 ms 95.164.160.5