DNS response history for ns2.viloweb.net

ns2.viloweb.net 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-26. For this date, NameServerHistory found 40 DNS check records, 40 successful responses, 0 failed responses, and 402 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.viloweb.net.
Records on Selected Date

40

Historical checks stored for this nameserver on selected date

Average Latency

402 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 13:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.255.7.8

Most recently resolved hosting IP on selected date

Successful Responses

40

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.viloweb.net

Showing DNS history for 2026-08-26 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
40 2026-08-26 13:06 639233455747096265
479 ms 131.255.7.8
39 2026-08-26 12:49 639233445367152284
491 ms 131.255.7.8
38 2026-08-26 12:31 639233434974187439
477 ms 131.255.7.8
37 2026-08-26 12:14 639233424567558554
4 ms 131.255.7.8
36 2026-08-26 11:57 639233414056832719
474 ms 131.255.7.8
35 2026-08-26 11:39 639233403515141099
481 ms 131.255.7.8
34 2026-08-26 10:44 639233370841350248
474 ms 131.255.7.8
33 2026-08-26 10:27 639233360361507238
472 ms 131.255.7.8
32 2026-08-26 10:10 639233350067824371
474 ms 131.255.7.8
31 2026-08-26 09:53 639233339545274518
242 ms 131.255.7.8
30 2026-08-26 09:35 639233329214918079
495 ms 131.255.7.8
29 2026-08-26 09:18 639233318749762337
262 ms 131.255.7.8
28 2026-08-26 09:00 639233308387917838
578 ms 131.255.7.8
27 2026-08-26 08:43 639233297961740122
253 ms 131.255.7.8
26 2026-08-26 08:26 639233287487159094
479 ms 131.255.7.8
25 2026-08-26 08:08 639233276995531707
470 ms 131.255.7.8
24 2026-08-26 07:51 639233266521568229
479 ms 131.255.7.8
23 2026-08-26 07:33 639233256081047431
253 ms 131.255.7.8
22 2026-08-26 06:39 639233223620132921
473 ms 131.255.7.8
21 2026-08-26 06:22 639233213287814244
482 ms 131.255.7.8
20 2026-08-26 06:05 639233202925983161
239 ms 131.255.7.8
19 2026-08-26 05:47 639233192644780696
480 ms 131.255.7.8
18 2026-08-26 05:30 639233182401183833
474 ms 131.255.7.8
17 2026-08-26 05:13 639233172074181051
476 ms 131.255.7.8
16 2026-08-26 04:56 639233161808421455
239 ms 131.255.7.8
15 2026-08-26 04:39 639233151357344052
261 ms 131.255.7.8
14 2026-08-26 04:21 639233141034116946
476 ms 131.255.7.8
13 2026-08-26 04:04 639233130828334142
476 ms 131.255.7.8
12 2026-08-26 03:47 639233120373450007
238 ms 131.255.7.8
11 2026-08-26 03:30 639233110066216193
236 ms 131.255.7.8
10 2026-08-26 02:36 639233078065410564
472 ms 131.255.7.8
9 2026-08-26 02:19 639233067787457832
484 ms 131.255.7.8
8 2026-08-26 02:02 639233057501801162
473 ms 131.255.7.8
7 2026-08-26 01:45 639233047089431703
239 ms 131.255.7.8
6 2026-08-26 01:28 639233036754790688
3 ms 131.255.7.8
5 2026-08-26 01:11 639233026412602472
474 ms 131.255.7.8
4 2026-08-26 00:53 639233016064066127
472 ms 131.255.7.8
3 2026-08-26 00:36 639233005922655772
474 ms 131.255.7.8
2 2026-08-26 00:19 639232995672256907
609 ms 131.255.7.8
1 2026-08-26 00:02 639232985300872416
476 ms 131.255.7.8