DNS response history for ns2.proredline.com

ns2.proredline.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-26. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 217 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.proredline.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

217 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

169.58.34.148

Most recently resolved hosting IP on selected date

Successful Responses

30

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

Showing DNS history for 2026-08-26 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
30 2026-08-26 09:45 639233339545274518
124 ms 169.58.34.148
29 2026-08-26 09:27 639233329214918079
91 ms 169.58.34.148
28 2026-08-26 09:10 639233318749762337
14 ms 169.58.34.148
27 2026-08-26 08:53 639233308387917838
31 ms 169.58.34.148
26 2026-08-26 08:35 639233297961740122
126 ms 169.58.34.148
25 2026-08-26 08:18 639233287487159094
1535 ms 169.58.34.148
24 2026-08-26 08:00 639233276995531707
62 ms 169.58.34.148
23 2026-08-26 07:43 639233266521568229
1038 ms 169.58.34.148
22 2026-08-26 07:25 639233256081047431
36 ms 169.58.34.148
21 2026-08-26 06:31 639233223620132921
35 ms 169.58.34.148
20 2026-08-26 06:14 639233213287814244
51 ms 169.58.34.148
19 2026-08-26 05:57 639233202925983161
38 ms 169.58.34.148
18 2026-08-26 05:40 639233192644780696
97 ms 169.58.34.148
17 2026-08-26 05:22 639233182401183833
37 ms 169.58.34.148
16 2026-08-26 05:05 639233172074181051
19 ms 169.58.34.148
15 2026-08-26 04:48 639233161808421455
285 ms 169.58.34.148
14 2026-08-26 04:31 639233151357344052
37 ms 169.58.34.148
13 2026-08-26 04:14 639233141034116946
52 ms 169.58.34.148
12 2026-08-26 03:57 639233130828334142
41 ms 169.58.34.148
11 2026-08-26 03:39 639233120373450007
2009 ms 169.58.34.148
10 2026-08-26 03:22 639233110066216193
93 ms 169.58.34.148
9 2026-08-26 02:29 639233078065410564
33 ms 169.58.34.148
8 2026-08-26 02:12 639233067787457832
31 ms 169.58.34.148
7 2026-08-26 01:54 639233057501801162
35 ms 169.58.34.148
6 2026-08-26 01:37 639233047089431703
44 ms 169.58.34.148
5 2026-08-26 01:20 639233036754790688
141 ms 169.58.34.148
4 2026-08-26 01:03 639233026412602472
31 ms 169.58.34.148
3 2026-08-26 00:45 639233016064066127
270 ms 169.58.34.148
2 2026-08-26 00:28 639233005922655772
45 ms 169.58.34.148
1 2026-08-26 00:11 639232995672256907
33 ms 169.58.34.148