DNS response history for ns2.b3host.com

ns2.b3host.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-28. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 280 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.b3host.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

198.175.150.39

Most recently resolved hosting IP on selected date

Successful Responses

32

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.b3host.com

Showing DNS history for 2026-08-28 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
32 2026-08-28 13:19 639235195230848570
244 ms 198.175.150.39
31 2026-08-28 13:02 639235184840503274
236 ms 198.175.150.39
30 2026-08-28 12:45 639235174453894956
157 ms 198.175.150.39
29 2026-08-28 12:27 639235163898672622
180 ms 198.175.150.39
28 2026-08-28 11:34 639235132147470568
24 ms 198.175.150.39
27 2026-08-28 11:17 639235121907744088
232 ms 198.175.150.39
26 2026-08-28 11:00 639235111428014262
161 ms 198.175.150.39
25 2026-08-28 10:42 639235100921813626
237 ms 198.175.150.39
24 2026-08-28 09:48 639235068670703481
241 ms 198.175.150.39
23 2026-08-28 09:31 639235058337459445
233 ms 198.175.150.39
22 2026-08-28 09:14 639235047825109146
247 ms 198.175.150.39
21 2026-08-28 08:56 639235037383229033
254 ms 198.175.150.39
20 2026-08-28 08:03 639235005619242711
268 ms 198.175.150.39
19 2026-08-28 07:46 639234995310346584
152 ms 198.175.150.39
18 2026-08-28 07:29 639234984946548933
244 ms 198.175.150.39
17 2026-08-28 07:11 639234974608077290
123 ms 198.175.150.39
16 2026-08-28 06:18 639234942529845595
234 ms 198.175.150.39
15 2026-08-28 06:01 639234932259126627
235 ms 198.175.150.39
14 2026-08-28 05:44 639234921916735988
226 ms 198.175.150.39
13 2026-08-28 05:26 639234911470038027
241 ms 198.175.150.39
12 2026-08-28 04:33 639234879588411654
2142 ms 198.175.150.39
11 2026-08-28 04:16 639234869341589104
128 ms 198.175.150.39
10 2026-08-28 03:59 639234859012216675
259 ms 198.175.150.39
9 2026-08-28 03:42 639234848695364934
248 ms 198.175.150.39
8 2026-08-28 02:49 639234816952458162
234 ms 198.175.150.39
7 2026-08-28 02:32 639234806773081598
231 ms 198.175.150.39
6 2026-08-28 02:15 639234796382955255
349 ms 198.175.150.39
5 2026-08-28 01:57 639234786015782563
246 ms 198.175.150.39
4 2026-08-28 01:04 639234753811917646
248 ms 198.175.150.39
3 2026-08-28 00:47 639234743739767811
244 ms 198.175.150.39
2 2026-08-28 00:30 639234733372362811
239 ms 198.175.150.39
1 2026-08-28 00:12 639234723048550337
234 ms 198.175.150.39