DNS response history for ns2.shipserver.com

ns2.shipserver.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 30 DNS check records, 29 successful responses, 1 failed responses, and 344 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.shipserver.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

344 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.64.179.126

Most recently resolved hosting IP on selected date

Successful Responses

29

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 ns2.shipserver.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
30 2026-08-27 09:43 639234202117531850
86 ms 208.64.179.126
29 2026-08-27 09:26 639234191649612722
157 ms 208.64.179.126
28 2026-08-27 09:08 639234181105879568
130 ms 208.64.179.126
27 2026-08-27 08:51 639234170713214496
2087 ms 208.64.179.126
26 2026-08-27 08:33 639234160341037652
82 ms 208.64.179.126
25 2026-08-27 08:16 639234149799404224
79 ms 208.64.179.126
24 2026-08-27 07:59 639234139553286469
-
23 2026-08-27 07:05 639234107183588293
39 ms 208.64.179.126
22 2026-08-27 06:48 639234096905435724
202 ms 208.64.179.126
21 2026-08-27 06:31 639234086579410775
2 ms 208.64.179.126
20 2026-08-27 06:13 639234076291157956
45 ms 208.64.179.126
19 2026-08-27 05:56 639234065981939454
2 ms 208.64.179.126
18 2026-08-27 05:39 639234055548642997
8 ms 208.64.179.126
17 2026-08-27 05:22 639234045267979603
7 ms 208.64.179.126
16 2026-08-27 05:05 639234034999717463
5 ms 208.64.179.126
15 2026-08-27 04:47 639234024739225358
98 ms 208.64.179.126
14 2026-08-27 04:30 639234014311170162
45 ms 208.64.179.126
13 2026-08-27 04:13 639234003806017640
100 ms 208.64.179.126
12 2026-08-27 03:55 639233993356203030
71 ms 208.64.179.126
11 2026-08-27 03:02 639233961301716608
98 ms 208.64.179.126
10 2026-08-27 02:45 639233950834200647
232 ms 208.64.179.126
9 2026-08-27 02:27 639233940431849026
2112 ms 208.64.179.126
8 2026-08-27 02:10 639233930110596398
2 ms 208.64.179.126
7 2026-08-27 01:53 639233919705434540
15 ms 208.64.179.126
6 2026-08-27 01:35 639233909452807845
2059 ms 208.64.179.126
5 2026-08-27 01:18 639233899096420820
3 ms 208.64.179.126
4 2026-08-27 01:01 639233888707824939
14 ms 208.64.179.126
3 2026-08-27 00:44 639233878461203802
2020 ms 208.64.179.126
2 2026-08-27 00:26 639233868060868209
56 ms 208.64.179.126
1 2026-08-27 00:09 639233857450922991
108 ms 208.64.179.126