DNS response history for ns2.cppc-app.com

ns2.cppc-app.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-25. For this date, NameServerHistory found 30 DNS check records, 29 successful responses, 1 failed responses, and 159 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.cppc-app.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

159 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

31.200.246.46

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.cppc-app.com

Showing DNS history for 2026-08-25 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-25 10:16 639232492740373468
111 ms 31.200.246.46
29 2026-08-25 09:59 639232482235303141
97 ms 31.200.246.46
28 2026-08-25 09:41 639232471861770303
93 ms 31.200.246.46
27 2026-08-25 09:24 639232461630217327
99 ms 31.200.246.46
26 2026-08-25 09:07 639232451282965990
90 ms 31.200.246.46
25 2026-08-25 08:49 639232440814614938
63 ms 31.200.246.46
24 2026-08-25 08:32 639232430410720425
54 ms 31.200.246.46
23 2026-08-25 08:15 639232420003096185
88 ms 31.200.246.46
22 2026-08-25 07:57 639232409467287444
83 ms 31.200.246.46
21 2026-08-25 07:40 639232399077195997
96 ms 31.200.246.46
20 2026-08-25 07:22 639232388731528337
119 ms 31.200.246.46
19 2026-08-25 07:05 639232378288598612
86 ms 31.200.246.46
18 2026-08-25 06:12 639232346196373643
-
17 2026-08-25 05:55 639232336112370741
82 ms 31.200.246.46
16 2026-08-25 05:38 639232326146508970
103 ms 31.200.246.46
15 2026-08-25 05:21 639232316189381720
2162 ms 31.200.246.46
14 2026-08-25 05:05 639232306217998913
81 ms 31.200.246.46
13 2026-08-25 04:48 639232296255744174
82 ms 31.200.246.46
12 2026-08-25 04:31 639232286095760789
88 ms 31.200.246.46
11 2026-08-25 04:15 639232276086186273
88 ms 31.200.246.46
10 2026-08-25 03:58 639232265900986425
89 ms 31.200.246.46
9 2026-08-25 03:41 639232255723518075
91 ms 31.200.246.46
8 2026-08-25 03:24 639232245484452890
68 ms 31.200.246.46
7 2026-08-25 03:07 639232235157175331
75 ms 31.200.246.46
6 2026-08-25 02:13 639232203197189095
84 ms 31.200.246.46
5 2026-08-25 01:56 639232192844564298
45 ms 31.200.246.46
4 2026-08-25 01:39 639232182496008942
101 ms 31.200.246.46
3 2026-08-25 01:22 639232172197053132
95 ms 31.200.246.46
2 2026-08-25 00:28 639232140250307418
86 ms 31.200.246.46
1 2026-08-25 00:11 639232129927860324
101 ms 31.200.246.46