DNS response history for ns2.congcong.wang

ns2.congcong.wang 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 31 DNS check records, 30 successful responses, 1 failed responses, and 553 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.congcong.wang.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

553 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

139.224.142.122

Most recently resolved hosting IP on selected date

Successful Responses

30

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.congcong.wang

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
31 2026-08-25 10:22 639232492740373468
540 ms 139.224.142.122
30 2026-08-25 10:05 639232482235303141
1026 ms 139.224.142.122
29 2026-08-25 09:47 639232471861770303
240 ms 139.224.142.122
28 2026-08-25 09:30 639232461630217327
492 ms 139.224.142.122
27 2026-08-25 09:13 639232451282965990
548 ms 139.224.142.122
26 2026-08-25 08:56 639232440814614938
509 ms 139.224.142.122
25 2026-08-25 08:38 639232430410720425
253 ms 139.224.142.122
24 2026-08-25 08:21 639232420003096185
521 ms 139.224.142.122
23 2026-08-25 08:03 639232409467287444
511 ms 139.224.142.122
22 2026-08-25 07:46 639232399077195997
538 ms 139.224.142.122
21 2026-08-25 07:29 639232388731528337
546 ms 139.224.142.122
20 2026-08-25 07:11 639232378288598612
1011 ms 139.224.142.122
19 2026-08-25 06:17 639232346196373643
522 ms 139.224.142.122
18 2026-08-25 06:01 639232336112370741
982 ms 139.224.142.122
17 2026-08-25 05:44 639232326146508970
-
16 2026-08-25 05:27 639232316189381720
543 ms 139.224.142.122
15 2026-08-25 05:11 639232306217998913
262 ms 139.224.142.122
14 2026-08-25 04:54 639232296255744174
535 ms 139.224.142.122
13 2026-08-25 04:37 639232286095760789
1045 ms 139.224.142.122
12 2026-08-25 04:20 639232276086186273
531 ms 139.224.142.122
11 2026-08-25 04:04 639232265900986425
234 ms 139.224.142.122
10 2026-08-25 03:47 639232255723518075
257 ms 139.224.142.122
9 2026-08-25 03:30 639232245484452890
535 ms 139.224.142.122
8 2026-08-25 03:13 639232235157175331
523 ms 139.224.142.122
7 2026-08-25 02:19 639232203197189095
223 ms 139.224.142.122
6 2026-08-25 02:02 639232192844564298
318 ms 139.224.142.122
5 2026-08-25 01:45 639232182496008942
273 ms 139.224.142.122
4 2026-08-25 01:28 639232172197053132
551 ms 139.224.142.122
3 2026-08-25 00:34 639232140250307418
540 ms 139.224.142.122
2 2026-08-25 00:17 639232129927860324
477 ms 139.224.142.122
1 2026-08-25 00:00 639232119551972438
1490 ms 139.224.142.122