DNS response history for ns2.vipnet.org

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

34

Historical checks stored for this nameserver on selected date

Average Latency

555 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.107.32.105

Most recently resolved hosting IP on selected date

Successful Responses

34

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.vipnet.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
34 2026-08-26 10:45 639233370841350248
581 ms 199.107.32.105
33 2026-08-26 10:27 639233360361507238
360 ms 199.107.32.105
32 2026-08-26 10:10 639233350067824371
587 ms 199.107.32.105
31 2026-08-26 09:53 639233339545274518
541 ms 199.107.32.105
30 2026-08-26 09:35 639233329214918079
220 ms 199.107.32.105
29 2026-08-26 09:18 639233318749762337
112 ms 199.107.32.105
28 2026-08-26 09:01 639233308387917838
1027 ms 199.107.32.105
27 2026-08-26 08:43 639233297961740122
113 ms 199.107.32.105
26 2026-08-26 08:26 639233287487159094
118 ms 199.107.32.105
25 2026-08-26 08:08 639233276995531707
569 ms 199.107.32.105
24 2026-08-26 07:51 639233266521568229
965 ms 199.107.32.105
23 2026-08-26 07:33 639233256081047431
579 ms 199.107.32.105
22 2026-08-26 06:39 639233223620132921
718 ms 199.107.32.105
21 2026-08-26 06:22 639233213287814244
948 ms 199.107.32.105
20 2026-08-26 06:05 639233202925983161
461 ms 199.107.32.105
19 2026-08-26 05:48 639233192644780696
2236 ms 199.107.32.105
18 2026-08-26 05:30 639233182401183833
220 ms 199.107.32.105
17 2026-08-26 05:13 639233172074181051
921 ms 199.107.32.105
16 2026-08-26 04:56 639233161808421455
562 ms 199.107.32.105
15 2026-08-26 04:39 639233151357344052
221 ms 199.107.32.105
14 2026-08-26 04:22 639233141034116946
464 ms 199.107.32.105
13 2026-08-26 04:04 639233130828334142
580 ms 199.107.32.105
12 2026-08-26 03:47 639233120373450007
109 ms 199.107.32.105
11 2026-08-26 03:30 639233110066216193
692 ms 199.107.32.105
10 2026-08-26 02:37 639233078065410564
220 ms 199.107.32.105
9 2026-08-26 02:20 639233067787457832
457 ms 199.107.32.105
8 2026-08-26 02:02 639233057501801162
595 ms 199.107.32.105
7 2026-08-26 01:45 639233047089431703
329 ms 199.107.32.105
6 2026-08-26 01:28 639233036754790688
448 ms 199.107.32.105
5 2026-08-26 01:11 639233026412602472
597 ms 199.107.32.105
4 2026-08-26 00:53 639233016064066127
506 ms 199.107.32.105
3 2026-08-26 00:36 639233005922655772
890 ms 199.107.32.105
2 2026-08-26 00:19 639232995672256907
233 ms 199.107.32.105
1 2026-08-26 00:02 639232985300872416
704 ms 199.107.32.105