DNS response history for ns2.gridalynx.com

ns2.gridalynx.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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 485 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.gridalynx.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

485 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

34.101.177.113

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 ns2.gridalynx.com

Showing DNS history for 2026-08-30 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-30 11:51 639236867916029489
317 ms 34.101.177.113
35 2026-08-30 11:34 639236858088772005
326 ms 34.101.177.113
34 2026-08-30 11:18 639236848158742395
474 ms 34.101.177.113
33 2026-08-30 11:01 639236838137395574
322 ms 34.101.177.113
32 2026-08-30 10:45 639236827967386881
314 ms 34.101.177.113
31 2026-08-30 10:27 639236817708615077
2341 ms 34.101.177.113
30 2026-08-30 09:34 639236785770651804
322 ms 34.101.177.113
29 2026-08-30 09:18 639236775820686373
320 ms 34.101.177.113
28 2026-08-30 09:01 639236765768339082
324 ms 34.101.177.113
27 2026-08-30 08:44 639236755602384085
308 ms 34.101.177.113
26 2026-08-30 08:27 639236745600094925
314 ms 34.101.177.113
25 2026-08-30 08:10 639236735311262753
312 ms 34.101.177.113
24 2026-08-30 07:53 639236724996745235
326 ms 34.101.177.113
23 2026-08-30 07:36 639236714839899761
319 ms 34.101.177.113
22 2026-08-30 07:19 639236704748431488
2177 ms 34.101.177.113
21 2026-08-30 07:02 639236694430128550
310 ms 34.101.177.113
20 2026-08-30 06:45 639236684143292417
321 ms 34.101.177.113
19 2026-08-30 06:28 639236673972499943
460 ms 34.101.177.113
18 2026-08-30 05:35 639236642126522802
328 ms 34.101.177.113
17 2026-08-30 05:18 639236632183518198
326 ms 34.101.177.113
16 2026-08-30 05:02 639236622289312589
321 ms 34.101.177.113
15 2026-08-30 04:45 639236612490676525
322 ms 34.101.177.113
14 2026-08-30 04:29 639236602582494852
314 ms 34.101.177.113
13 2026-08-30 04:12 639236592511706469
318 ms 34.101.177.113
12 2026-08-30 03:55 639236582441006869
325 ms 34.101.177.113
11 2026-08-30 03:39 639236572478785089
322 ms 34.101.177.113
10 2026-08-30 03:22 639236562556749999
323 ms 34.101.177.113
9 2026-08-30 03:05 639236552353482281
318 ms 34.101.177.113
8 2026-08-30 02:48 639236542188881607
181 ms 34.101.177.113
7 2026-08-30 02:31 639236531885440105
325 ms 34.101.177.113
6 2026-08-30 01:38 639236499922985383
310 ms 34.101.177.113
5 2026-08-30 01:21 639236489713594431
311 ms 34.101.177.113
4 2026-08-30 01:04 639236479750443901
2244 ms 34.101.177.113
3 2026-08-30 00:47 639236469719936375
320 ms 34.101.177.113
2 2026-08-30 00:31 639236459579244885
320 ms 34.101.177.113
1 2026-08-30 00:14 639236449582837549
319 ms 34.101.177.113