DNS response history for ns2.webcom.nc

ns2.webcom.nc 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 37 DNS check records, 37 successful responses, 0 failed responses, and 542 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.webcom.nc.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

542 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.171.68.68

Most recently resolved hosting IP on selected date

Successful Responses

37

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.webcom.nc

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
37 2026-08-25 12:42 639232576780683689
704 ms 202.171.68.68
36 2026-08-25 12:25 639232566381512620
691 ms 202.171.68.68
35 2026-08-25 12:07 639232556111768563
346 ms 202.171.68.68
34 2026-08-25 11:50 639232545839529039
341 ms 202.171.68.68
33 2026-08-25 11:33 639232535349285207
683 ms 202.171.68.68
32 2026-08-25 11:15 639232524938080723
689 ms 202.171.68.68
31 2026-08-25 10:22 639232492740373468
358 ms 202.171.68.68
30 2026-08-25 10:05 639232482235303141
700 ms 202.171.68.68
29 2026-08-25 09:47 639232471861770303
679 ms 202.171.68.68
28 2026-08-25 09:30 639232461630217327
342 ms 202.171.68.68
27 2026-08-25 09:13 639232451282965990
687 ms 202.171.68.68
26 2026-08-25 08:55 639232440814614938
700 ms 202.171.68.68
25 2026-08-25 08:38 639232430410720425
3 ms 202.171.68.68
24 2026-08-25 08:21 639232420003096185
692 ms 202.171.68.68
23 2026-08-25 08:03 639232409467287444
707 ms 202.171.68.68
22 2026-08-25 07:46 639232399077195997
343 ms 202.171.68.68
21 2026-08-25 07:28 639232388731528337
690 ms 202.171.68.68
20 2026-08-25 07:11 639232378288598612
1051 ms 202.171.68.68
19 2026-08-25 06:17 639232346196373643
3 ms 202.171.68.68
18 2026-08-25 06:00 639232336112370741
691 ms 202.171.68.68
17 2026-08-25 05:44 639232326146508970
692 ms 202.171.68.68
16 2026-08-25 05:27 639232316189381720
683 ms 202.171.68.68
15 2026-08-25 05:11 639232306217998913
352 ms 202.171.68.68
14 2026-08-25 04:54 639232296255744174
697 ms 202.171.68.68
13 2026-08-25 04:37 639232286095760789
344 ms 202.171.68.68
12 2026-08-25 04:20 639232276086186273
701 ms 202.171.68.68
11 2026-08-25 04:04 639232265900986425
339 ms 202.171.68.68
10 2026-08-25 03:47 639232255723518075
339 ms 202.171.68.68
9 2026-08-25 03:30 639232245484452890
342 ms 202.171.68.68
8 2026-08-25 03:12 639232235157175331
686 ms 202.171.68.68
7 2026-08-25 02:19 639232203197189095
344 ms 202.171.68.68
6 2026-08-25 02:02 639232192844564298
692 ms 202.171.68.68
5 2026-08-25 01:45 639232182496008942
688 ms 202.171.68.68
4 2026-08-25 01:27 639232172197053132
680 ms 202.171.68.68
3 2026-08-25 00:34 639232140250307418
688 ms 202.171.68.68
2 2026-08-25 00:17 639232129927860324
3 ms 202.171.68.68
1 2026-08-25 00:00 639232119551972438
684 ms 202.171.68.68