DNS response history for ns2.365news.biz

ns2.365news.biz 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-09-01. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 255 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.365news.biz.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

255 ms

Calculated from available response records

Latest Check on Selected Date

2026-09-01 12:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.108.130.120

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.365news.biz

Showing DNS history for 2026-09-01 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-09-01 12:37 639238628486902752
111 ms 213.108.130.120
36 2026-09-01 12:19 639238617906743100
96 ms 213.108.130.120
35 2026-09-01 12:02 639238607506044626
41 ms 213.108.130.120
34 2026-09-01 11:44 639238597040761406
111 ms 213.108.130.120
33 2026-09-01 11:27 639238586261546969
111 ms 213.108.130.120
32 2026-09-01 11:09 639238575587642333
110 ms 213.108.130.120
31 2026-09-01 10:15 639238543127398267
102 ms 213.108.130.120
30 2026-09-01 09:57 639238532668234016
32 ms 213.108.130.120
29 2026-09-01 09:40 639238522029321761
36 ms 213.108.130.120
28 2026-09-01 09:22 639238511519050351
124 ms 213.108.130.120
27 2026-09-01 09:04 639238500942239673
94 ms 213.108.130.120
26 2026-09-01 08:47 639238490412377398
89 ms 213.108.130.120
25 2026-09-01 08:29 639238479833203021
50 ms 213.108.130.120
24 2026-09-01 08:11 639238469140507479
100 ms 213.108.130.120
23 2026-09-01 07:54 639238458443560361
144 ms 213.108.130.120
22 2026-09-01 07:36 639238447694851502
131 ms 213.108.130.120
21 2026-09-01 07:17 639238436624109087
87 ms 213.108.130.120
20 2026-09-01 06:59 639238425565611335
123 ms 213.108.130.120
19 2026-09-01 06:03 639238392250222581
149 ms 213.108.130.120
18 2026-09-01 05:45 639238381322537831
123 ms 213.108.130.120
17 2026-09-01 05:27 639238370248186084
38 ms 213.108.130.120
16 2026-09-01 05:08 639238359264687845
87 ms 213.108.130.120
15 2026-09-01 04:50 639238348534621818
114 ms 213.108.130.120
14 2026-09-01 04:32 639238337725739433
115 ms 213.108.130.120
13 2026-09-01 04:14 639238326844749368
2028 ms 213.108.130.120
12 2026-09-01 03:56 639238315792024737
108 ms 213.108.130.120
11 2026-09-01 03:38 639238304931064768
97 ms 213.108.130.120
10 2026-09-01 03:20 639238294131483803
92 ms 213.108.130.120
9 2026-09-01 03:02 639238283314985519
99 ms 213.108.130.120
8 2026-09-01 02:43 639238272374093187
99 ms 213.108.130.120
7 2026-09-01 01:49 639238240032549922
118 ms 213.108.130.120
6 2026-09-01 01:32 639238229204177368
94 ms 213.108.130.120
5 2026-09-01 01:13 639238218326150282
93 ms 213.108.130.120
4 2026-09-01 00:55 639238207574700853
2010 ms 213.108.130.120
3 2026-09-01 00:37 639238196660283915
2075 ms 213.108.130.120
2 2026-09-01 00:19 639238185782358546
92 ms 213.108.130.120
1 2026-09-01 00:01 639238175054391781
128 ms 213.108.130.120