DNS response history for ns2.viviporn.tv

ns2.viviporn.tv 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 36 DNS check records, 35 successful responses, 1 failed responses, and 175 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.viviporn.tv.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

175 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 12:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

62.122.168.8

Most recently resolved hosting IP on selected date

Successful Responses

35

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.viviporn.tv

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
36 2026-08-26 12:05 639233424567558554
82 ms 62.122.168.8
35 2026-08-26 11:47 639233414056832719
49 ms 62.122.168.8
34 2026-08-26 11:30 639233403515141099
23 ms 62.122.168.8
33 2026-08-26 10:35 639233370841350248
62 ms 62.122.168.8
32 2026-08-26 10:18 639233360361507238
62 ms 62.122.168.8
31 2026-08-26 10:00 639233350067824371
45 ms 62.122.168.8
30 2026-08-26 09:43 639233339545274518
29 ms 62.122.168.8
29 2026-08-26 09:26 639233329214918079
144 ms 62.122.168.8
28 2026-08-26 09:08 639233318749762337
56 ms 62.122.168.8
27 2026-08-26 08:51 639233308387917838
46 ms 62.122.168.8
26 2026-08-26 08:34 639233297961740122
25 ms 62.122.168.8
25 2026-08-26 08:16 639233287487159094
42 ms 62.122.168.8
24 2026-08-26 07:59 639233276995531707
132 ms 62.122.168.8
23 2026-08-26 07:41 639233266521568229
46 ms 62.122.168.8
22 2026-08-26 07:24 639233256081047431
2075 ms 62.122.168.8
21 2026-08-26 06:30 639233223620132921
42 ms 62.122.168.8
20 2026-08-26 06:12 639233213287814244
2031 ms 62.122.168.8
19 2026-08-26 05:55 639233202925983161
49 ms 62.122.168.8
18 2026-08-26 05:38 639233192644780696
50 ms 62.122.168.8
17 2026-08-26 05:21 639233182401183833
36 ms 62.122.168.8
16 2026-08-26 05:04 639233172074181051
108 ms 62.122.168.8
15 2026-08-26 04:47 639233161808421455
42 ms 62.122.168.8
14 2026-08-26 04:29 639233151357344052
40 ms 62.122.168.8
13 2026-08-26 04:12 639233141034116946
72 ms 62.122.168.8
12 2026-08-26 03:55 639233130828334142
53 ms 62.122.168.8
11 2026-08-26 03:38 639233120373450007
44 ms 62.122.168.8
10 2026-08-26 03:20 639233110066216193
45 ms 62.122.168.8
9 2026-08-26 02:27 639233078065410564
58 ms 62.122.168.8
8 2026-08-26 02:10 639233067787457832
-
7 2026-08-26 01:53 639233057501801162
68 ms 62.122.168.8
6 2026-08-26 01:35 639233047089431703
91 ms 62.122.168.8
5 2026-08-26 01:18 639233036754790688
49 ms 62.122.168.8
4 2026-08-26 01:01 639233026412602472
45 ms 62.122.168.8
3 2026-08-26 00:44 639233016064066127
20 ms 62.122.168.8
2 2026-08-26 00:27 639233005922655772
84 ms 62.122.168.8
1 2026-08-26 00:10 639232995672256907
173 ms 62.122.168.8