DNS response history for ns2.cotrage.com

ns2.cotrage.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 34 DNS check records, 34 successful responses, 0 failed responses, and 274 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.cotrage.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

213.136.88.236

Most recently resolved hosting IP on selected date

Successful Responses

34

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.cotrage.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
34 2026-08-25 11:56 639232556111768563
20 ms 213.136.88.236
33 2026-08-25 11:39 639232545839529039
84 ms 213.136.88.236
32 2026-08-25 11:22 639232535349285207
152 ms 213.136.88.236
31 2026-08-25 11:04 639232524938080723
167 ms 213.136.88.236
30 2026-08-25 10:10 639232492740373468
94 ms 213.136.88.236
29 2026-08-25 09:53 639232482235303141
205 ms 213.136.88.236
28 2026-08-25 09:36 639232471861770303
107 ms 213.136.88.236
27 2026-08-25 09:19 639232461630217327
2023 ms 213.136.88.236
26 2026-08-25 09:01 639232451282965990
58 ms 213.136.88.236
25 2026-08-25 08:44 639232440814614938
44 ms 213.136.88.236
24 2026-08-25 08:27 639232430410720425
161 ms 213.136.88.236
23 2026-08-25 08:09 639232420003096185
160 ms 213.136.88.236
22 2026-08-25 07:52 639232409467287444
63 ms 213.136.88.236
21 2026-08-25 07:34 639232399077195997
43 ms 213.136.88.236
20 2026-08-25 07:17 639232388731528337
189 ms 213.136.88.236
19 2026-08-25 07:00 639232378288598612
57 ms 213.136.88.236
18 2026-08-25 06:06 639232346196373643
71 ms 213.136.88.236
17 2026-08-25 05:49 639232336112370741
2022 ms 213.136.88.236
16 2026-08-25 05:33 639232326146508970
96 ms 213.136.88.236
15 2026-08-25 05:16 639232316189381720
74 ms 213.136.88.236
14 2026-08-25 05:00 639232306217998913
53 ms 213.136.88.236
13 2026-08-25 04:43 639232296255744174
215 ms 213.136.88.236
12 2026-08-25 04:26 639232286095760789
71 ms 213.136.88.236
11 2026-08-25 04:09 639232276086186273
113 ms 213.136.88.236
10 2026-08-25 03:52 639232265900986425
87 ms 213.136.88.236
9 2026-08-25 03:35 639232255723518075
177 ms 213.136.88.236
8 2026-08-25 03:18 639232245484452890
70 ms 213.136.88.236
7 2026-08-25 03:01 639232235157175331
112 ms 213.136.88.236
6 2026-08-25 02:08 639232203197189095
2025 ms 213.136.88.236
5 2026-08-25 01:51 639232192844564298
241 ms 213.136.88.236
4 2026-08-25 01:34 639232182496008942
60 ms 213.136.88.236
3 2026-08-25 01:16 639232172197053132
125 ms 213.136.88.236
2 2026-08-25 00:23 639232140250307418
57 ms 213.136.88.236
1 2026-08-25 00:06 639232129927860324
37 ms 213.136.88.236