DNS response history for ns2.netcorps.com

ns2.netcorps.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 36 DNS check records, 36 successful responses, 0 failed responses, and 300 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.netcorps.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

300 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:58

All timestamps shown in UTC

Latest Resolved IP on Selected Date

204.228.234.15

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 ns2.netcorps.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
36 2026-08-27 11:58 639234286253196126
25 ms 204.228.234.15
35 2026-08-27 11:04 639234253963286387
14 ms 204.228.234.15
34 2026-08-27 10:47 639234243654907465
28 ms 204.228.234.15
33 2026-08-27 10:30 639234233269654413
9 ms 204.228.234.15
32 2026-08-27 10:12 639234222943951923
6 ms 204.228.234.15
31 2026-08-27 09:55 639234212558002823
9 ms 204.228.234.15
30 2026-08-27 09:38 639234202117531850
11 ms 204.228.234.15
29 2026-08-27 09:20 639234191649612722
2020 ms 204.228.234.15
28 2026-08-27 09:03 639234181105879568
20 ms 204.228.234.15
27 2026-08-27 08:45 639234170713214496
20 ms 204.228.234.15
26 2026-08-27 08:28 639234160341037652
48 ms 204.228.234.15
25 2026-08-27 08:11 639234149799404224
31 ms 204.228.234.15
24 2026-08-27 07:54 639234139553286469
12 ms 204.228.234.15
23 2026-08-27 07:00 639234107183588293
13 ms 204.228.234.15
22 2026-08-27 06:42 639234096905435724
48 ms 204.228.234.15
21 2026-08-27 06:25 639234086579410775
47 ms 204.228.234.15
20 2026-08-27 06:08 639234076291157956
18 ms 204.228.234.15
19 2026-08-27 05:51 639234065981939454
17 ms 204.228.234.15
18 2026-08-27 05:34 639234055548642997
2032 ms 204.228.234.15
17 2026-08-27 05:16 639234045267979603
27 ms 204.228.234.15
16 2026-08-27 04:59 639234034999717463
9 ms 204.228.234.15
15 2026-08-27 04:42 639234024739225358
23 ms 204.228.234.15
14 2026-08-27 04:25 639234014311170162
19 ms 204.228.234.15
13 2026-08-27 04:07 639234003806017640
16 ms 204.228.234.15
12 2026-08-27 03:50 639233993356203030
44 ms 204.228.234.15
11 2026-08-27 02:56 639233961301716608
42 ms 204.228.234.15
10 2026-08-27 02:39 639233950834200647
15 ms 204.228.234.15
9 2026-08-27 02:22 639233940431849026
17 ms 204.228.234.15
8 2026-08-27 02:04 639233930110596398
15 ms 204.228.234.15
7 2026-08-27 01:47 639233919705434540
29 ms 204.228.234.15
6 2026-08-27 01:30 639233909452807845
17 ms 204.228.234.15
5 2026-08-27 01:13 639233899096420820
6 ms 204.228.234.15
4 2026-08-27 00:55 639233888707824939
4019 ms 204.228.234.15
3 2026-08-27 00:38 639233878461203802
7 ms 204.228.234.15
2 2026-08-27 00:21 639233868060868209
22 ms 204.228.234.15
1 2026-08-27 00:03 639233857450922991
2036 ms 204.228.234.15