DNS response history for ns2.ingecom.co

ns2.ingecom.co 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 38 DNS check records, 37 successful responses, 1 failed responses, and 334 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.ingecom.co.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

334 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

169.197.91.242

Most recently resolved hosting IP on selected date

Successful Responses

37

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.ingecom.co

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
38 2026-08-25 13:12 639232597643611557
117 ms 169.197.91.242
37 2026-08-25 12:54 639232587225721862
245 ms 169.197.91.242
36 2026-08-25 12:37 639232576780683689
247 ms 169.197.91.242
35 2026-08-25 12:20 639232566381512620
2153 ms 169.197.91.242
34 2026-08-25 12:02 639232556111768563
128 ms 169.197.91.242
33 2026-08-25 11:45 639232545839529039
252 ms 169.197.91.242
32 2026-08-25 11:28 639232535349285207
264 ms 169.197.91.242
31 2026-08-25 11:11 639232524938080723
166 ms 169.197.91.242
30 2026-08-25 10:17 639232492740373468
232 ms 169.197.91.242
29 2026-08-25 10:00 639232482235303141
118 ms 169.197.91.242
28 2026-08-25 09:42 639232471861770303
115 ms 169.197.91.242
27 2026-08-25 09:25 639232461630217327
243 ms 169.197.91.242
26 2026-08-25 09:08 639232451282965990
5 ms 169.197.91.242
25 2026-08-25 08:50 639232440814614938
134 ms 169.197.91.242
24 2026-08-25 08:33 639232430410720425
120 ms 169.197.91.242
23 2026-08-25 08:16 639232420003096185
243 ms 169.197.91.242
22 2026-08-25 07:58 639232409467287444
123 ms 169.197.91.242
21 2026-08-25 07:41 639232399077195997
2008 ms 169.197.91.242
20 2026-08-25 07:24 639232388731528337
136 ms 169.197.91.242
19 2026-08-25 07:06 639232378288598612
236 ms 169.197.91.242
18 2026-08-25 06:13 639232346196373643
171 ms 169.197.91.242
17 2026-08-25 05:56 639232336112370741
10 ms 169.197.91.242
16 2026-08-25 05:39 639232326146508970
241 ms 169.197.91.242
15 2026-08-25 05:23 639232316189381720
238 ms 169.197.91.242
14 2026-08-25 05:06 639232306217998913
155 ms 169.197.91.242
13 2026-08-25 04:49 639232296255744174
139 ms 169.197.91.242
12 2026-08-25 04:33 639232286095760789
244 ms 169.197.91.242
11 2026-08-25 04:16 639232276086186273
233 ms 169.197.91.242
10 2026-08-25 03:59 639232265900986425
235 ms 169.197.91.242
9 2026-08-25 03:42 639232255723518075
236 ms 169.197.91.242
8 2026-08-25 03:25 639232245484452890
235 ms 169.197.91.242
7 2026-08-25 03:08 639232235157175331
11 ms 169.197.91.242
6 2026-08-25 02:14 639232203197189095
-
5 2026-08-25 01:57 639232192844564298
2140 ms 169.197.91.242
4 2026-08-25 01:40 639232182496008942
238 ms 169.197.91.242
3 2026-08-25 01:23 639232172197053132
115 ms 169.197.91.242
2 2026-08-25 00:29 639232140250307418
155 ms 169.197.91.242
1 2026-08-25 00:12 639232129927860324
289 ms 169.197.91.242