DNS response history for ns2.glowvision.tv

ns2.glowvision.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-25. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 408 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.glowvision.tv.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

408 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

50.6.229.127

Most recently resolved hosting IP on selected date

Successful Responses

39

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

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
39 2026-08-25 13:26 639232608016476376
100 ms 50.6.229.127
38 2026-08-25 13:09 639232597643611557
102 ms 50.6.229.127
37 2026-08-25 12:51 639232587225721862
214 ms 50.6.229.127
36 2026-08-25 12:34 639232576780683689
223 ms 50.6.229.127
35 2026-08-25 12:17 639232566381512620
7 ms 50.6.229.127
34 2026-08-25 11:59 639232556111768563
107 ms 50.6.229.127
33 2026-08-25 11:42 639232545839529039
198 ms 50.6.229.127
32 2026-08-25 11:25 639232535349285207
205 ms 50.6.229.127
31 2026-08-25 11:08 639232524938080723
215 ms 50.6.229.127
30 2026-08-25 10:14 639232492740373468
212 ms 50.6.229.127
29 2026-08-25 09:57 639232482235303141
230 ms 50.6.229.127
28 2026-08-25 09:39 639232471861770303
10 ms 50.6.229.127
27 2026-08-25 09:22 639232461630217327
207 ms 50.6.229.127
26 2026-08-25 09:05 639232451282965990
9 ms 50.6.229.127
25 2026-08-25 08:47 639232440814614938
200 ms 50.6.229.127
24 2026-08-25 08:30 639232430410720425
33 ms 50.6.229.127
23 2026-08-25 08:13 639232420003096185
222 ms 50.6.229.127
22 2026-08-25 07:55 639232409467287444
203 ms 50.6.229.127
21 2026-08-25 07:38 639232399077195997
200 ms 50.6.229.127
20 2026-08-25 07:21 639232388731528337
2126 ms 50.6.229.127
19 2026-08-25 07:03 639232378288598612
128 ms 50.6.229.127
18 2026-08-25 06:10 639232346196373643
201 ms 50.6.229.127
17 2026-08-25 05:53 639232336112370741
2118 ms 50.6.229.127
16 2026-08-25 05:36 639232326146508970
200 ms 50.6.229.127
15 2026-08-25 05:20 639232316189381720
85 ms 50.6.229.127
14 2026-08-25 05:03 639232306217998913
200 ms 50.6.229.127
13 2026-08-25 04:46 639232296255744174
7 ms 50.6.229.127
12 2026-08-25 04:30 639232286095760789
202 ms 50.6.229.127
11 2026-08-25 04:13 639232276086186273
205 ms 50.6.229.127
10 2026-08-25 03:56 639232265900986425
2025 ms 50.6.229.127
9 2026-08-25 03:39 639232255723518075
199 ms 50.6.229.127
8 2026-08-25 03:22 639232245484452890
101 ms 50.6.229.127
7 2026-08-25 03:05 639232235157175331
4123 ms 50.6.229.127
6 2026-08-25 02:11 639232203197189095
218 ms 50.6.229.127
5 2026-08-25 01:54 639232192844564298
102 ms 50.6.229.127
4 2026-08-25 01:37 639232182496008942
238 ms 50.6.229.127
3 2026-08-25 01:20 639232172197053132
109 ms 50.6.229.127
2 2026-08-25 00:26 639232140250307418
201 ms 50.6.229.127
1 2026-08-25 00:09 639232129927860324
238 ms 50.6.229.127