DNS response history for ns2.shamcom.com

ns2.shamcom.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-29. For this date, NameServerHistory found 29 DNS check records, 29 successful responses, 0 failed responses, and 147 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.shamcom.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

147 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

93.180.132.123

Most recently resolved hosting IP on selected date

Successful Responses

29

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.shamcom.com

Showing DNS history for 2026-08-29 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
29 2026-08-29 10:26 639235956590882003
83 ms 93.180.132.123
28 2026-08-29 09:33 639235924465736791
75 ms 93.180.132.123
27 2026-08-29 09:16 639235914430611197
78 ms 93.180.132.123
26 2026-08-29 08:59 639235904343784853
81 ms 93.180.132.123
25 2026-08-29 08:43 639235894201078068
52 ms 93.180.132.123
24 2026-08-29 08:26 639235884233447452
59 ms 93.180.132.123
23 2026-08-29 08:09 639235874142207309
47 ms 93.180.132.123
22 2026-08-29 07:52 639235863974652466
101 ms 93.180.132.123
21 2026-08-29 07:35 639235853716243436
78 ms 93.180.132.123
20 2026-08-29 07:18 639235843614494759
61 ms 93.180.132.123
19 2026-08-29 07:01 639235833401459551
3 ms 93.180.132.123
18 2026-08-29 06:44 639235823220464528
98 ms 93.180.132.123
17 2026-08-29 06:27 639235812997510905
68 ms 93.180.132.123
16 2026-08-29 05:34 639235781101962521
27 ms 93.180.132.123
15 2026-08-29 05:17 639235771207673260
85 ms 93.180.132.123
14 2026-08-29 05:01 639235761047429642
58 ms 93.180.132.123
13 2026-08-29 04:44 639235750964347246
2069 ms 93.180.132.123
12 2026-08-29 04:27 639235740923490874
450 ms 93.180.132.123
11 2026-08-29 04:10 639235730842894399
86 ms 93.180.132.123
10 2026-08-29 03:53 639235720760084717
76 ms 93.180.132.123
9 2026-08-29 03:37 639235710843666743
110 ms 93.180.132.123
8 2026-08-29 03:20 639235700733510561
17 ms 93.180.132.123
7 2026-08-29 03:03 639235690509906192
76 ms 93.180.132.123
6 2026-08-29 02:46 639235680156673501
77 ms 93.180.132.123
5 2026-08-29 02:28 639235669720606443
76 ms 93.180.132.123
4 2026-08-29 01:35 639235637451417084
3 ms 93.180.132.123
3 2026-08-29 01:18 639235627307383453
64 ms 93.180.132.123
2 2026-08-29 01:00 639235616906386856
11 ms 93.180.132.123
1 2026-08-29 00:43 639235606582912691
98 ms 93.180.132.123