DNS response history for ns2.yiban.cn

ns2.yiban.cn 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, 30 successful responses, 0 failed responses, and 504 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.yiban.cn.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

504 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:21

All timestamps shown in UTC

Latest Resolved IP on Selected Date

117.135.145.150

Most recently resolved hosting IP on selected date

Successful Responses

30

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.yiban.cn

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:21 639232492740373468
519 ms 117.135.145.150
29 2026-08-25 10:04 639232482235303141
635 ms 117.135.145.150
28 2026-08-25 09:46 639232471861770303
94 ms 117.135.145.150
27 2026-08-25 09:29 639232461630217327
205 ms 117.135.145.150
26 2026-08-25 09:12 639232451282965990
479 ms 117.135.145.150
25 2026-08-25 08:55 639232440814614938
455 ms 117.135.145.150
24 2026-08-25 08:37 639232430410720425
468 ms 117.135.145.150
23 2026-08-25 08:20 639232420003096185
1782 ms 117.135.145.150
22 2026-08-25 08:02 639232409467287444
5 ms 117.135.145.150
21 2026-08-25 07:45 639232399077195997
13 ms 117.135.145.150
20 2026-08-25 07:28 639232388731528337
865 ms 117.135.145.150
19 2026-08-25 07:10 639232378288598612
600 ms 117.135.145.150
18 2026-08-25 06:16 639232346196373643
449 ms 117.135.145.150
17 2026-08-25 06:00 639232336112370741
10 ms 117.135.145.150
16 2026-08-25 05:43 639232326146508970
604 ms 117.135.145.150
15 2026-08-25 05:26 639232316189381720
1054 ms 117.135.145.150
14 2026-08-25 05:10 639232306217998913
546 ms 117.135.145.150
13 2026-08-25 04:53 639232296255744174
576 ms 117.135.145.150
12 2026-08-25 04:36 639232286095760789
9 ms 117.135.145.150
11 2026-08-25 04:19 639232276086186273
6 ms 117.135.145.150
10 2026-08-25 04:03 639232265900986425
198 ms 117.135.145.150
9 2026-08-25 03:46 639232255723518075
249 ms 117.135.145.150
8 2026-08-25 03:29 639232245484452890
539 ms 117.135.145.150
7 2026-08-25 03:12 639232235157175331
355 ms 117.135.145.150
6 2026-08-25 02:18 639232203197189095
270 ms 117.135.145.150
5 2026-08-25 02:01 639232192844564298
295 ms 117.135.145.150
4 2026-08-25 01:44 639232182496008942
512 ms 117.135.145.150
3 2026-08-25 01:27 639232172197053132
267 ms 117.135.145.150
2 2026-08-25 00:33 639232140250307418
582 ms 117.135.145.150
1 2026-08-25 00:16 639232129927860324
2471 ms 117.135.145.150