DNS response history for c2.core-dns.net

c2.core-dns.net 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 32 DNS check records, 32 successful responses, 0 failed responses, and 200 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 c2.core-dns.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

200 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

199.102.46.228

Most recently resolved hosting IP on selected date

Successful Responses

32

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 c2.core-dns.net

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
32 2026-08-27 10:14 639234222943951923
6 ms 199.102.46.228
31 2026-08-27 09:57 639234212558002823
19 ms 199.102.46.228
30 2026-08-27 09:39 639234202117531850
6 ms 199.102.46.228
29 2026-08-27 09:22 639234191649612722
11 ms 199.102.46.228
28 2026-08-27 09:04 639234181105879568
2054 ms 199.102.46.228
27 2026-08-27 08:47 639234170713214496
11 ms 199.102.46.228
26 2026-08-27 08:30 639234160341037652
25 ms 199.102.46.228
25 2026-08-27 08:12 639234149799404224
10 ms 199.102.46.228
24 2026-08-27 07:55 639234139553286469
20 ms 199.102.46.228
23 2026-08-27 07:01 639234107183588293
6 ms 199.102.46.228
22 2026-08-27 06:44 639234096905435724
5 ms 199.102.46.228
21 2026-08-27 06:27 639234086579410775
10 ms 199.102.46.228
20 2026-08-27 06:10 639234076291157956
5 ms 199.102.46.228
19 2026-08-27 05:53 639234065981939454
5 ms 199.102.46.228
18 2026-08-27 05:35 639234055548642997
5 ms 199.102.46.228
17 2026-08-27 05:18 639234045267979603
5 ms 199.102.46.228
16 2026-08-27 05:01 639234034999717463
12 ms 199.102.46.228
15 2026-08-27 04:44 639234024739225358
4 ms 199.102.46.228
14 2026-08-27 04:27 639234014311170162
9 ms 199.102.46.228
13 2026-08-27 04:09 639234003806017640
5 ms 199.102.46.228
12 2026-08-27 03:51 639233993356203030
14 ms 199.102.46.228
11 2026-08-27 02:58 639233961301716608
4049 ms 199.102.46.228
10 2026-08-27 02:41 639233950834200647
4 ms 199.102.46.228
9 2026-08-27 02:23 639233940431849026
26 ms 199.102.46.228
8 2026-08-27 02:06 639233930110596398
5 ms 199.102.46.228
7 2026-08-27 01:49 639233919705434540
9 ms 199.102.46.228
6 2026-08-27 01:32 639233909452807845
6 ms 199.102.46.228
5 2026-08-27 01:15 639233899096420820
5 ms 199.102.46.228
4 2026-08-27 00:57 639233888707824939
17 ms 199.102.46.228
3 2026-08-27 00:40 639233878461203802
7 ms 199.102.46.228
2 2026-08-27 00:23 639233868060868209
5 ms 199.102.46.228
1 2026-08-27 00:05 639233857450922991
5 ms 199.102.46.228