DNS response history for ns2.virmanporgence.com

ns2.virmanporgence.com 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 38 DNS check records, 38 successful responses, 0 failed responses, and 380 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.virmanporgence.com.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

380 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:31

All timestamps shown in UTC

Latest Resolved IP on Selected Date

8.8.8.164

Most recently resolved hosting IP on selected date

Successful Responses

38

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.virmanporgence.com

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
38 2026-08-26 12:31 639233434974187439
435 ms 8.8.8.164
37 2026-08-26 12:14 639233424567558554
358 ms 8.8.8.164
36 2026-08-26 11:56 639233414056832719
354 ms 8.8.8.164
35 2026-08-26 11:39 639233403515141099
352 ms 8.8.8.164
34 2026-08-26 10:44 639233370841350248
349 ms 8.8.8.164
33 2026-08-26 10:27 639233360361507238
349 ms 8.8.8.164
32 2026-08-26 10:09 639233350067824371
437 ms 8.8.8.164
31 2026-08-26 09:52 639233339545274518
352 ms 8.8.8.164
30 2026-08-26 09:35 639233329214918079
367 ms 8.8.8.164
29 2026-08-26 09:17 639233318749762337
1884 ms 8.8.8.164
28 2026-08-26 09:00 639233308387917838
233 ms 8.8.8.164
27 2026-08-26 08:43 639233297961740122
355 ms 8.8.8.164
26 2026-08-26 08:25 639233287487159094
237 ms 8.8.8.164
25 2026-08-26 08:08 639233276995531707
367 ms 8.8.8.164
24 2026-08-26 07:50 639233266521568229
234 ms 8.8.8.164
23 2026-08-26 07:33 639233256081047431
351 ms 8.8.8.164
22 2026-08-26 06:39 639233223620132921
367 ms 8.8.8.164
21 2026-08-26 06:22 639233213287814244
353 ms 8.8.8.164
20 2026-08-26 06:04 639233202925983161
523 ms 8.8.8.164
19 2026-08-26 05:47 639233192644780696
347 ms 8.8.8.164
18 2026-08-26 05:30 639233182401183833
360 ms 8.8.8.164
17 2026-08-26 05:13 639233172074181051
244 ms 8.8.8.164
16 2026-08-26 04:56 639233161808421455
351 ms 8.8.8.164
15 2026-08-26 04:39 639233151357344052
2 ms 8.8.8.164
14 2026-08-26 04:21 639233141034116946
354 ms 8.8.8.164
13 2026-08-26 04:04 639233130828334142
366 ms 8.8.8.164
12 2026-08-26 03:47 639233120373450007
235 ms 8.8.8.164
11 2026-08-26 03:29 639233110066216193
352 ms 8.8.8.164
10 2026-08-26 02:36 639233078065410564
590 ms 8.8.8.164
9 2026-08-26 02:19 639233067787457832
239 ms 8.8.8.164
8 2026-08-26 02:02 639233057501801162
235 ms 8.8.8.164
7 2026-08-26 01:45 639233047089431703
354 ms 8.8.8.164
6 2026-08-26 01:27 639233036754790688
482 ms 8.8.8.164
5 2026-08-26 01:10 639233026412602472
348 ms 8.8.8.164
4 2026-08-26 00:53 639233016064066127
354 ms 8.8.8.164
3 2026-08-26 00:36 639233005922655772
351 ms 8.8.8.164
2 2026-08-26 00:19 639232995672256907
241 ms 8.8.8.164
1 2026-08-26 00:02 639232985300872416
363 ms 8.8.8.164