DNS response history for ns2.viraal.org

ns2.viraal.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-26. For this date, NameServerHistory found 35 DNS check records, 34 successful responses, 1 failed responses, and 176 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.viraal.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

176 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.181.99.130

Most recently resolved hosting IP on selected date

Successful Responses

34

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.viraal.org

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
35 2026-08-26 11:45 639233414056832719
187 ms 135.181.99.130
34 2026-08-26 11:27 639233403515141099
49 ms 135.181.99.130
33 2026-08-26 10:33 639233370841350248
403 ms 135.181.99.130
32 2026-08-26 10:16 639233360361507238
48 ms 135.181.99.130
31 2026-08-26 09:58 639233350067824371
9 ms 135.181.99.130
30 2026-08-26 09:41 639233339545274518
489 ms 135.181.99.130
29 2026-08-26 09:24 639233329214918079
12 ms 135.181.99.130
28 2026-08-26 09:06 639233318749762337
6 ms 135.181.99.130
27 2026-08-26 08:49 639233308387917838
208 ms 135.181.99.130
26 2026-08-26 08:31 639233297961740122
41 ms 135.181.99.130
25 2026-08-26 08:14 639233287487159094
402 ms 135.181.99.130
24 2026-08-26 07:57 639233276995531707
15 ms 135.181.99.130
23 2026-08-26 07:39 639233266521568229
268 ms 135.181.99.130
22 2026-08-26 07:22 639233256081047431
591 ms 135.181.99.130
21 2026-08-26 06:28 639233223620132921
4 ms 135.181.99.130
20 2026-08-26 06:10 639233213287814244
4 ms 135.181.99.130
19 2026-08-26 05:53 639233202925983161
282 ms 135.181.99.130
18 2026-08-26 05:36 639233192644780696
156 ms 135.181.99.130
17 2026-08-26 05:19 639233182401183833
197 ms 135.181.99.130
16 2026-08-26 05:02 639233172074181051
166 ms 135.181.99.130
15 2026-08-26 04:45 639233161808421455
157 ms 135.181.99.130
14 2026-08-26 04:27 639233151357344052
45 ms 135.181.99.130
13 2026-08-26 04:10 639233141034116946
139 ms 135.181.99.130
12 2026-08-26 03:53 639233130828334142
79 ms 135.181.99.130
11 2026-08-26 03:36 639233120373450007
174 ms 135.181.99.130
10 2026-08-26 03:18 639233110066216193
67 ms 135.181.99.130
9 2026-08-26 02:25 639233078065410564
487 ms 135.181.99.130
8 2026-08-26 02:08 639233067787457832
-
7 2026-08-26 01:51 639233057501801162
31 ms 135.181.99.130
6 2026-08-26 01:33 639233047089431703
46 ms 135.181.99.130
5 2026-08-26 01:16 639233036754790688
262 ms 135.181.99.130
4 2026-08-26 00:59 639233026412602472
74 ms 135.181.99.130
3 2026-08-26 00:42 639233016064066127
198 ms 135.181.99.130
2 2026-08-26 00:25 639233005922655772
186 ms 135.181.99.130
1 2026-08-26 00:08 639232995672256907
494 ms 135.181.99.130