History for ns1.bingnode.top

Domain: bingnode.top • Tracking since 2026-08-04 23:25 UTC

DNS response history for ns1.bingnode.top

ns1.bingnode.top 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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 112 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 ns1.bingnode.top.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

112 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.38.89.85

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns1.bingnode.top

Showing DNS history for 2026-08-27 UTC. Newest records appear first.

Today Previous Next

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
35 2026-08-27 11:09 639234253963286387
41 ms 51.38.89.85
34 2026-08-27 10:52 639234243654907465
200 ms 51.38.89.85
33 2026-08-27 10:34 639234233269654413
79 ms 51.38.89.85
32 2026-08-27 10:17 639234222943951923
145 ms 51.38.89.85
31 2026-08-27 10:00 639234212558002823
28 ms 51.38.89.85
30 2026-08-27 09:42 639234202117531850
34 ms 51.38.89.85
29 2026-08-27 09:25 639234191649612722
34 ms 51.38.89.85
28 2026-08-27 09:07 639234181105879568
57 ms 51.38.89.85
27 2026-08-27 08:50 639234170713214496
52 ms 51.38.89.85
26 2026-08-27 08:33 639234160341037652
60 ms 51.38.89.85
25 2026-08-27 08:15 639234149799404224
24 ms 51.38.89.85
24 2026-08-27 07:58 639234139553286469
96 ms 51.38.89.85
23 2026-08-27 07:04 639234107183588293
38 ms 51.38.89.85
22 2026-08-27 06:47 639234096905435724
73 ms 51.38.89.85
21 2026-08-27 06:30 639234086579410775
56 ms 51.38.89.85
20 2026-08-27 06:13 639234076291157956
8 ms 51.38.89.85
19 2026-08-27 05:56 639234065981939454
24 ms 51.38.89.85
18 2026-08-27 05:38 639234055548642997
26 ms 51.38.89.85
17 2026-08-27 05:21 639234045267979603
7 ms 51.38.89.85
16 2026-08-27 05:04 639234034999717463
58 ms 51.38.89.85
15 2026-08-27 04:47 639234024739225358
53 ms 51.38.89.85
14 2026-08-27 04:30 639234014311170162
77 ms 51.38.89.85
13 2026-08-27 04:12 639234003806017640
69 ms 51.38.89.85
12 2026-08-27 03:54 639233993356203030
13 ms 51.38.89.85
11 2026-08-27 03:01 639233961301716608
26 ms 51.38.89.85
10 2026-08-27 02:44 639233950834200647
51 ms 51.38.89.85
9 2026-08-27 02:26 639233940431849026
37 ms 51.38.89.85
8 2026-08-27 02:09 639233930110596398
2021 ms 51.38.89.85
7 2026-08-27 01:52 639233919705434540
56 ms 51.38.89.85
6 2026-08-27 01:35 639233909452807845
55 ms 51.38.89.85
5 2026-08-27 01:17 639233899096420820
37 ms 51.38.89.85
4 2026-08-27 01:00 639233888707824939
136 ms 51.38.89.85
3 2026-08-27 00:43 639233878461203802
39 ms 51.38.89.85
2 2026-08-27 00:26 639233868060868209
54 ms 51.38.89.85
1 2026-08-27 00:08 639233857450922991
55 ms 51.38.89.85