DNS response history for ns3.smashsoft.in

ns3.smashsoft.in 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-24. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 486 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 ns3.smashsoft.in.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

486 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 15:19

All timestamps shown in UTC

Latest Resolved IP on Selected Date

49.50.68.101

Most recently resolved hosting IP on selected date

Successful Responses

36

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 ns3.smashsoft.in

Showing DNS history for 2026-08-24 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
36 2026-08-24 15:19 639231807961539652
293 ms 49.50.68.101
35 2026-08-24 15:02 639231797631669865
597 ms 49.50.68.101
34 2026-08-24 14:09 639231765923559455
303 ms 49.50.68.101
33 2026-08-24 13:52 639231755868832964
293 ms 49.50.68.101
32 2026-08-24 13:35 639231745628278877
600 ms 49.50.68.101
31 2026-08-24 13:18 639231735407682062
2378 ms 49.50.68.101
30 2026-08-24 12:25 639231703815441688
3 ms 49.50.68.101
29 2026-08-24 12:09 639231693747052549
308 ms 49.50.68.101
28 2026-08-24 11:52 639231683712487276
300 ms 49.50.68.101
27 2026-08-24 11:35 639231673513573868
595 ms 49.50.68.101
26 2026-08-24 10:42 639231641791249939
305 ms 49.50.68.101
25 2026-08-24 10:26 639231631866211033
293 ms 49.50.68.101
24 2026-08-24 10:09 639231621644955316
631 ms 49.50.68.101
23 2026-08-24 09:52 639231611478799259
4 ms 49.50.68.101
22 2026-08-24 08:59 639231579923718211
3 ms 49.50.68.101
21 2026-08-24 08:42 639231569810702936
297 ms 49.50.68.101
20 2026-08-24 08:25 639231559762411619
296 ms 49.50.68.101
19 2026-08-24 08:09 639231549663595407
631 ms 49.50.68.101
18 2026-08-24 07:16 639231518076817246
6 ms 49.50.68.101
17 2026-08-24 06:59 639231508078650885
4 ms 49.50.68.101
16 2026-08-24 06:43 639231498210697093
302 ms 49.50.68.101
15 2026-08-24 06:26 639231488109699360
612 ms 49.50.68.101
14 2026-08-24 05:34 639231456772510692
316 ms 49.50.68.101
13 2026-08-24 05:17 639231447084631185
608 ms 49.50.68.101
12 2026-08-24 05:01 639231437208519473
614 ms 49.50.68.101
11 2026-08-24 04:44 639231427209627490
605 ms 49.50.68.101
10 2026-08-24 03:52 639231395791246644
3 ms 49.50.68.101
9 2026-08-24 03:36 639231386075551458
3 ms 49.50.68.101
8 2026-08-24 03:20 639231376208713791
3 ms 49.50.68.101
7 2026-08-24 03:03 639231366170589276
4 ms 49.50.68.101
6 2026-08-24 02:10 639231334732159368
307 ms 49.50.68.101
5 2026-08-24 01:54 639231325035670078
614 ms 49.50.68.101
4 2026-08-24 01:38 639231315132253837
344 ms 49.50.68.101
3 2026-08-24 01:21 639231305014280808
293 ms 49.50.68.101
2 2026-08-24 00:28 639231273779380675
380 ms 49.50.68.101
1 2026-08-24 00:13 639231264180839154
4359 ms 49.50.68.101