DNS response history for ns2.lcccorp.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

284 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:04

All timestamps shown in UTC

Latest Resolved IP on Selected Date

70.33.130.68

Most recently resolved hosting IP on selected date

Successful Responses

31

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

Showing DNS history for 2026-08-27 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
31 2026-08-27 10:04 639234212558002823
220 ms 70.33.130.68
30 2026-08-27 09:47 639234202117531850
210 ms 70.33.130.68
29 2026-08-27 09:29 639234191649612722
107 ms 70.33.130.68
28 2026-08-27 09:12 639234181105879568
106 ms 70.33.130.68
27 2026-08-27 08:54 639234170713214496
105 ms 70.33.130.68
26 2026-08-27 08:37 639234160341037652
212 ms 70.33.130.68
25 2026-08-27 08:20 639234149799404224
213 ms 70.33.130.68
24 2026-08-27 08:02 639234139553286469
215 ms 70.33.130.68
23 2026-08-27 07:09 639234107183588293
217 ms 70.33.130.68
22 2026-08-27 06:51 639234096905435724
210 ms 70.33.130.68
21 2026-08-27 06:34 639234086579410775
212 ms 70.33.130.68
20 2026-08-27 06:17 639234076291157956
13 ms 70.33.130.68
19 2026-08-27 06:00 639234065981939454
103 ms 70.33.130.68
18 2026-08-27 05:43 639234055548642997
204 ms 70.33.130.68
17 2026-08-27 05:25 639234045267979603
3 ms 70.33.130.68
16 2026-08-27 05:08 639234034999717463
201 ms 70.33.130.68
15 2026-08-27 04:51 639234024739225358
219 ms 70.33.130.68
14 2026-08-27 04:34 639234014311170162
205 ms 70.33.130.68
13 2026-08-27 04:16 639234003806017640
203 ms 70.33.130.68
12 2026-08-27 03:59 639233993356203030
203 ms 70.33.130.68
11 2026-08-27 03:06 639233961301716608
201 ms 70.33.130.68
10 2026-08-27 02:48 639233950834200647
2099 ms 70.33.130.68
9 2026-08-27 02:31 639233940431849026
218 ms 70.33.130.68
8 2026-08-27 02:14 639233930110596398
2013 ms 70.33.130.68
7 2026-08-27 01:56 639233919705434540
207 ms 70.33.130.68
6 2026-08-27 01:39 639233909452807845
202 ms 70.33.130.68
5 2026-08-27 01:22 639233899096420820
33 ms 70.33.130.68
4 2026-08-27 01:05 639233888707824939
205 ms 70.33.130.68
3 2026-08-27 00:47 639233878461203802
9 ms 70.33.130.68
2 2026-08-27 00:30 639233868060868209
31 ms 70.33.130.68
1 2026-08-27 00:13 639233857450922991
208 ms 70.33.130.68