DNS response history for ns2.infocomltd.com

ns2.infocomltd.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 565 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.infocomltd.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

565 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

221.120.96.42

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.infocomltd.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:07 639232556111768563
353 ms 221.120.96.42
34 2026-08-25 11:50 639232545839529039
358 ms 221.120.96.42
33 2026-08-25 11:33 639232535349285207
364 ms 221.120.96.42
32 2026-08-25 11:15 639232524938080723
808 ms 221.120.96.42
31 2026-08-25 10:21 639232492740373468
804 ms 221.120.96.42
30 2026-08-25 10:04 639232482235303141
352 ms 221.120.96.42
29 2026-08-25 09:47 639232471861770303
799 ms 221.120.96.42
28 2026-08-25 09:30 639232461630217327
800 ms 221.120.96.42
27 2026-08-25 09:12 639232451282965990
2424 ms 221.120.96.42
26 2026-08-25 08:55 639232440814614938
804 ms 221.120.96.42
25 2026-08-25 08:38 639232430410720425
802 ms 221.120.96.42
24 2026-08-25 08:20 639232420003096185
815 ms 221.120.96.42
23 2026-08-25 08:03 639232409467287444
795 ms 221.120.96.42
22 2026-08-25 07:46 639232399077195997
801 ms 221.120.96.42
21 2026-08-25 07:28 639232388731528337
802 ms 221.120.96.42
20 2026-08-25 07:11 639232378288598612
356 ms 221.120.96.42
19 2026-08-25 06:17 639232346196373643
3 ms 221.120.96.42
18 2026-08-25 06:00 639232336112370741
3 ms 221.120.96.42
17 2026-08-25 05:44 639232326146508970
3 ms 221.120.96.42
16 2026-08-25 05:27 639232316189381720
4 ms 221.120.96.42
15 2026-08-25 05:10 639232306217998913
2 ms 221.120.96.42
14 2026-08-25 04:54 639232296255744174
389 ms 221.120.96.42
13 2026-08-25 04:37 639232286095760789
803 ms 221.120.96.42
12 2026-08-25 04:20 639232276086186273
797 ms 221.120.96.42
11 2026-08-25 04:03 639232265900986425
3 ms 221.120.96.42
10 2026-08-25 03:46 639232255723518075
802 ms 221.120.96.42
9 2026-08-25 03:29 639232245484452890
799 ms 221.120.96.42
8 2026-08-25 03:12 639232235157175331
804 ms 221.120.96.42
7 2026-08-25 02:19 639232203197189095
353 ms 221.120.96.42
6 2026-08-25 02:02 639232192844564298
805 ms 221.120.96.42
5 2026-08-25 01:44 639232182496008942
802 ms 221.120.96.42
4 2026-08-25 01:27 639232172197053132
4 ms 221.120.96.42
3 2026-08-25 00:34 639232140250307418
354 ms 221.120.96.42
2 2026-08-25 00:17 639232129927860324
4 ms 221.120.96.42
1 2026-08-25 00:00 639232119551972438
812 ms 221.120.96.42