DNS response history for ns2.mkto-j0134.com

ns2.mkto-j0134.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 28 DNS check records, 28 successful responses, 0 failed responses, and 438 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-j0134.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

438 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

95.164.160.28

Most recently resolved hosting IP on selected date

Successful Responses

28

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-j0134.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
28 2026-08-25 09:41 639232471861770303
44 ms 95.164.160.28
27 2026-08-25 09:24 639232461630217327
2120 ms 95.164.160.28
26 2026-08-25 09:07 639232451282965990
40 ms 95.164.160.28
25 2026-08-25 08:50 639232440814614938
2194 ms 95.164.160.28
24 2026-08-25 08:32 639232430410720425
127 ms 95.164.160.28
23 2026-08-25 08:15 639232420003096185
2022 ms 95.164.160.28
22 2026-08-25 07:58 639232409467287444
8 ms 95.164.160.28
21 2026-08-25 07:40 639232399077195997
144 ms 95.164.160.28
20 2026-08-25 07:23 639232388731528337
24 ms 95.164.160.28
19 2026-08-25 07:05 639232378288598612
39 ms 95.164.160.28
18 2026-08-25 06:12 639232346196373643
46 ms 95.164.160.28
17 2026-08-25 05:55 639232336112370741
132 ms 95.164.160.28
16 2026-08-25 05:38 639232326146508970
35 ms 95.164.160.28
15 2026-08-25 05:22 639232316189381720
40 ms 95.164.160.28
14 2026-08-25 05:05 639232306217998913
57 ms 95.164.160.28
13 2026-08-25 04:49 639232296255744174
36 ms 95.164.160.28
12 2026-08-25 04:32 639232286095760789
32 ms 95.164.160.28
11 2026-08-25 04:15 639232276086186273
44 ms 95.164.160.28
10 2026-08-25 03:58 639232265900986425
4361 ms 95.164.160.28
9 2026-08-25 03:41 639232255723518075
144 ms 95.164.160.28
8 2026-08-25 03:24 639232245484452890
8 ms 95.164.160.28
7 2026-08-25 03:07 639232235157175331
150 ms 95.164.160.28
6 2026-08-25 02:14 639232203197189095
42 ms 95.164.160.28
5 2026-08-25 01:56 639232192844564298
9 ms 95.164.160.28
4 2026-08-25 01:39 639232182496008942
147 ms 95.164.160.28
3 2026-08-25 01:22 639232172197053132
128 ms 95.164.160.28
2 2026-08-25 00:28 639232140250307418
35 ms 95.164.160.28
1 2026-08-25 00:12 639232129927860324
49 ms 95.164.160.28