DNS response history for ns3.gamelife.biz

ns3.gamelife.biz 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-27. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 269 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 ns3.gamelife.biz.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

269 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:02

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.59.170.201

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 ns3.gamelife.biz

Showing DNS history for 2026-08-27 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-27 12:02 639234286253196126
83 ms 108.59.170.201
35 2026-08-27 11:08 639234253963286387
9 ms 108.59.170.201
34 2026-08-27 10:51 639234243654907465
157 ms 108.59.170.201
33 2026-08-27 10:33 639234233269654413
41 ms 108.59.170.201
32 2026-08-27 10:16 639234222943951923
101 ms 108.59.170.201
31 2026-08-27 09:59 639234212558002823
25 ms 108.59.170.201
30 2026-08-27 09:42 639234202117531850
47 ms 108.59.170.201
29 2026-08-27 09:24 639234191649612722
60 ms 108.59.170.201
28 2026-08-27 09:07 639234181105879568
3606 ms 108.59.170.201
27 2026-08-27 08:49 639234170713214496
53 ms 108.59.170.201
26 2026-08-27 08:32 639234160341037652
2082 ms 108.59.170.201
25 2026-08-27 08:15 639234149799404224
54 ms 108.59.170.201
24 2026-08-27 07:57 639234139553286469
55 ms 108.59.170.201
23 2026-08-27 07:03 639234107183588293
37 ms 108.59.170.201
22 2026-08-27 06:46 639234096905435724
2023 ms 108.59.170.201
21 2026-08-27 06:29 639234086579410775
39 ms 108.59.170.201
20 2026-08-27 06:12 639234076291157956
58 ms 108.59.170.201
19 2026-08-27 05:55 639234065981939454
52 ms 108.59.170.201
18 2026-08-27 05:38 639234055548642997
34 ms 108.59.170.201
17 2026-08-27 05:20 639234045267979603
35 ms 108.59.170.201
16 2026-08-27 05:03 639234034999717463
96 ms 108.59.170.201
15 2026-08-27 04:46 639234024739225358
31 ms 108.59.170.201
14 2026-08-27 04:29 639234014311170162
111 ms 108.59.170.201
13 2026-08-27 04:11 639234003806017640
24 ms 108.59.170.201
12 2026-08-27 03:54 639233993356203030
7 ms 108.59.170.201
11 2026-08-27 03:00 639233961301716608
80 ms 108.59.170.201
10 2026-08-27 02:43 639233950834200647
43 ms 108.59.170.201
9 2026-08-27 02:26 639233940431849026
63 ms 108.59.170.201
8 2026-08-27 02:08 639233930110596398
19 ms 108.59.170.201
7 2026-08-27 01:51 639233919705434540
100 ms 108.59.170.201
6 2026-08-27 01:34 639233909452807845
145 ms 108.59.170.201
5 2026-08-27 01:17 639233899096420820
39 ms 108.59.170.201
4 2026-08-27 00:59 639233888707824939
91 ms 108.59.170.201
3 2026-08-27 00:42 639233878461203802
33 ms 108.59.170.201
2 2026-08-27 00:25 639233868060868209
119 ms 108.59.170.201
1 2026-08-27 00:07 639233857450922991
17 ms 108.59.170.201