DNS response history for gremlin.lasvegas.net

gremlin.lasvegas.net 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 28 DNS check records, 28 successful responses, 0 failed responses, and 309 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 gremlin.lasvegas.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

309 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

64.250.224.6

Most recently resolved hosting IP on selected date

Successful Responses

28

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 gremlin.lasvegas.net

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
28 2026-08-26 09:13 639233318749762337
164 ms 64.250.224.6
27 2026-08-26 08:56 639233308387917838
317 ms 64.250.224.6
26 2026-08-26 08:38 639233297961740122
305 ms 64.250.224.6
25 2026-08-26 08:21 639233287487159094
308 ms 64.250.224.6
24 2026-08-26 08:03 639233276995531707
311 ms 64.250.224.6
23 2026-08-26 07:46 639233266521568229
12 ms 64.250.224.6
22 2026-08-26 07:28 639233256081047431
114 ms 64.250.224.6
21 2026-08-26 06:34 639233223620132921
303 ms 64.250.224.6
20 2026-08-26 06:17 639233213287814244
302 ms 64.250.224.6
19 2026-08-26 06:00 639233202925983161
5 ms 64.250.224.6
18 2026-08-26 05:42 639233192644780696
306 ms 64.250.224.6
17 2026-08-26 05:25 639233182401183833
502 ms 64.250.224.6
16 2026-08-26 05:08 639233172074181051
152 ms 64.250.224.6
15 2026-08-26 04:51 639233161808421455
2309 ms 64.250.224.6
14 2026-08-26 04:34 639233151357344052
304 ms 64.250.224.6
13 2026-08-26 04:17 639233141034116946
305 ms 64.250.224.6
12 2026-08-26 03:59 639233130828334142
302 ms 64.250.224.6
11 2026-08-26 03:42 639233120373450007
303 ms 64.250.224.6
10 2026-08-26 03:25 639233110066216193
202 ms 64.250.224.6
9 2026-08-26 02:32 639233078065410564
302 ms 64.250.224.6
8 2026-08-26 02:14 639233067787457832
300 ms 64.250.224.6
7 2026-08-26 01:57 639233057501801162
301 ms 64.250.224.6
6 2026-08-26 01:40 639233047089431703
6 ms 64.250.224.6
5 2026-08-26 01:23 639233036754790688
9 ms 64.250.224.6
4 2026-08-26 01:06 639233026412602472
163 ms 64.250.224.6
3 2026-08-26 00:48 639233016064066127
302 ms 64.250.224.6
2 2026-08-26 00:31 639233005922655772
152 ms 64.250.224.6
1 2026-08-26 00:14 639232995672256907
304 ms 64.250.224.6