DNS response history for ns3.bitsoftweb.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

188 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

209.141.60.121

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 ns3.bitsoftweb.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
33 2026-08-25 11:33 639232535349285207
152 ms 209.141.60.121
32 2026-08-25 11:16 639232524938080723
8 ms 209.141.60.121
31 2026-08-25 10:22 639232492740373468
153 ms 209.141.60.121
30 2026-08-25 10:05 639232482235303141
302 ms 209.141.60.121
29 2026-08-25 09:47 639232471861770303
152 ms 209.141.60.121
28 2026-08-25 09:30 639232461630217327
322 ms 209.141.60.121
27 2026-08-25 09:13 639232451282965990
157 ms 209.141.60.121
26 2026-08-25 08:56 639232440814614938
151 ms 209.141.60.121
25 2026-08-25 08:38 639232430410720425
155 ms 209.141.60.121
24 2026-08-25 08:21 639232420003096185
302 ms 209.141.60.121
23 2026-08-25 08:04 639232409467287444
164 ms 209.141.60.121
22 2026-08-25 07:46 639232399077195997
150 ms 209.141.60.121
21 2026-08-25 07:29 639232388731528337
304 ms 209.141.60.121
20 2026-08-25 07:12 639232378288598612
312 ms 209.141.60.121
19 2026-08-25 06:18 639232346196373643
151 ms 209.141.60.121
18 2026-08-25 06:01 639232336112370741
153 ms 209.141.60.121
17 2026-08-25 05:44 639232326146508970
300 ms 209.141.60.121
16 2026-08-25 05:28 639232316189381720
3 ms 209.141.60.121
15 2026-08-25 05:11 639232306217998913
4 ms 209.141.60.121
14 2026-08-25 04:54 639232296255744174
300 ms 209.141.60.121
13 2026-08-25 04:38 639232286095760789
297 ms 209.141.60.121
12 2026-08-25 04:21 639232276086186273
149 ms 209.141.60.121
11 2026-08-25 04:04 639232265900986425
7 ms 209.141.60.121
10 2026-08-25 03:47 639232255723518075
156 ms 209.141.60.121
9 2026-08-25 03:30 639232245484452890
183 ms 209.141.60.121
8 2026-08-25 03:13 639232235157175331
152 ms 209.141.60.121
7 2026-08-25 02:19 639232203197189095
3 ms 209.141.60.121
6 2026-08-25 02:03 639232192844564298
321 ms 209.141.60.121
5 2026-08-25 01:45 639232182496008942
310 ms 209.141.60.121
4 2026-08-25 01:28 639232172197053132
302 ms 209.141.60.121
3 2026-08-25 00:34 639232140250307418
299 ms 209.141.60.121
2 2026-08-25 00:18 639232129927860324
152 ms 209.141.60.121
1 2026-08-25 00:00 639232119551972438
163 ms 209.141.60.121