DNS response history for ns2.vegas-solution.com

ns2.vegas-solution.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 36 DNS check records, 36 successful responses, 0 failed responses, and 577 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.vegas-solution.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

577 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

222.122.129.149

Most recently resolved hosting IP on selected date

Successful Responses

36

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.vegas-solution.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
36 2026-08-26 11:58 639233414056832719
580 ms 222.122.129.149
35 2026-08-26 11:40 639233403515141099
569 ms 222.122.129.149
34 2026-08-26 10:45 639233370841350248
576 ms 222.122.129.149
33 2026-08-26 10:28 639233360361507238
585 ms 222.122.129.149
32 2026-08-26 10:11 639233350067824371
565 ms 222.122.129.149
31 2026-08-26 09:54 639233339545274518
602 ms 222.122.129.149
30 2026-08-26 09:36 639233329214918079
563 ms 222.122.129.149
29 2026-08-26 09:19 639233318749762337
581 ms 222.122.129.149
28 2026-08-26 09:01 639233308387917838
605 ms 222.122.129.149
27 2026-08-26 08:44 639233297961740122
581 ms 222.122.129.149
26 2026-08-26 08:27 639233287487159094
566 ms 222.122.129.149
25 2026-08-26 08:09 639233276995531707
565 ms 222.122.129.149
24 2026-08-26 07:52 639233266521568229
560 ms 222.122.129.149
23 2026-08-26 07:34 639233256081047431
569 ms 222.122.129.149
22 2026-08-26 06:40 639233223620132921
578 ms 222.122.129.149
21 2026-08-26 06:23 639233213287814244
581 ms 222.122.129.149
20 2026-08-26 06:06 639233202925983161
562 ms 222.122.129.149
19 2026-08-26 05:48 639233192644780696
572 ms 222.122.129.149
18 2026-08-26 05:31 639233182401183833
564 ms 222.122.129.149
17 2026-08-26 05:14 639233172074181051
582 ms 222.122.129.149
16 2026-08-26 04:57 639233161808421455
573 ms 222.122.129.149
15 2026-08-26 04:40 639233151357344052
583 ms 222.122.129.149
14 2026-08-26 04:22 639233141034116946
590 ms 222.122.129.149
13 2026-08-26 04:05 639233130828334142
592 ms 222.122.129.149
12 2026-08-26 03:48 639233120373450007
606 ms 222.122.129.149
11 2026-08-26 03:31 639233110066216193
553 ms 222.122.129.149
10 2026-08-26 02:37 639233078065410564
563 ms 222.122.129.149
9 2026-08-26 02:20 639233067787457832
578 ms 222.122.129.149
8 2026-08-26 02:03 639233057501801162
560 ms 222.122.129.149
7 2026-08-26 01:46 639233047089431703
593 ms 222.122.129.149
6 2026-08-26 01:29 639233036754790688
580 ms 222.122.129.149
5 2026-08-26 01:11 639233026412602472
579 ms 222.122.129.149
4 2026-08-26 00:54 639233016064066127
573 ms 222.122.129.149
3 2026-08-26 00:37 639233005922655772
600 ms 222.122.129.149
2 2026-08-26 00:20 639232995672256907
567 ms 222.122.129.149
1 2026-08-26 00:03 639232985300872416
578 ms 222.122.129.149