DNS response history for ns2.chipmanpoint.com

ns2.chipmanpoint.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, 36 successful responses, 0 failed responses, and 350 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.chipmanpoint.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

350 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.153.181.68

Most recently resolved hosting IP on selected date

Successful Responses

36

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.chipmanpoint.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:06 639234286253196126
338 ms 160.153.181.68
35 2026-08-27 11:12 639234253963286387
355 ms 160.153.181.68
34 2026-08-27 10:55 639234243654907465
339 ms 160.153.181.68
33 2026-08-27 10:38 639234233269654413
332 ms 160.153.181.68
32 2026-08-27 10:21 639234222943951923
404 ms 160.153.181.68
31 2026-08-27 10:03 639234212558002823
322 ms 160.153.181.68
30 2026-08-27 09:46 639234202117531850
385 ms 160.153.181.68
29 2026-08-27 09:29 639234191649612722
360 ms 160.153.181.68
28 2026-08-27 09:11 639234181105879568
350 ms 160.153.181.68
27 2026-08-27 08:54 639234170713214496
347 ms 160.153.181.68
26 2026-08-27 08:36 639234160341037652
326 ms 160.153.181.68
25 2026-08-27 08:19 639234149799404224
331 ms 160.153.181.68
24 2026-08-27 08:02 639234139553286469
344 ms 160.153.181.68
23 2026-08-27 07:08 639234107183588293
23 ms 160.153.181.68
22 2026-08-27 06:51 639234096905435724
331 ms 160.153.181.68
21 2026-08-27 06:33 639234086579410775
379 ms 160.153.181.68
20 2026-08-27 06:16 639234076291157956
366 ms 160.153.181.68
19 2026-08-27 05:59 639234065981939454
330 ms 160.153.181.68
18 2026-08-27 05:42 639234055548642997
338 ms 160.153.181.68
17 2026-08-27 05:25 639234045267979603
318 ms 160.153.181.68
16 2026-08-27 05:08 639234034999717463
314 ms 160.153.181.68
15 2026-08-27 04:50 639234024739225358
320 ms 160.153.181.68
14 2026-08-27 04:33 639234014311170162
408 ms 160.153.181.68
13 2026-08-27 04:16 639234003806017640
415 ms 160.153.181.68
12 2026-08-27 03:58 639233993356203030
352 ms 160.153.181.68
11 2026-08-27 03:05 639233961301716608
357 ms 160.153.181.68
10 2026-08-27 02:48 639233950834200647
371 ms 160.153.181.68
9 2026-08-27 02:30 639233940431849026
319 ms 160.153.181.68
8 2026-08-27 02:13 639233930110596398
373 ms 160.153.181.68
7 2026-08-27 01:56 639233919705434540
319 ms 160.153.181.68
6 2026-08-27 01:38 639233909452807845
339 ms 160.153.181.68
5 2026-08-27 01:21 639233899096420820
344 ms 160.153.181.68
4 2026-08-27 01:04 639233888707824939
317 ms 160.153.181.68
3 2026-08-27 00:47 639233878461203802
761 ms 160.153.181.68
2 2026-08-27 00:29 639233868060868209
326 ms 160.153.181.68
1 2026-08-27 00:12 639233857450922991
355 ms 160.153.181.68