DNS response history for ns3.bizserve.com

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

37

Historical checks stored for this nameserver on selected date

Average Latency

222 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

72.13.7.137

Most recently resolved hosting IP on selected date

Successful Responses

37

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.bizserve.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
37 2026-08-25 12:52 639232587225721862
8 ms 72.13.7.137
36 2026-08-25 12:35 639232576780683689
245 ms 72.13.7.137
35 2026-08-25 12:18 639232566381512620
238 ms 72.13.7.137
34 2026-08-25 12:00 639232556111768563
237 ms 72.13.7.137
33 2026-08-25 11:43 639232545839529039
245 ms 72.13.7.137
32 2026-08-25 11:26 639232535349285207
134 ms 72.13.7.137
31 2026-08-25 11:08 639232524938080723
137 ms 72.13.7.137
30 2026-08-25 10:15 639232492740373468
232 ms 72.13.7.137
29 2026-08-25 09:57 639232482235303141
235 ms 72.13.7.137
28 2026-08-25 09:40 639232471861770303
136 ms 72.13.7.137
27 2026-08-25 09:23 639232461630217327
141 ms 72.13.7.137
26 2026-08-25 09:06 639232451282965990
121 ms 72.13.7.137
25 2026-08-25 08:48 639232440814614938
265 ms 72.13.7.137
24 2026-08-25 08:31 639232430410720425
116 ms 72.13.7.137
23 2026-08-25 08:14 639232420003096185
250 ms 72.13.7.137
22 2026-08-25 07:56 639232409467287444
212 ms 72.13.7.137
21 2026-08-25 07:39 639232399077195997
238 ms 72.13.7.137
20 2026-08-25 07:21 639232388731528337
228 ms 72.13.7.137
19 2026-08-25 07:04 639232378288598612
242 ms 72.13.7.137
18 2026-08-25 06:11 639232346196373643
138 ms 72.13.7.137
17 2026-08-25 05:54 639232336112370741
14 ms 72.13.7.137
16 2026-08-25 05:37 639232326146508970
131 ms 72.13.7.137
15 2026-08-25 05:20 639232316189381720
231 ms 72.13.7.137
14 2026-08-25 05:04 639232306217998913
1662 ms 72.13.7.137
13 2026-08-25 04:47 639232296255744174
233 ms 72.13.7.137
12 2026-08-25 04:30 639232286095760789
119 ms 72.13.7.137
11 2026-08-25 04:14 639232276086186273
235 ms 72.13.7.137
10 2026-08-25 03:57 639232265900986425
135 ms 72.13.7.137
9 2026-08-25 03:40 639232255723518075
228 ms 72.13.7.137
8 2026-08-25 03:23 639232245484452890
21 ms 72.13.7.137
7 2026-08-25 03:06 639232235157175331
123 ms 72.13.7.137
6 2026-08-25 02:12 639232203197189095
226 ms 72.13.7.137
5 2026-08-25 01:55 639232192844564298
226 ms 72.13.7.137
4 2026-08-25 01:38 639232182496008942
150 ms 72.13.7.137
3 2026-08-25 01:20 639232172197053132
234 ms 72.13.7.137
2 2026-08-25 00:27 639232140250307418
229 ms 72.13.7.137
1 2026-08-25 00:10 639232129927860324
223 ms 72.13.7.137