DNS response history for ns3.cdn30.com

ns3.cdn30.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 36 DNS check records, 36 successful responses, 0 failed responses, and 186 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 ns3.cdn30.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

186 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 06:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

180.130.108.111

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 ns3.cdn30.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
36 2026-08-25 06:14 639232346196373643
238 ms 180.130.108.111
35 2026-08-25 06:14 639232346196373643
238 ms 27.148.142.89
34 2026-08-25 05:57 639232336112370741
171 ms 180.130.108.111
33 2026-08-25 05:57 639232336112370741
171 ms 27.148.142.89
32 2026-08-25 05:40 639232326146508970
282 ms 180.130.108.111
31 2026-08-25 05:40 639232326146508970
282 ms 27.148.142.89
30 2026-08-25 05:24 639232316189381720
203 ms 180.130.108.111
29 2026-08-25 05:24 639232316189381720
203 ms 27.148.142.89
28 2026-08-25 05:07 639232306217998913
217 ms 180.130.108.111
27 2026-08-25 05:07 639232306217998913
217 ms 27.148.142.89
26 2026-08-25 04:50 639232296255744174
27 ms 27.148.142.89
25 2026-08-25 04:50 639232296255744174
27 ms 180.130.108.111
24 2026-08-25 04:34 639232286095760789
10 ms 180.130.108.111
23 2026-08-25 04:34 639232286095760789
10 ms 27.148.142.89
22 2026-08-25 04:17 639232276086186273
251 ms 180.130.108.111
21 2026-08-25 04:17 639232276086186273
251 ms 27.148.142.89
20 2026-08-25 04:00 639232265900986425
165 ms 180.130.108.111
19 2026-08-25 04:00 639232265900986425
165 ms 27.148.142.89
18 2026-08-25 03:43 639232255723518075
203 ms 180.130.108.111
17 2026-08-25 03:43 639232255723518075
203 ms 27.148.142.89
16 2026-08-25 03:26 639232245484452890
5 ms 180.130.108.111
15 2026-08-25 03:26 639232245484452890
5 ms 27.148.142.89
14 2026-08-25 03:09 639232235157175331
7 ms 180.130.108.111
13 2026-08-25 03:09 639232235157175331
7 ms 27.148.142.89
12 2026-08-25 02:15 639232203197189095
200 ms 180.130.108.111
11 2026-08-25 02:15 639232203197189095
200 ms 27.148.142.89
10 2026-08-25 01:58 639232192844564298
283 ms 180.130.108.111
9 2026-08-25 01:58 639232192844564298
283 ms 27.148.142.89
8 2026-08-25 01:41 639232182496008942
266 ms 180.130.108.111
7 2026-08-25 01:41 639232182496008942
266 ms 27.148.142.89
6 2026-08-25 01:24 639232172197053132
220 ms 180.130.108.111
5 2026-08-25 01:24 639232172197053132
220 ms 27.148.142.89
4 2026-08-25 00:30 639232140250307418
196 ms 180.130.108.111
3 2026-08-25 00:30 639232140250307418
196 ms 27.148.142.89
2 2026-08-25 00:14 639232129927860324
402 ms 180.130.108.111
1 2026-08-25 00:14 639232129927860324
402 ms 27.148.142.89