DNS response history for ns2.b4comtech.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

250 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

79.143.25.97

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.b4comtech.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
33 2026-08-27 10:35 639234233269654413
115 ms 79.143.25.97
32 2026-08-27 10:18 639234222943951923
123 ms 79.143.25.97
31 2026-08-27 10:00 639234212558002823
75 ms 79.143.25.97
30 2026-08-27 09:43 639234202117531850
137 ms 79.143.25.97
29 2026-08-27 09:26 639234191649612722
2053 ms 79.143.25.97
28 2026-08-27 09:08 639234181105879568
126 ms 79.143.25.97
27 2026-08-27 08:51 639234170713214496
129 ms 79.143.25.97
26 2026-08-27 08:33 639234160341037652
50 ms 79.143.25.97
25 2026-08-27 08:16 639234149799404224
128 ms 79.143.25.97
24 2026-08-27 07:59 639234139553286469
136 ms 79.143.25.97
23 2026-08-27 07:05 639234107183588293
118 ms 79.143.25.97
22 2026-08-27 06:48 639234096905435724
122 ms 79.143.25.97
21 2026-08-27 06:31 639234086579410775
128 ms 79.143.25.97
20 2026-08-27 06:13 639234076291157956
133 ms 79.143.25.97
19 2026-08-27 05:56 639234065981939454
128 ms 79.143.25.97
18 2026-08-27 05:39 639234055548642997
66 ms 79.143.25.97
17 2026-08-27 05:22 639234045267979603
175 ms 79.143.25.97
16 2026-08-27 05:05 639234034999717463
136 ms 79.143.25.97
15 2026-08-27 04:47 639234024739225358
123 ms 79.143.25.97
14 2026-08-27 04:30 639234014311170162
157 ms 79.143.25.97
13 2026-08-27 04:13 639234003806017640
121 ms 79.143.25.97
12 2026-08-27 03:55 639233993356203030
118 ms 79.143.25.97
11 2026-08-27 03:02 639233961301716608
128 ms 79.143.25.97
10 2026-08-27 02:45 639233950834200647
123 ms 79.143.25.97
9 2026-08-27 02:27 639233940431849026
56 ms 79.143.25.97
8 2026-08-27 02:10 639233930110596398
148 ms 79.143.25.97
7 2026-08-27 01:52 639233919705434540
130 ms 79.143.25.97
6 2026-08-27 01:35 639233909452807845
522 ms 79.143.25.97
5 2026-08-27 01:18 639233899096420820
68 ms 79.143.25.97
4 2026-08-27 01:01 639233888707824939
119 ms 79.143.25.97
3 2026-08-27 00:44 639233878461203802
124 ms 79.143.25.97
2 2026-08-27 00:26 639233868060868209
2094 ms 79.143.25.97
1 2026-08-27 00:09 639233857450922991
137 ms 79.143.25.97