DNS response history for in.cname.com

in.cname.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-26. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 496 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 in.cname.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

496 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:22

All timestamps shown in UTC

Latest Resolved IP on Selected Date

204.203.92.130

Most recently resolved hosting IP on selected date

Successful Responses

32

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 in.cname.com

Showing DNS history for 2026-08-26 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
32 2026-08-26 10:22 639233360361507238
330 ms 204.203.92.130
31 2026-08-26 10:05 639233350067824371
7 ms 204.203.92.130
30 2026-08-26 09:48 639233339545274518
309 ms 204.203.92.130
29 2026-08-26 09:30 639233329214918079
339 ms 204.203.92.130
28 2026-08-26 09:13 639233318749762337
168 ms 204.203.92.130
27 2026-08-26 08:56 639233308387917838
314 ms 204.203.92.130
26 2026-08-26 08:38 639233297961740122
313 ms 204.203.92.130
25 2026-08-26 08:21 639233287487159094
311 ms 204.203.92.130
24 2026-08-26 08:04 639233276995531707
314 ms 204.203.92.130
23 2026-08-26 07:46 639233266521568229
2162 ms 204.203.92.130
22 2026-08-26 07:29 639233256081047431
314 ms 204.203.92.130
21 2026-08-26 06:35 639233223620132921
2031 ms 204.203.92.130
20 2026-08-26 06:17 639233213287814244
297 ms 204.203.92.130
19 2026-08-26 06:00 639233202925983161
185 ms 204.203.92.130
18 2026-08-26 05:43 639233192644780696
309 ms 204.203.92.130
17 2026-08-26 05:26 639233182401183833
309 ms 204.203.92.130
16 2026-08-26 05:09 639233172074181051
8 ms 204.203.92.130
15 2026-08-26 04:51 639233161808421455
168 ms 204.203.92.130
14 2026-08-26 04:34 639233151357344052
2159 ms 204.203.92.130
13 2026-08-26 04:17 639233141034116946
2008 ms 204.203.92.130
12 2026-08-26 04:00 639233130828334142
311 ms 204.203.92.130
11 2026-08-26 03:43 639233120373450007
311 ms 204.203.92.130
10 2026-08-26 03:25 639233110066216193
312 ms 204.203.92.130
9 2026-08-26 02:32 639233078065410564
315 ms 204.203.92.130
8 2026-08-26 02:15 639233067787457832
311 ms 204.203.92.130
7 2026-08-26 01:58 639233057501801162
315 ms 204.203.92.130
6 2026-08-26 01:40 639233047089431703
177 ms 204.203.92.130
5 2026-08-26 01:23 639233036754790688
310 ms 204.203.92.130
4 2026-08-26 01:06 639233026412602472
309 ms 204.203.92.130
3 2026-08-26 00:49 639233016064066127
312 ms 204.203.92.130
2 2026-08-26 00:32 639233005922655772
314 ms 204.203.92.130
1 2026-08-26 00:15 639232995672256907
205 ms 204.203.92.130