DNS response history for ns2.globaldc.com

ns2.globaldc.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-25. For this date, NameServerHistory found 39 DNS check records, 39 successful responses, 0 failed responses, and 368 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.globaldc.com.
Records on Selected Date

39

Historical checks stored for this nameserver on selected date

Average Latency

368 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:30

All timestamps shown in UTC

Latest Resolved IP on Selected Date

154.127.52.71

Most recently resolved hosting IP on selected date

Successful Responses

39

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

Showing DNS history for 2026-08-25 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
39 2026-08-25 13:30 639232608016476376
115 ms 154.127.52.71
38 2026-08-25 13:12 639232597643611557
242 ms 154.127.52.71
37 2026-08-25 12:55 639232587225721862
235 ms 154.127.52.71
36 2026-08-25 12:38 639232576780683689
123 ms 154.127.52.71
35 2026-08-25 12:20 639232566381512620
118 ms 154.127.52.71
34 2026-08-25 12:03 639232556111768563
248 ms 154.127.52.71
33 2026-08-25 11:46 639232545839529039
244 ms 154.127.52.71
32 2026-08-25 11:29 639232535349285207
122 ms 154.127.52.71
31 2026-08-25 11:11 639232524938080723
235 ms 154.127.52.71
30 2026-08-25 10:17 639232492740373468
236 ms 154.127.52.71
29 2026-08-25 10:00 639232482235303141
2115 ms 154.127.52.71
28 2026-08-25 09:43 639232471861770303
121 ms 154.127.52.71
27 2026-08-25 09:26 639232461630217327
232 ms 154.127.52.71
26 2026-08-25 09:08 639232451282965990
242 ms 154.127.52.71
25 2026-08-25 08:51 639232440814614938
241 ms 154.127.52.71
24 2026-08-25 08:34 639232430410720425
232 ms 154.127.52.71
23 2026-08-25 08:16 639232420003096185
235 ms 154.127.52.71
22 2026-08-25 07:59 639232409467287444
236 ms 154.127.52.71
21 2026-08-25 07:42 639232399077195997
256 ms 154.127.52.71
20 2026-08-25 07:24 639232388731528337
126 ms 154.127.52.71
19 2026-08-25 07:07 639232378288598612
133 ms 154.127.52.71
18 2026-08-25 06:13 639232346196373643
230 ms 154.127.52.71
17 2026-08-25 05:56 639232336112370741
119 ms 154.127.52.71
16 2026-08-25 05:40 639232326146508970
119 ms 154.127.52.71
15 2026-08-25 05:23 639232316189381720
240 ms 154.127.52.71
14 2026-08-25 05:07 639232306217998913
229 ms 154.127.52.71
13 2026-08-25 04:50 639232296255744174
123 ms 154.127.52.71
12 2026-08-25 04:33 639232286095760789
237 ms 154.127.52.71
11 2026-08-25 04:16 639232276086186273
2116 ms 154.127.52.71
10 2026-08-25 03:59 639232265900986425
116 ms 154.127.52.71
9 2026-08-25 03:43 639232255723518075
1337 ms 154.127.52.71
8 2026-08-25 03:25 639232245484452890
116 ms 154.127.52.71
7 2026-08-25 03:08 639232235157175331
245 ms 154.127.52.71
6 2026-08-25 02:15 639232203197189095
205 ms 154.127.52.71
5 2026-08-25 01:58 639232192844564298
120 ms 154.127.52.71
4 2026-08-25 01:41 639232182496008942
2122 ms 154.127.52.71
3 2026-08-25 01:23 639232172197053132
247 ms 154.127.52.71
2 2026-08-25 00:30 639232140250307418
121 ms 154.127.52.71
1 2026-08-25 00:13 639232129927860324
234 ms 154.127.52.71