DNS response history for ns2.svrmx.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

152 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.241.142.94

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.svrmx.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
36 2026-08-26 12:02 639233424567558554
26 ms 162.241.142.94
35 2026-08-26 11:45 639233414056832719
37 ms 162.241.142.94
34 2026-08-26 11:27 639233403515141099
50 ms 162.241.142.94
33 2026-08-26 10:33 639233370841350248
37 ms 162.241.142.94
32 2026-08-26 10:15 639233360361507238
35 ms 162.241.142.94
31 2026-08-26 09:58 639233350067824371
105 ms 162.241.142.94
30 2026-08-26 09:41 639233339545274518
50 ms 162.241.142.94
29 2026-08-26 09:23 639233329214918079
61 ms 162.241.142.94
28 2026-08-26 09:06 639233318749762337
43 ms 162.241.142.94
27 2026-08-26 08:49 639233308387917838
2030 ms 162.241.142.94
26 2026-08-26 08:31 639233297961740122
16 ms 162.241.142.94
25 2026-08-26 08:14 639233287487159094
18 ms 162.241.142.94
24 2026-08-26 07:56 639233276995531707
42 ms 162.241.142.94
23 2026-08-26 07:39 639233266521568229
47 ms 162.241.142.94
22 2026-08-26 07:22 639233256081047431
20 ms 162.241.142.94
21 2026-08-26 06:27 639233223620132921
2073 ms 162.241.142.94
20 2026-08-26 06:10 639233213287814244
38 ms 162.241.142.94
19 2026-08-26 05:53 639233202925983161
13 ms 162.241.142.94
18 2026-08-26 05:36 639233192644780696
59 ms 162.241.142.94
17 2026-08-26 05:19 639233182401183833
12 ms 162.241.142.94
16 2026-08-26 05:02 639233172074181051
86 ms 162.241.142.94
15 2026-08-26 04:44 639233161808421455
31 ms 162.241.142.94
14 2026-08-26 04:27 639233151357344052
46 ms 162.241.142.94
13 2026-08-26 04:10 639233141034116946
69 ms 162.241.142.94
12 2026-08-26 03:53 639233130828334142
50 ms 162.241.142.94
11 2026-08-26 03:35 639233120373450007
109 ms 162.241.142.94
10 2026-08-26 03:18 639233110066216193
26 ms 162.241.142.94
9 2026-08-26 02:25 639233078065410564
49 ms 162.241.142.94
8 2026-08-26 02:08 639233067787457832
18 ms 162.241.142.94
7 2026-08-26 01:51 639233057501801162
40 ms 162.241.142.94
6 2026-08-26 01:33 639233047089431703
39 ms 162.241.142.94
5 2026-08-26 01:16 639233036754790688
10 ms 162.241.142.94
4 2026-08-26 00:59 639233026412602472
17 ms 162.241.142.94
3 2026-08-26 00:41 639233016064066127
36 ms 162.241.142.94
2 2026-08-26 00:25 639233005922655772
23 ms 162.241.142.94
1 2026-08-26 00:07 639232995672256907
28 ms 162.241.142.94