DNS response history for ns4.beyconhost.com

ns4.beyconhost.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 30 DNS check records, 30 successful responses, 0 failed responses, and 237 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 ns4.beyconhost.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

237 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:46

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.230.111.111

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns4.beyconhost.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
30 2026-08-28 12:46 639235174453894956
112 ms 37.230.111.111
29 2026-08-28 12:28 639235163898672622
2066 ms 37.230.111.111
28 2026-08-28 11:35 639235132147470568
46 ms 37.230.111.111
27 2026-08-28 11:18 639235121907744088
54 ms 37.230.111.111
26 2026-08-28 11:01 639235111428014262
111 ms 37.230.111.111
25 2026-08-28 10:43 639235100921813626
107 ms 37.230.111.111
24 2026-08-28 09:49 639235068670703481
121 ms 37.230.111.111
23 2026-08-28 09:32 639235058337459445
111 ms 37.230.111.111
22 2026-08-28 09:15 639235047825109146
57 ms 37.230.111.111
21 2026-08-28 08:57 639235037383229033
112 ms 37.230.111.111
20 2026-08-28 08:04 639235005619242711
115 ms 37.230.111.111
19 2026-08-28 07:47 639234995310346584
112 ms 37.230.111.111
18 2026-08-28 07:30 639234984946548933
56 ms 37.230.111.111
17 2026-08-28 07:13 639234974608077290
56 ms 37.230.111.111
16 2026-08-28 06:19 639234942529845595
118 ms 37.230.111.111
15 2026-08-28 06:02 639234932259126627
112 ms 37.230.111.111
14 2026-08-28 05:45 639234921916735988
55 ms 37.230.111.111
13 2026-08-28 05:28 639234911470038027
56 ms 37.230.111.111
12 2026-08-28 04:34 639234879588411654
2077 ms 37.230.111.111
11 2026-08-28 04:17 639234869341589104
109 ms 37.230.111.111
10 2026-08-28 04:00 639234859012216675
114 ms 37.230.111.111
9 2026-08-28 03:43 639234848695364934
112 ms 37.230.111.111
8 2026-08-28 02:50 639234816952458162
111 ms 37.230.111.111
7 2026-08-28 02:33 639234806773081598
114 ms 37.230.111.111
6 2026-08-28 02:16 639234796382955255
298 ms 37.230.111.111
5 2026-08-28 01:58 639234786015782563
28 ms 37.230.111.111
4 2026-08-28 01:05 639234753811917646
110 ms 37.230.111.111
3 2026-08-28 00:48 639234743739767811
147 ms 37.230.111.111
2 2026-08-28 00:31 639234733372362811
216 ms 37.230.111.111
1 2026-08-28 00:13 639234723048550337
109 ms 37.230.111.111