DNS response history for ns2.369bin.com

ns2.369bin.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 546 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.369bin.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

546 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 12:50

All timestamps shown in UTC

Latest Resolved IP on Selected Date

157.7.140.107

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.369bin.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:50 639236038221169202
905 ms 157.7.140.107
36 2026-08-29 12:33 639236028175589918
697 ms 157.7.140.107
35 2026-08-29 12:17 639236017965421028
802 ms 157.7.140.107
34 2026-08-29 12:00 639236007792625266
481 ms 157.7.140.107
33 2026-08-29 11:43 639235997602806960
718 ms 157.7.140.107
32 2026-08-29 11:26 639235987487833458
436 ms 157.7.140.107
31 2026-08-29 11:09 639235977211002296
642 ms 157.7.140.107
30 2026-08-29 10:52 639235966864596836
592 ms 157.7.140.107
29 2026-08-29 10:34 639235956590882003
501 ms 157.7.140.107
28 2026-08-29 09:41 639235924465736791
450 ms 157.7.140.107
27 2026-08-29 09:24 639235914430611197
529 ms 157.7.140.107
26 2026-08-29 09:07 639235904343784853
616 ms 157.7.140.107
25 2026-08-29 08:50 639235894201078068
455 ms 157.7.140.107
24 2026-08-29 08:33 639235884233447452
766 ms 157.7.140.107
23 2026-08-29 08:17 639235874142207309
435 ms 157.7.140.107
22 2026-08-29 08:00 639235863974652466
480 ms 157.7.140.107
21 2026-08-29 07:43 639235853716243436
435 ms 157.7.140.107
20 2026-08-29 07:26 639235843614494759
437 ms 157.7.140.107
19 2026-08-29 07:09 639235833401459551
651 ms 157.7.140.107
18 2026-08-29 06:52 639235823220464528
439 ms 157.7.140.107
17 2026-08-29 06:35 639235812997510905
733 ms 157.7.140.107
16 2026-08-29 05:42 639235781101962521
446 ms 157.7.140.107
15 2026-08-29 05:25 639235771207673260
830 ms 157.7.140.107
14 2026-08-29 05:08 639235761047429642
444 ms 157.7.140.107
13 2026-08-29 04:52 639235750964347246
219 ms 157.7.140.107
12 2026-08-29 04:35 639235740923490874
442 ms 157.7.140.107
11 2026-08-29 04:18 639235730842894399
671 ms 157.7.140.107
10 2026-08-29 04:01 639235720760084717
436 ms 157.7.140.107
9 2026-08-29 03:44 639235710843666743
656 ms 157.7.140.107
8 2026-08-29 03:28 639235700733510561
445 ms 157.7.140.107
7 2026-08-29 03:11 639235690509906192
479 ms 157.7.140.107
6 2026-08-29 02:54 639235680156673501
619 ms 157.7.140.107
5 2026-08-29 02:36 639235669720606443
447 ms 157.7.140.107
4 2026-08-29 01:43 639235637451417084
439 ms 157.7.140.107
3 2026-08-29 01:25 639235627307383453
568 ms 157.7.140.107
2 2026-08-29 01:08 639235616906386856
433 ms 157.7.140.107
1 2026-08-29 00:51 639235606582912691
436 ms 157.7.140.107