DNS response history for h2ns2.grohost.com

h2ns2.grohost.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 28 DNS check records, 28 successful responses, 0 failed responses, and 101 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 h2ns2.grohost.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

101 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:39

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.79.247.147

Most recently resolved hosting IP on selected date

Successful Responses

28

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 h2ns2.grohost.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
28 2026-08-25 09:39 639232471861770303
157 ms 217.79.247.147
27 2026-08-25 09:22 639232461630217327
150 ms 217.79.247.147
26 2026-08-25 09:05 639232451282965990
30 ms 217.79.247.147
25 2026-08-25 08:47 639232440814614938
30 ms 217.79.247.147
24 2026-08-25 08:30 639232430410720425
164 ms 217.79.247.147
23 2026-08-25 08:13 639232420003096185
178 ms 217.79.247.147
22 2026-08-25 07:55 639232409467287444
294 ms 217.79.247.147
21 2026-08-25 07:38 639232399077195997
244 ms 217.79.247.147
20 2026-08-25 07:21 639232388731528337
166 ms 217.79.247.147
19 2026-08-25 07:03 639232378288598612
149 ms 217.79.247.147
18 2026-08-25 06:10 639232346196373643
4 ms 217.79.247.147
17 2026-08-25 05:53 639232336112370741
43 ms 217.79.247.147
16 2026-08-25 05:36 639232326146508970
7 ms 217.79.247.147
15 2026-08-25 05:20 639232316189381720
41 ms 217.79.247.147
14 2026-08-25 05:03 639232306217998913
6 ms 217.79.247.147
13 2026-08-25 04:47 639232296255744174
165 ms 217.79.247.147
12 2026-08-25 04:30 639232286095760789
149 ms 217.79.247.147
11 2026-08-25 04:13 639232276086186273
301 ms 217.79.247.147
10 2026-08-25 03:56 639232265900986425
16 ms 217.79.247.147
9 2026-08-25 03:39 639232255723518075
24 ms 217.79.247.147
8 2026-08-25 03:22 639232245484452890
5 ms 217.79.247.147
7 2026-08-25 03:05 639232235157175331
5 ms 217.79.247.147
6 2026-08-25 02:11 639232203197189095
29 ms 217.79.247.147
5 2026-08-25 01:54 639232192844564298
18 ms 217.79.247.147
4 2026-08-25 01:37 639232182496008942
292 ms 217.79.247.147
3 2026-08-25 01:20 639232172197053132
5 ms 217.79.247.147
2 2026-08-25 00:26 639232140250307418
12 ms 217.79.247.147
1 2026-08-25 00:09 639232129927860324
151 ms 217.79.247.147