DNS response history for ns2.arenabet23.org

ns2.arenabet23.org 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 33 DNS check records, 33 successful responses, 0 failed responses, and 284 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.arenabet23.org.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

284 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.155.10.178

Most recently resolved hosting IP on selected date

Successful Responses

33

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.arenabet23.org

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
33 2026-08-25 11:49 639232545839529039
582 ms 202.155.10.178
32 2026-08-25 11:31 639232535349285207
177 ms 202.155.10.178
31 2026-08-25 11:14 639232524938080723
175 ms 202.155.10.178
30 2026-08-25 10:20 639232492740373468
360 ms 202.155.10.178
29 2026-08-25 10:03 639232482235303141
343 ms 202.155.10.178
28 2026-08-25 09:45 639232471861770303
575 ms 202.155.10.178
27 2026-08-25 09:28 639232461630217327
372 ms 202.155.10.178
26 2026-08-25 09:11 639232451282965990
171 ms 202.155.10.178
25 2026-08-25 08:54 639232440814614938
349 ms 202.155.10.178
24 2026-08-25 08:36 639232430410720425
475 ms 202.155.10.178
23 2026-08-25 08:19 639232420003096185
355 ms 202.155.10.178
22 2026-08-25 08:02 639232409467287444
177 ms 202.155.10.178
21 2026-08-25 07:44 639232399077195997
174 ms 202.155.10.178
20 2026-08-25 07:27 639232388731528337
174 ms 202.155.10.178
19 2026-08-25 07:09 639232378288598612
497 ms 202.155.10.178
18 2026-08-25 06:16 639232346196373643
344 ms 202.155.10.178
17 2026-08-25 05:59 639232336112370741
371 ms 202.155.10.178
16 2026-08-25 05:42 639232326146508970
170 ms 202.155.10.178
15 2026-08-25 05:26 639232316189381720
2 ms 202.155.10.178
14 2026-08-25 05:09 639232306217998913
4 ms 202.155.10.178
13 2026-08-25 04:52 639232296255744174
344 ms 202.155.10.178
12 2026-08-25 04:36 639232286095760789
182 ms 202.155.10.178
11 2026-08-25 04:19 639232276086186273
180 ms 202.155.10.178
10 2026-08-25 04:02 639232265900986425
370 ms 202.155.10.178
9 2026-08-25 03:45 639232255723518075
189 ms 202.155.10.178
8 2026-08-25 03:28 639232245484452890
333 ms 202.155.10.178
7 2026-08-25 03:11 639232235157175331
175 ms 202.155.10.178
6 2026-08-25 02:18 639232203197189095
347 ms 202.155.10.178
5 2026-08-25 02:01 639232192844564298
186 ms 202.155.10.178
4 2026-08-25 01:43 639232182496008942
338 ms 202.155.10.178
3 2026-08-25 01:26 639232172197053132
346 ms 202.155.10.178
2 2026-08-25 00:33 639232140250307418
178 ms 202.155.10.178
1 2026-08-25 00:16 639232129927860324
349 ms 202.155.10.178