DNS response history for ns2.ridgeleap.com

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

34

Historical checks stored for this nameserver on selected date

Average Latency

579 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

45.154.204.16

Most recently resolved hosting IP on selected date

Successful Responses

34

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.ridgeleap.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
34 2026-08-26 10:44 639233370841350248
398 ms 45.154.204.16
33 2026-08-26 10:27 639233360361507238
397 ms 45.154.204.16
32 2026-08-26 10:10 639233350067824371
396 ms 45.154.204.16
31 2026-08-26 09:53 639233339545274518
399 ms 45.154.204.16
30 2026-08-26 09:35 639233329214918079
406 ms 45.154.204.16
29 2026-08-26 09:18 639233318749762337
394 ms 45.154.204.16
28 2026-08-26 09:00 639233308387917838
399 ms 45.154.204.16
27 2026-08-26 08:43 639233297961740122
397 ms 45.154.204.16
26 2026-08-26 08:26 639233287487159094
396 ms 45.154.204.16
25 2026-08-26 08:08 639233276995531707
400 ms 45.154.204.16
24 2026-08-26 07:51 639233266521568229
403 ms 45.154.204.16
23 2026-08-26 07:33 639233256081047431
396 ms 45.154.204.16
22 2026-08-26 06:39 639233223620132921
436 ms 45.154.204.16
21 2026-08-26 06:22 639233213287814244
421 ms 45.154.204.16
20 2026-08-26 06:05 639233202925983161
431 ms 45.154.204.16
19 2026-08-26 05:47 639233192644780696
436 ms 45.154.204.16
18 2026-08-26 05:30 639233182401183833
437 ms 45.154.204.16
17 2026-08-26 05:13 639233172074181051
440 ms 45.154.204.16
16 2026-08-26 04:56 639233161808421455
464 ms 45.154.204.16
15 2026-08-26 04:39 639233151357344052
1820 ms 45.154.204.16
14 2026-08-26 04:21 639233141034116946
130 ms 45.154.204.16
13 2026-08-26 04:04 639233130828334142
1868 ms 45.154.204.16
12 2026-08-26 03:47 639233120373450007
1858 ms 45.154.204.16
11 2026-08-26 03:30 639233110066216193
1862 ms 45.154.204.16
10 2026-08-26 02:37 639233078065410564
423 ms 45.154.204.16
9 2026-08-26 02:19 639233067787457832
433 ms 45.154.204.16
8 2026-08-26 02:02 639233057501801162
423 ms 45.154.204.16
7 2026-08-26 01:45 639233047089431703
429 ms 45.154.204.16
6 2026-08-26 01:28 639233036754790688
429 ms 45.154.204.16
5 2026-08-26 01:11 639233026412602472
435 ms 45.154.204.16
4 2026-08-26 00:53 639233016064066127
440 ms 45.154.204.16
3 2026-08-26 00:36 639233005922655772
435 ms 45.154.204.16
2 2026-08-26 00:19 639232995672256907
430 ms 45.154.204.16
1 2026-08-26 00:02 639232985300872416
437 ms 45.154.204.16