DNS response history for two.gamelink.com

two.gamelink.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-28. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 228 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 two.gamelink.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

228 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 12:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

66.11.152.205

Most recently resolved hosting IP on selected date

Successful Responses

30

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 two.gamelink.com

Showing DNS history for 2026-08-28 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
30 2026-08-28 12:38 639235174453894956
12 ms 66.11.152.205
29 2026-08-28 12:20 639235163898672622
19 ms 66.11.152.205
28 2026-08-28 11:27 639235132147470568
28 ms 66.11.152.205
27 2026-08-28 11:10 639235121907744088
21 ms 66.11.152.205
26 2026-08-28 10:53 639235111428014262
26 ms 66.11.152.205
25 2026-08-28 10:35 639235100921813626
24 ms 66.11.152.205
24 2026-08-28 09:42 639235068670703481
17 ms 66.11.152.205
23 2026-08-28 09:24 639235058337459445
94 ms 66.11.152.205
22 2026-08-28 09:07 639235047825109146
12 ms 66.11.152.205
21 2026-08-28 08:49 639235037383229033
42 ms 66.11.152.205
20 2026-08-28 07:57 639235005619242711
72 ms 66.11.152.205
19 2026-08-28 07:39 639234995310346584
29 ms 66.11.152.205
18 2026-08-28 07:22 639234984946548933
54 ms 66.11.152.205
17 2026-08-28 07:05 639234974608077290
18 ms 66.11.152.205
16 2026-08-28 06:11 639234942529845595
25 ms 66.11.152.205
15 2026-08-28 05:54 639234932259126627
2019 ms 66.11.152.205
14 2026-08-28 05:37 639234921916735988
36 ms 66.11.152.205
13 2026-08-28 05:20 639234911470038027
7 ms 66.11.152.205
12 2026-08-28 04:27 639234879588411654
23 ms 66.11.152.205
11 2026-08-28 04:09 639234869341589104
18 ms 66.11.152.205
10 2026-08-28 03:52 639234859012216675
23 ms 66.11.152.205
9 2026-08-28 03:35 639234848695364934
40 ms 66.11.152.205
8 2026-08-28 02:42 639234816952458162
9 ms 66.11.152.205
7 2026-08-28 02:25 639234806773081598
20 ms 66.11.152.205
6 2026-08-28 02:08 639234796382955255
16 ms 66.11.152.205
5 2026-08-28 01:51 639234786015782563
22 ms 66.11.152.205
4 2026-08-28 00:57 639234753811917646
2026 ms 66.11.152.205
3 2026-08-28 00:40 639234743739767811
27 ms 66.11.152.205
2 2026-08-28 00:23 639234733372362811
2056 ms 66.11.152.205
1 2026-08-28 00:06 639234723048550337
17 ms 66.11.152.205