DNS response history for ns2.chipbert.com

ns2.chipbert.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 231 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.chipbert.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

231 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:28

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.29.138.190

Most recently resolved hosting IP on selected date

Successful Responses

33

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

Showing DNS history for 2026-08-26 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
33 2026-08-26 10:28 639233360361507238
306 ms 66.29.138.190
32 2026-08-26 10:11 639233350067824371
295 ms 66.29.138.190
31 2026-08-26 09:54 639233339545274518
317 ms 66.29.138.190
30 2026-08-26 09:36 639233329214918079
311 ms 66.29.138.190
29 2026-08-26 09:19 639233318749762337
301 ms 66.29.138.190
28 2026-08-26 09:01 639233308387917838
158 ms 66.29.138.190
27 2026-08-26 08:44 639233297961740122
304 ms 66.29.138.190
26 2026-08-26 08:27 639233287487159094
308 ms 66.29.138.190
25 2026-08-26 08:09 639233276995531707
299 ms 66.29.138.190
24 2026-08-26 07:52 639233266521568229
301 ms 66.29.138.190
23 2026-08-26 07:34 639233256081047431
155 ms 66.29.138.190
22 2026-08-26 06:40 639233223620132921
3 ms 66.29.138.190
21 2026-08-26 06:23 639233213287814244
158 ms 66.29.138.190
20 2026-08-26 06:06 639233202925983161
3 ms 66.29.138.190
19 2026-08-26 05:48 639233192644780696
303 ms 66.29.138.190
18 2026-08-26 05:31 639233182401183833
312 ms 66.29.138.190
17 2026-08-26 05:14 639233172074181051
300 ms 66.29.138.190
16 2026-08-26 04:57 639233161808421455
148 ms 66.29.138.190
15 2026-08-26 04:40 639233151357344052
305 ms 66.29.138.190
14 2026-08-26 04:22 639233141034116946
297 ms 66.29.138.190
13 2026-08-26 04:05 639233130828334142
293 ms 66.29.138.190
12 2026-08-26 03:48 639233120373450007
148 ms 66.29.138.190
11 2026-08-26 03:31 639233110066216193
155 ms 66.29.138.190
10 2026-08-26 02:37 639233078065410564
309 ms 66.29.138.190
9 2026-08-26 02:20 639233067787457832
304 ms 66.29.138.190
8 2026-08-26 02:03 639233057501801162
150 ms 66.29.138.190
7 2026-08-26 01:46 639233047089431703
148 ms 66.29.138.190
6 2026-08-26 01:29 639233036754790688
305 ms 66.29.138.190
5 2026-08-26 01:12 639233026412602472
155 ms 66.29.138.190
4 2026-08-26 00:54 639233016064066127
309 ms 66.29.138.190
3 2026-08-26 00:37 639233005922655772
148 ms 66.29.138.190
2 2026-08-26 00:20 639232995672256907
156 ms 66.29.138.190
1 2026-08-26 00:03 639232985300872416
152 ms 66.29.138.190