DNS response history for ns2.aprotex.com

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

33

Historical checks stored for this nameserver on selected date

Average Latency

615 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:49

All timestamps shown in UTC

Latest Resolved IP on Selected Date

98.187.177.229

Most recently resolved hosting IP on selected date

Successful Responses

33

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.aprotex.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
33 2026-08-25 11:49 639232545839529039
709 ms 98.187.177.229
32 2026-08-25 11:32 639232535349285207
956 ms 98.187.177.229
31 2026-08-25 11:14 639232524938080723
696 ms 98.187.177.229
30 2026-08-25 10:20 639232492740373468
144 ms 98.187.177.229
29 2026-08-25 10:03 639232482235303141
721 ms 98.187.177.229
28 2026-08-25 09:46 639232471861770303
4 ms 98.187.177.229
27 2026-08-25 09:28 639232461630217327
5 ms 98.187.177.229
26 2026-08-25 09:11 639232451282965990
563 ms 98.187.177.229
25 2026-08-25 08:54 639232440814614938
703 ms 98.187.177.229
24 2026-08-25 08:37 639232430410720425
156 ms 98.187.177.229
23 2026-08-25 08:19 639232420003096185
163 ms 98.187.177.229
22 2026-08-25 08:02 639232409467287444
958 ms 98.187.177.229
21 2026-08-25 07:44 639232399077195997
684 ms 98.187.177.229
20 2026-08-25 07:27 639232388731528337
144 ms 98.187.177.229
19 2026-08-25 07:10 639232378288598612
285 ms 98.187.177.229
18 2026-08-25 06:16 639232346196373643
170 ms 98.187.177.229
17 2026-08-25 05:59 639232336112370741
1093 ms 98.187.177.229
16 2026-08-25 05:42 639232326146508970
289 ms 98.187.177.229
15 2026-08-25 05:26 639232316189381720
157 ms 98.187.177.229
14 2026-08-25 05:09 639232306217998913
590 ms 98.187.177.229
13 2026-08-25 04:53 639232296255744174
2148 ms 98.187.177.229
12 2026-08-25 04:36 639232286095760789
291 ms 98.187.177.229
11 2026-08-25 04:19 639232276086186273
751 ms 98.187.177.229
10 2026-08-25 04:02 639232265900986425
702 ms 98.187.177.229
9 2026-08-25 03:45 639232255723518075
144 ms 98.187.177.229
8 2026-08-25 03:28 639232245484452890
704 ms 98.187.177.229
7 2026-08-25 03:11 639232235157175331
135 ms 98.187.177.229
6 2026-08-25 02:18 639232203197189095
712 ms 98.187.177.229
5 2026-08-25 02:01 639232192844564298
164 ms 98.187.177.229
4 2026-08-25 01:43 639232182496008942
319 ms 98.187.177.229
3 2026-08-25 01:26 639232172197053132
715 ms 98.187.177.229
2 2026-08-25 00:33 639232140250307418
155 ms 98.187.177.229
1 2026-08-25 00:16 639232129927860324
4153 ms 98.187.177.229