DNS response history for ns2.glorydns.com

ns2.glorydns.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-31. For this date, NameServerHistory found 37 DNS check records, 37 successful responses, 0 failed responses, and 391 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.glorydns.com.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

391 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-31 12:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.47.180.115

Most recently resolved hosting IP on selected date

Successful Responses

37

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.glorydns.com

Showing DNS history for 2026-08-31 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
37 2026-08-31 12:11 639237742927117371
353 ms 38.47.180.115
36 2026-08-31 11:54 639237732538256235
209 ms 38.47.180.115
35 2026-08-31 11:37 639237722025682013
174 ms 38.47.180.115
34 2026-08-31 11:19 639237711568720101
357 ms 38.47.180.115
33 2026-08-31 11:02 639237701119461876
349 ms 38.47.180.115
32 2026-08-31 10:44 639237690759595513
350 ms 38.47.180.115
31 2026-08-31 10:27 639237680122296836
350 ms 38.47.180.115
30 2026-08-31 09:33 639237647999458954
172 ms 38.47.180.115
29 2026-08-31 09:16 639237637680951774
355 ms 38.47.180.115
28 2026-08-31 08:59 639237627437728712
376 ms 38.47.180.115
27 2026-08-31 08:42 639237617127808241
362 ms 38.47.180.115
26 2026-08-31 08:24 639237606990101394
350 ms 38.47.180.115
25 2026-08-31 08:07 639237596595480036
187 ms 38.47.180.115
24 2026-08-31 07:50 639237586261012001
344 ms 38.47.180.115
23 2026-08-31 07:33 639237576047657695
351 ms 38.47.180.115
22 2026-08-31 07:16 639237565832936443
420 ms 38.47.180.115
21 2026-08-31 06:59 639237555466329546
374 ms 38.47.180.115
20 2026-08-31 06:41 639237545032411072
416 ms 38.47.180.115
19 2026-08-31 06:24 639237534469438634
349 ms 38.47.180.115
18 2026-08-31 05:30 639237502279296801
2723 ms 38.47.180.115
17 2026-08-31 05:13 639237492362730124
184 ms 38.47.180.115
16 2026-08-31 04:57 639237482311584319
374 ms 38.47.180.115
15 2026-08-31 04:40 639237472150685594
361 ms 38.47.180.115
14 2026-08-31 04:23 639237462055295430
352 ms 38.47.180.115
13 2026-08-31 04:06 639237452089913890
344 ms 38.47.180.115
12 2026-08-31 03:49 639237441972654103
348 ms 38.47.180.115
11 2026-08-31 03:33 639237432052396478
367 ms 38.47.180.115
10 2026-08-31 03:16 639237422012990851
171 ms 38.47.180.115
9 2026-08-31 02:59 639237411889602012
358 ms 38.47.180.115
8 2026-08-31 02:42 639237401637354221
372 ms 38.47.180.115
7 2026-08-31 02:25 639237391412690360
179 ms 38.47.180.115
6 2026-08-31 01:33 639237359972957132
344 ms 38.47.180.115
5 2026-08-31 01:16 639237350032183979
351 ms 38.47.180.115
4 2026-08-31 00:59 639237340111452066
195 ms 38.47.180.115
3 2026-08-31 00:43 639237329967272514
349 ms 38.47.180.115
2 2026-08-31 00:26 639237319916508151
188 ms 38.47.180.115
1 2026-08-31 00:09 639237309944877243
723 ms 38.47.180.115