DNS response history for ns2.targetmy.com

ns2.targetmy.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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 108 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.targetmy.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

108 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 07:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

76.223.54.146

Most recently resolved hosting IP on selected date

Successful Responses

36

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.targetmy.com

Showing DNS history for 2026-08-24 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
36 2026-08-24 07:09 639231518076817246
9 ms 76.223.54.146
35 2026-08-24 07:09 639231518076817246
9 ms 13.248.169.48
34 2026-08-24 06:52 639231508078650885
218 ms 13.248.169.48
33 2026-08-24 06:52 639231508078650885
218 ms 76.223.54.146
32 2026-08-24 06:35 639231498210697093
153 ms 13.248.169.48
31 2026-08-24 06:35 639231498210697093
153 ms 76.223.54.146
30 2026-08-24 06:19 639231488109699360
334 ms 13.248.169.48
29 2026-08-24 06:19 639231488109699360
334 ms 76.223.54.146
28 2026-08-24 05:26 639231456772510692
149 ms 76.223.54.146
27 2026-08-24 05:26 639231456772510692
149 ms 13.248.169.48
26 2026-08-24 05:10 639231447084631185
53 ms 13.248.169.48
25 2026-08-24 05:10 639231447084631185
53 ms 76.223.54.146
24 2026-08-24 04:54 639231437208519473
40 ms 13.248.169.48
23 2026-08-24 04:54 639231437208519473
40 ms 76.223.54.146
22 2026-08-24 04:37 639231427209627490
44 ms 13.248.169.48
21 2026-08-24 04:37 639231427209627490
44 ms 76.223.54.146
20 2026-08-24 03:45 639231395791246644
6 ms 76.223.54.146
19 2026-08-24 03:45 639231395791246644
6 ms 13.248.169.48
18 2026-08-24 03:29 639231386075551458
29 ms 76.223.54.146
17 2026-08-24 03:29 639231386075551458
29 ms 13.248.169.48
16 2026-08-24 03:12 639231376208713791
33 ms 13.248.169.48
15 2026-08-24 03:12 639231376208713791
33 ms 76.223.54.146
14 2026-08-24 02:55 639231366170589276
93 ms 13.248.169.48
13 2026-08-24 02:55 639231366170589276
93 ms 76.223.54.146
12 2026-08-24 02:03 639231334732159368
38 ms 13.248.169.48
11 2026-08-24 02:03 639231334732159368
38 ms 76.223.54.146
10 2026-08-24 01:47 639231325035670078
9 ms 13.248.169.48
9 2026-08-24 01:47 639231325035670078
9 ms 76.223.54.146
8 2026-08-24 01:30 639231315132253837
46 ms 76.223.54.146
7 2026-08-24 01:30 639231315132253837
46 ms 13.248.169.48
6 2026-08-24 01:13 639231305014280808
140 ms 13.248.169.48
5 2026-08-24 01:13 639231305014280808
140 ms 76.223.54.146
4 2026-08-24 00:21 639231273779380675
279 ms 76.223.54.146
3 2026-08-24 00:21 639231273779380675
279 ms 13.248.169.48
2 2026-08-24 00:05 639231264180839154
271 ms 76.223.54.146
1 2026-08-24 00:05 639231264180839154
271 ms 13.248.169.48