DNS response history for ns2.wippy.com

ns2.wippy.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-29. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 297 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.wippy.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

297 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.159.1.232

Most recently resolved hosting IP on selected date

Successful Responses

37

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

Showing DNS history for 2026-08-29 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
37 2026-08-29 12:38 639236038221169202
4 ms 162.159.1.232
36 2026-08-29 12:21 639236028175589918
49 ms 162.159.1.232
35 2026-08-29 12:04 639236017965421028
51 ms 162.159.1.232
34 2026-08-29 11:47 639236007792625266
38 ms 162.159.1.232
33 2026-08-29 11:30 639235997602806960
7 ms 162.159.1.232
32 2026-08-29 11:13 639235987487833458
27 ms 162.159.1.232
31 2026-08-29 10:56 639235977211002296
2024 ms 162.159.1.232
30 2026-08-29 10:39 639235966864596836
4 ms 162.159.1.232
29 2026-08-29 10:22 639235956590882003
2022 ms 162.159.1.232
28 2026-08-29 09:28 639235924465736791
40 ms 162.159.1.232
27 2026-08-29 09:11 639235914430611197
21 ms 162.159.1.232
26 2026-08-29 08:55 639235904343784853
5 ms 162.159.1.232
25 2026-08-29 08:38 639235894201078068
44 ms 162.159.1.232
24 2026-08-29 08:21 639235884233447452
68 ms 162.159.1.232
23 2026-08-29 08:04 639235874142207309
31 ms 162.159.1.232
22 2026-08-29 07:47 639235863974652466
26 ms 162.159.1.232
21 2026-08-29 07:30 639235853716243436
33 ms 162.159.1.232
20 2026-08-29 07:13 639235843614494759
40 ms 162.159.1.232
19 2026-08-29 06:56 639235833401459551
4 ms 162.159.1.232
18 2026-08-29 06:39 639235823220464528
20 ms 162.159.1.232
17 2026-08-29 06:22 639235812997510905
3 ms 162.159.1.232
16 2026-08-29 05:29 639235781101962521
23 ms 162.159.1.232
15 2026-08-29 05:13 639235771207673260
32 ms 162.159.1.232
14 2026-08-29 04:56 639235761047429642
36 ms 162.159.1.232
13 2026-08-29 04:39 639235750964347246
16 ms 162.159.1.232
12 2026-08-29 04:22 639235740923490874
49 ms 162.159.1.232
11 2026-08-29 04:05 639235730842894399
19 ms 162.159.1.232
10 2026-08-29 03:49 639235720760084717
10 ms 162.159.1.232
9 2026-08-29 03:32 639235710843666743
41 ms 162.159.1.232
8 2026-08-29 03:15 639235700733510561
7 ms 162.159.1.232
7 2026-08-29 02:58 639235690509906192
2023 ms 162.159.1.232
6 2026-08-29 02:41 639235680156673501
33 ms 162.159.1.232
5 2026-08-29 02:24 639235669720606443
2025 ms 162.159.1.232
4 2026-08-29 01:30 639235637451417084
41 ms 162.159.1.232
3 2026-08-29 01:13 639235627307383453
2035 ms 162.159.1.232
2 2026-08-29 00:55 639235616906386856
20 ms 162.159.1.232
1 2026-08-29 00:38 639235606582912691
10 ms 162.159.1.232