DNS response history for ns2.apreporting.com

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

31

Historical checks stored for this nameserver on selected date

Average Latency

132 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

51.68.149.200

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

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
31 2026-08-25 11:08 639232524938080723
53 ms 51.68.149.200
30 2026-08-25 10:14 639232492740373468
198 ms 51.68.149.200
29 2026-08-25 09:57 639232482235303141
164 ms 51.68.149.200
28 2026-08-25 09:39 639232471861770303
30 ms 51.68.149.200
27 2026-08-25 09:22 639232461630217327
158 ms 51.68.149.200
26 2026-08-25 09:05 639232451282965990
135 ms 51.68.149.200
25 2026-08-25 08:48 639232440814614938
160 ms 51.68.149.200
24 2026-08-25 08:31 639232430410720425
165 ms 51.68.149.200
23 2026-08-25 08:13 639232420003096185
21 ms 51.68.149.200
22 2026-08-25 07:56 639232409467287444
125 ms 51.68.149.200
21 2026-08-25 07:38 639232399077195997
163 ms 51.68.149.200
20 2026-08-25 07:21 639232388731528337
127 ms 51.68.149.200
19 2026-08-25 07:04 639232378288598612
173 ms 51.68.149.200
18 2026-08-25 06:10 639232346196373643
167 ms 51.68.149.200
17 2026-08-25 05:53 639232336112370741
163 ms 51.68.149.200
16 2026-08-25 05:37 639232326146508970
179 ms 51.68.149.200
15 2026-08-25 05:20 639232316189381720
163 ms 51.68.149.200
14 2026-08-25 05:04 639232306217998913
112 ms 51.68.149.200
13 2026-08-25 04:47 639232296255744174
166 ms 51.68.149.200
12 2026-08-25 04:30 639232286095760789
155 ms 51.68.149.200
11 2026-08-25 04:13 639232276086186273
108 ms 51.68.149.200
10 2026-08-25 03:56 639232265900986425
117 ms 51.68.149.200
9 2026-08-25 03:39 639232255723518075
13 ms 51.68.149.200
8 2026-08-25 03:22 639232245484452890
169 ms 51.68.149.200
7 2026-08-25 03:05 639232235157175331
163 ms 51.68.149.200
6 2026-08-25 02:12 639232203197189095
162 ms 51.68.149.200
5 2026-08-25 01:55 639232192844564298
223 ms 51.68.149.200
4 2026-08-25 01:37 639232182496008942
176 ms 51.68.149.200
3 2026-08-25 01:20 639232172197053132
105 ms 51.68.149.200
2 2026-08-25 00:27 639232140250307418
14 ms 51.68.149.200
1 2026-08-25 00:10 639232129927860324
62 ms 51.68.149.200