DNS response history for ns3.fullhost.com

ns3.fullhost.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 36 DNS check records, 35 successful responses, 1 failed responses, and 327 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.fullhost.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

327 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.223.228.250

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns3.fullhost.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
36 2026-08-27 12:02 639234286253196126
2009 ms 162.223.228.250
35 2026-08-27 11:08 639234253963286387
65 ms 162.223.228.250
34 2026-08-27 10:51 639234243654907465
34 ms 162.223.228.250
33 2026-08-27 10:34 639234233269654413
2061 ms 162.223.228.250
32 2026-08-27 10:16 639234222943951923
5 ms 162.223.228.250
31 2026-08-27 09:59 639234212558002823
40 ms 162.223.228.250
30 2026-08-27 09:42 639234202117531850
38 ms 162.223.228.250
29 2026-08-27 09:24 639234191649612722
30 ms 162.223.228.250
28 2026-08-27 09:07 639234181105879568
55 ms 162.223.228.250
27 2026-08-27 08:49 639234170713214496
40 ms 162.223.228.250
26 2026-08-27 08:32 639234160341037652
14 ms 162.223.228.250
25 2026-08-27 08:15 639234149799404224
14 ms 162.223.228.250
24 2026-08-27 07:58 639234139553286469
103 ms 162.223.228.250
23 2026-08-27 07:04 639234107183588293
29 ms 162.223.228.250
22 2026-08-27 06:46 639234096905435724
71 ms 162.223.228.250
21 2026-08-27 06:29 639234086579410775
2013 ms 162.223.228.250
20 2026-08-27 06:12 639234076291157956
34 ms 162.223.228.250
19 2026-08-27 05:55 639234065981939454
-
18 2026-08-27 05:38 639234055548642997
26 ms 162.223.228.250
17 2026-08-27 05:20 639234045267979603
27 ms 162.223.228.250
16 2026-08-27 05:03 639234034999717463
54 ms 162.223.228.250
15 2026-08-27 04:46 639234024739225358
2012 ms 162.223.228.250
14 2026-08-27 04:29 639234014311170162
158 ms 162.223.228.250
13 2026-08-27 04:11 639234003806017640
39 ms 162.223.228.250
12 2026-08-27 03:54 639233993356203030
42 ms 162.223.228.250
11 2026-08-27 03:01 639233961301716608
50 ms 162.223.228.250
10 2026-08-27 02:43 639233950834200647
8 ms 162.223.228.250
9 2026-08-27 02:26 639233940431849026
26 ms 162.223.228.250
8 2026-08-27 02:09 639233930110596398
6 ms 162.223.228.250
7 2026-08-27 01:51 639233919705434540
58 ms 162.223.228.250
6 2026-08-27 01:34 639233909452807845
2016 ms 162.223.228.250
5 2026-08-27 01:17 639233899096420820
82 ms 162.223.228.250
4 2026-08-27 01:00 639233888707824939
83 ms 162.223.228.250
3 2026-08-27 00:42 639233878461203802
9 ms 162.223.228.250
2 2026-08-27 00:25 639233868060868209
30 ms 162.223.228.250
1 2026-08-27 00:07 639233857450922991
74 ms 162.223.228.250