DNS response history for ns2.troy-oz.com

ns2.troy-oz.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 663 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.troy-oz.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

663 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

153.122.10.133

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.troy-oz.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:30 639232461630217327
275 ms 153.122.10.133
27 2026-08-25 09:13 639232451282965990
258 ms 153.122.10.133
26 2026-08-25 08:56 639232440814614938
266 ms 153.122.10.133
25 2026-08-25 08:39 639232430410720425
257 ms 153.122.10.133
24 2026-08-25 08:21 639232420003096185
1073 ms 153.122.10.133
23 2026-08-25 08:04 639232409467287444
255 ms 153.122.10.133
22 2026-08-25 07:46 639232399077195997
1056 ms 153.122.10.133
21 2026-08-25 07:29 639232388731528337
1074 ms 153.122.10.133
20 2026-08-25 07:12 639232378288598612
1097 ms 153.122.10.133
19 2026-08-25 06:18 639232346196373643
1040 ms 153.122.10.133
18 2026-08-25 06:01 639232336112370741
2 ms 153.122.10.133
17 2026-08-25 05:44 639232326146508970
3 ms 153.122.10.133
16 2026-08-25 05:28 639232316189381720
3 ms 153.122.10.133
15 2026-08-25 05:11 639232306217998913
1091 ms 153.122.10.133
14 2026-08-25 04:55 639232296255744174
1106 ms 153.122.10.133
13 2026-08-25 04:38 639232286095760789
1069 ms 153.122.10.133
12 2026-08-25 04:21 639232276086186273
8 ms 153.122.10.133
11 2026-08-25 04:04 639232265900986425
1074 ms 153.122.10.133
10 2026-08-25 03:47 639232255723518075
3 ms 153.122.10.133
9 2026-08-25 03:30 639232245484452890
1063 ms 153.122.10.133
8 2026-08-25 03:13 639232235157175331
3 ms 153.122.10.133
7 2026-08-25 02:20 639232203197189095
1080 ms 153.122.10.133
6 2026-08-25 02:03 639232192844564298
1088 ms 153.122.10.133
5 2026-08-25 01:45 639232182496008942
1029 ms 153.122.10.133
4 2026-08-25 01:28 639232172197053132
1120 ms 153.122.10.133
3 2026-08-25 00:35 639232140250307418
1073 ms 153.122.10.133
2 2026-08-25 00:18 639232129927860324
4 ms 153.122.10.133
1 2026-08-25 00:00 639232119551972438
1082 ms 153.122.10.133