DNS response history for vegas2.biglasvegasseocompany.com

vegas2.biglasvegasseocompany.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-25. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 338 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 vegas2.biglasvegasseocompany.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

338 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.87.210.5

Most recently resolved hosting IP on selected date

Successful Responses

33

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 vegas2.biglasvegasseocompany.com

Showing DNS history for 2026-08-25 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
33 2026-08-25 11:45 639232545839529039
215 ms 199.87.210.5
32 2026-08-25 11:27 639232535349285207
200 ms 199.87.210.5
31 2026-08-25 11:10 639232524938080723
55 ms 199.87.210.5
30 2026-08-25 10:16 639232492740373468
12 ms 199.87.210.5
29 2026-08-25 09:59 639232482235303141
217 ms 199.87.210.5
28 2026-08-25 09:41 639232471861770303
212 ms 199.87.210.5
27 2026-08-25 09:24 639232461630217327
8 ms 199.87.210.5
26 2026-08-25 09:07 639232451282965990
210 ms 199.87.210.5
25 2026-08-25 08:50 639232440814614938
118 ms 199.87.210.5
24 2026-08-25 08:32 639232430410720425
212 ms 199.87.210.5
23 2026-08-25 08:15 639232420003096185
162 ms 199.87.210.5
22 2026-08-25 07:58 639232409467287444
208 ms 199.87.210.5
21 2026-08-25 07:40 639232399077195997
176 ms 199.87.210.5
20 2026-08-25 07:23 639232388731528337
198 ms 199.87.210.5
19 2026-08-25 07:05 639232378288598612
211 ms 199.87.210.5
18 2026-08-25 06:12 639232346196373643
194 ms 199.87.210.5
17 2026-08-25 05:55 639232336112370741
55 ms 199.87.210.5
16 2026-08-25 05:38 639232326146508970
209 ms 199.87.210.5
15 2026-08-25 05:22 639232316189381720
203 ms 199.87.210.5
14 2026-08-25 05:05 639232306217998913
205 ms 199.87.210.5
13 2026-08-25 04:49 639232296255744174
4 ms 199.87.210.5
12 2026-08-25 04:32 639232286095760789
25 ms 199.87.210.5
11 2026-08-25 04:15 639232276086186273
204 ms 199.87.210.5
10 2026-08-25 03:58 639232265900986425
199 ms 199.87.210.5
9 2026-08-25 03:41 639232255723518075
2193 ms 199.87.210.5
8 2026-08-25 03:24 639232245484452890
2282 ms 199.87.210.5
7 2026-08-25 03:07 639232235157175331
101 ms 199.87.210.5
6 2026-08-25 02:14 639232203197189095
213 ms 199.87.210.5
5 2026-08-25 01:56 639232192844564298
144 ms 199.87.210.5
4 2026-08-25 01:39 639232182496008942
93 ms 199.87.210.5
3 2026-08-25 01:22 639232172197053132
107 ms 199.87.210.5
2 2026-08-25 00:29 639232140250307418
2097 ms 199.87.210.5
1 2026-08-25 00:12 639232129927860324
221 ms 199.87.210.5