DNS response history for ns2.qmarksoft.com

ns2.qmarksoft.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-27. For this date, NameServerHistory found 36 DNS check records, 35 successful responses, 1 failed responses, and 1114 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.qmarksoft.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

1114 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:18

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.93.233.139

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.qmarksoft.com

Showing DNS history for 2026-08-27 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-27 11:18 639234253963286387
1203 ms 34.93.233.139
35 2026-08-27 11:01 639234243654907465
1812 ms 34.93.233.139
34 2026-08-27 10:44 639234233269654413
-
33 2026-08-27 10:26 639234222943951923
1199 ms 34.93.233.139
32 2026-08-27 10:09 639234212558002823
1224 ms 34.93.233.139
31 2026-08-27 09:52 639234202117531850
1212 ms 34.93.233.139
30 2026-08-27 09:34 639234191649612722
1203 ms 34.93.233.139
29 2026-08-27 09:17 639234181105879568
1190 ms 34.93.233.139
28 2026-08-27 08:59 639234170713214496
1208 ms 34.93.233.139
27 2026-08-27 08:42 639234160341037652
1211 ms 34.93.233.139
26 2026-08-27 08:25 639234149799404224
1218 ms 34.93.233.139
25 2026-08-27 08:07 639234139553286469
2315 ms 34.93.233.139
24 2026-08-27 07:14 639234107183588293
1211 ms 34.93.233.139
23 2026-08-27 06:56 639234096905435724
1215 ms 34.93.233.139
22 2026-08-27 06:39 639234086579410775
1207 ms 34.93.233.139
21 2026-08-27 06:22 639234076291157956
1207 ms 34.93.233.139
20 2026-08-27 06:05 639234065981939454
1215 ms 34.93.233.139
19 2026-08-27 05:48 639234055548642997
1558 ms 34.93.233.139
18 2026-08-27 05:30 639234045267979603
1204 ms 34.93.233.139
17 2026-08-27 05:13 639234034999717463
1204 ms 34.93.233.139
16 2026-08-27 04:56 639234024739225358
1795 ms 34.93.233.139
15 2026-08-27 04:39 639234014311170162
1181 ms 34.93.233.139
14 2026-08-27 04:21 639234003806017640
1210 ms 34.93.233.139
13 2026-08-27 04:04 639233993356203030
1191 ms 34.93.233.139
12 2026-08-27 03:10 639233961301716608
2 ms 34.93.233.139
11 2026-08-27 02:53 639233950834200647
7 ms 34.93.233.139
10 2026-08-27 02:36 639233940431849026
1193 ms 34.93.233.139
9 2026-08-27 02:18 639233930110596398
3 ms 34.93.233.139
8 2026-08-27 02:01 639233919705434540
1214 ms 34.93.233.139
7 2026-08-27 01:44 639233909452807845
6 ms 34.93.233.139
6 2026-08-27 01:27 639233899096420820
5 ms 34.93.233.139
5 2026-08-27 01:10 639233888707824939
1200 ms 34.93.233.139
4 2026-08-27 00:52 639233878461203802
1201 ms 34.93.233.139
3 2026-08-27 00:35 639233868060868209
1207 ms 34.93.233.139
2 2026-08-27 00:18 639233857450922991
1367 ms 34.93.233.139
1 2026-08-27 00:00 639233846871926285
1194 ms 34.93.233.139