DNS response history for ns2.triangle-kick.com

ns2.triangle-kick.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 35 DNS check records, 35 successful responses, 0 failed responses, and 416 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.triangle-kick.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

416 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

210.167.23.51

Most recently resolved hosting IP on selected date

Successful Responses

35

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.triangle-kick.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
35 2026-08-25 12:24 639232566381512620
10 ms 210.167.23.51
34 2026-08-25 12:06 639232556111768563
282 ms 210.167.23.51
33 2026-08-25 11:49 639232545839529039
265 ms 210.167.23.51
32 2026-08-25 11:32 639232535349285207
537 ms 210.167.23.51
31 2026-08-25 11:15 639232524938080723
4 ms 210.167.23.51
30 2026-08-25 10:21 639232492740373468
5 ms 210.167.23.51
29 2026-08-25 10:04 639232482235303141
281 ms 210.167.23.51
28 2026-08-25 09:46 639232471861770303
10 ms 210.167.23.51
27 2026-08-25 09:29 639232461630217327
7 ms 210.167.23.51
26 2026-08-25 09:12 639232451282965990
564 ms 210.167.23.51
25 2026-08-25 08:54 639232440814614938
561 ms 210.167.23.51
24 2026-08-25 08:37 639232430410720425
2330 ms 210.167.23.51
23 2026-08-25 08:20 639232420003096185
277 ms 210.167.23.51
22 2026-08-25 08:02 639232409467287444
559 ms 210.167.23.51
21 2026-08-25 07:45 639232399077195997
547 ms 210.167.23.51
20 2026-08-25 07:27 639232388731528337
531 ms 210.167.23.51
19 2026-08-25 07:10 639232378288598612
532 ms 210.167.23.51
18 2026-08-25 06:16 639232346196373643
278 ms 210.167.23.51
17 2026-08-25 06:00 639232336112370741
542 ms 210.167.23.51
16 2026-08-25 05:43 639232326146508970
308 ms 210.167.23.51
15 2026-08-25 05:26 639232316189381720
346 ms 210.167.23.51
14 2026-08-25 05:10 639232306217998913
566 ms 210.167.23.51
13 2026-08-25 04:53 639232296255744174
565 ms 210.167.23.51
12 2026-08-25 04:36 639232286095760789
541 ms 210.167.23.51
11 2026-08-25 04:19 639232276086186273
542 ms 210.167.23.51
10 2026-08-25 04:03 639232265900986425
544 ms 210.167.23.51
9 2026-08-25 03:46 639232255723518075
276 ms 210.167.23.51
8 2026-08-25 03:29 639232245484452890
549 ms 210.167.23.51
7 2026-08-25 03:12 639232235157175331
286 ms 210.167.23.51
6 2026-08-25 02:18 639232203197189095
271 ms 210.167.23.51
5 2026-08-25 02:01 639232192844564298
274 ms 210.167.23.51
4 2026-08-25 01:44 639232182496008942
558 ms 210.167.23.51
3 2026-08-25 01:26 639232172197053132
273 ms 210.167.23.51
2 2026-08-25 00:33 639232140250307418
545 ms 210.167.23.51
1 2026-08-25 00:16 639232129927860324
3 ms 210.167.23.51