DNS response history for ns2.goictc.link

ns2.goictc.link 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 30 DNS check records, 30 successful responses, 0 failed responses, and 304 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.goictc.link.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

3.33.188.145

Most recently resolved hosting IP on selected date

Successful Responses

30

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.goictc.link

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
30 2026-08-25 10:11 639232492740373468
32 ms 3.33.188.145
29 2026-08-25 09:53 639232482235303141
29 ms 3.33.188.145
28 2026-08-25 09:36 639232471861770303
33 ms 3.33.188.145
27 2026-08-25 09:19 639232461630217327
101 ms 3.33.188.145
26 2026-08-25 09:02 639232451282965990
34 ms 3.33.188.145
25 2026-08-25 08:44 639232440814614938
2016 ms 207.174.61.1
24 2026-08-25 08:27 639232430410720425
18 ms 207.174.61.1
23 2026-08-25 08:10 639232420003096185
47 ms 3.33.188.145
22 2026-08-25 07:52 639232409467287444
32 ms 3.33.188.145
21 2026-08-25 07:35 639232399077195997
33 ms 207.174.61.1
20 2026-08-25 07:17 639232388731528337
29 ms 3.33.188.145
19 2026-08-25 07:00 639232378288598612
34 ms 3.33.188.145
18 2026-08-25 06:07 639232346196373643
44 ms 3.33.188.145
17 2026-08-25 05:50 639232336112370741
27 ms 3.33.188.145
16 2026-08-25 05:33 639232326146508970
27 ms 3.33.188.145
15 2026-08-25 05:17 639232316189381720
4027 ms 207.174.61.1
14 2026-08-25 05:00 639232306217998913
29 ms 3.33.188.145
13 2026-08-25 04:43 639232296255744174
55 ms 3.33.188.145
12 2026-08-25 04:26 639232286095760789
13 ms 3.33.188.145
11 2026-08-25 04:10 639232276086186273
16 ms 3.33.188.145
10 2026-08-25 03:53 639232265900986425
43 ms 3.33.188.145
9 2026-08-25 03:36 639232255723518075
165 ms 207.174.61.1
8 2026-08-25 03:19 639232245484452890
63 ms 207.174.61.1
7 2026-08-25 03:02 639232235157175331
29 ms 3.33.188.145
6 2026-08-25 02:08 639232203197189095
31 ms 3.33.188.145
5 2026-08-25 01:51 639232192844564298
38 ms 3.33.188.145
4 2026-08-25 01:34 639232182496008942
2019 ms 3.33.188.145
3 2026-08-25 01:17 639232172197053132
29 ms 3.33.188.145
2 2026-08-25 00:23 639232140250307418
19 ms 3.33.188.145
1 2026-08-25 00:06 639232129927860324
23 ms 3.33.188.145