DNS response history for ns2.servimoney.com

ns2.servimoney.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 33 DNS check records, 33 successful responses, 0 failed responses, and 191 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.servimoney.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

191 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

192.168.1.100

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.servimoney.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
33 2026-08-26 10:34 639233370841350248
73 ms 192.168.1.100
32 2026-08-26 10:17 639233360361507238
31 ms 192.168.1.100
31 2026-08-26 10:00 639233350067824371
78 ms 192.168.1.100
30 2026-08-26 09:42 639233339545274518
2067 ms 192.168.1.100
29 2026-08-26 09:25 639233329214918079
170 ms 192.168.1.100
28 2026-08-26 09:07 639233318749762337
45 ms 192.168.1.100
27 2026-08-26 08:50 639233308387917838
55 ms 192.168.1.100
26 2026-08-26 08:33 639233297961740122
47 ms 192.168.1.100
25 2026-08-26 08:15 639233287487159094
47 ms 192.168.1.100
24 2026-08-26 07:58 639233276995531707
43 ms 192.168.1.100
23 2026-08-26 07:40 639233266521568229
8 ms 192.168.1.100
22 2026-08-26 07:23 639233256081047431
48 ms 192.168.1.100
21 2026-08-26 06:29 639233223620132921
49 ms 192.168.1.100
20 2026-08-26 06:12 639233213287814244
140 ms 192.168.1.100
19 2026-08-26 05:54 639233202925983161
41 ms 192.168.1.100
18 2026-08-26 05:37 639233192644780696
43 ms 192.168.1.100
17 2026-08-26 05:20 639233182401183833
53 ms 192.168.1.100
16 2026-08-26 05:03 639233172074181051
56 ms 192.168.1.100
15 2026-08-26 04:46 639233161808421455
62 ms 192.168.1.100
14 2026-08-26 04:28 639233151357344052
165 ms 192.168.1.100
13 2026-08-26 04:11 639233141034116946
2046 ms 192.168.1.100
12 2026-08-26 03:54 639233130828334142
181 ms 192.168.1.100
11 2026-08-26 03:37 639233120373450007
56 ms 192.168.1.100
10 2026-08-26 03:20 639233110066216193
46 ms 192.168.1.100
9 2026-08-26 02:26 639233078065410564
136 ms 192.168.1.100
8 2026-08-26 02:09 639233067787457832
143 ms 192.168.1.100
7 2026-08-26 01:52 639233057501801162
75 ms 192.168.1.100
6 2026-08-26 01:35 639233047089431703
56 ms 192.168.1.100
5 2026-08-26 01:17 639233036754790688
47 ms 192.168.1.100
4 2026-08-26 01:00 639233026412602472
46 ms 192.168.1.100
3 2026-08-26 00:43 639233016064066127
42 ms 192.168.1.100
2 2026-08-26 00:26 639233005922655772
41 ms 192.168.1.100
1 2026-08-26 00:09 639232995672256907
66 ms 192.168.1.100