DNS response history for ns2.server.chess-server.net

ns2.server.chess-server.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-27. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 99 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.server.chess-server.net.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

99 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

87.118.121.126

Most recently resolved hosting IP on selected date

Successful Responses

38

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.server.chess-server.net

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
38 2026-08-27 12:40 639234307007468133
26 ms 87.118.121.126
37 2026-08-27 12:22 639234296664302575
54 ms 87.118.121.126
36 2026-08-27 12:05 639234286253196126
48 ms 87.118.121.126
35 2026-08-27 11:11 639234253963286387
21 ms 87.118.121.126
34 2026-08-27 10:54 639234243654907465
56 ms 87.118.121.126
33 2026-08-27 10:37 639234233269654413
70 ms 87.118.121.126
32 2026-08-27 10:19 639234222943951923
10 ms 87.118.121.126
31 2026-08-27 10:02 639234212558002823
40 ms 87.118.121.126
30 2026-08-27 09:45 639234202117531850
42 ms 87.118.121.126
29 2026-08-27 09:27 639234191649612722
46 ms 87.118.121.126
28 2026-08-27 09:10 639234181105879568
75 ms 87.118.121.126
27 2026-08-27 08:52 639234170713214496
43 ms 87.118.121.126
26 2026-08-27 08:35 639234160341037652
54 ms 87.118.121.126
25 2026-08-27 08:18 639234149799404224
58 ms 87.118.121.126
24 2026-08-27 08:00 639234139553286469
53 ms 87.118.121.126
23 2026-08-27 07:07 639234107183588293
71 ms 87.118.121.126
22 2026-08-27 06:49 639234096905435724
63 ms 87.118.121.126
21 2026-08-27 06:32 639234086579410775
75 ms 87.118.121.126
20 2026-08-27 06:15 639234076291157956
37 ms 87.118.121.126
19 2026-08-27 05:58 639234065981939454
53 ms 87.118.121.126
18 2026-08-27 05:41 639234055548642997
21 ms 87.118.121.126
17 2026-08-27 05:23 639234045267979603
67 ms 87.118.121.126
16 2026-08-27 05:06 639234034999717463
20 ms 87.118.121.126
15 2026-08-27 04:49 639234024739225358
29 ms 87.118.121.126
14 2026-08-27 04:32 639234014311170162
45 ms 87.118.121.126
13 2026-08-27 04:14 639234003806017640
106 ms 87.118.121.126
12 2026-08-27 03:57 639233993356203030
67 ms 87.118.121.126
11 2026-08-27 03:04 639233961301716608
21 ms 87.118.121.126
10 2026-08-27 02:46 639233950834200647
65 ms 87.118.121.126
9 2026-08-27 02:29 639233940431849026
67 ms 87.118.121.126
8 2026-08-27 02:12 639233930110596398
60 ms 87.118.121.126
7 2026-08-27 01:54 639233919705434540
4 ms 87.118.121.126
6 2026-08-27 01:37 639233909452807845
23 ms 87.118.121.126
5 2026-08-27 01:20 639233899096420820
69 ms 87.118.121.126
4 2026-08-27 01:03 639233888707824939
42 ms 87.118.121.126
3 2026-08-27 00:45 639233878461203802
36 ms 87.118.121.126
2 2026-08-27 00:28 639233868060868209
2008 ms 87.118.121.126
1 2026-08-27 00:11 639233857450922991
19 ms 87.118.121.126