DNS response history for dns2.nitroserv.com

dns2.nitroserv.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-26. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 283 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 dns2.nitroserv.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

283 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

109.239.159.110

Most recently resolved hosting IP on selected date

Successful Responses

32

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 dns2.nitroserv.com

Showing DNS history for 2026-08-26 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
32 2026-08-26 10:14 639233360361507238
2042 ms 109.239.159.110
31 2026-08-26 09:57 639233350067824371
46 ms 109.239.159.110
30 2026-08-26 09:39 639233339545274518
15 ms 109.239.159.110
29 2026-08-26 09:22 639233329214918079
16 ms 109.239.159.110
28 2026-08-26 09:05 639233318749762337
50 ms 109.239.159.110
27 2026-08-26 08:47 639233308387917838
120 ms 109.239.159.110
26 2026-08-26 08:30 639233297961740122
25 ms 109.239.159.110
25 2026-08-26 08:13 639233287487159094
37 ms 109.239.159.110
24 2026-08-26 07:55 639233276995531707
2041 ms 109.239.159.110
23 2026-08-26 07:38 639233266521568229
18 ms 109.239.159.110
22 2026-08-26 07:20 639233256081047431
2043 ms 109.239.159.110
21 2026-08-26 06:26 639233223620132921
18 ms 109.239.159.110
20 2026-08-26 06:09 639233213287814244
18 ms 109.239.159.110
19 2026-08-26 05:52 639233202925983161
118 ms 109.239.159.110
18 2026-08-26 05:34 639233192644780696
11 ms 109.239.159.110
17 2026-08-26 05:17 639233182401183833
41 ms 109.239.159.110
16 2026-08-26 05:00 639233172074181051
4 ms 109.239.159.110
15 2026-08-26 04:43 639233161808421455
28 ms 109.239.159.110
14 2026-08-26 04:26 639233151357344052
9 ms 109.239.159.110
13 2026-08-26 04:08 639233141034116946
2093 ms 109.239.159.110
12 2026-08-26 03:51 639233130828334142
48 ms 109.239.159.110
11 2026-08-26 03:34 639233120373450007
35 ms 109.239.159.110
10 2026-08-26 03:17 639233110066216193
9 ms 109.239.159.110
9 2026-08-26 02:23 639233078065410564
15 ms 109.239.159.110
8 2026-08-26 02:06 639233067787457832
32 ms 109.239.159.110
7 2026-08-26 01:49 639233057501801162
5 ms 109.239.159.110
6 2026-08-26 01:32 639233047089431703
7 ms 109.239.159.110
5 2026-08-26 01:15 639233036754790688
37 ms 109.239.159.110
4 2026-08-26 00:57 639233026412602472
24 ms 109.239.159.110
3 2026-08-26 00:40 639233016064066127
10 ms 109.239.159.110
2 2026-08-26 00:23 639233005922655772
37 ms 109.239.159.110
1 2026-08-26 00:06 639232995672256907
9 ms 109.239.159.110