DNS response history for ns1.ridefix.bike

ns1.ridefix.bike 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 34 DNS check records, 34 successful responses, 0 failed responses, and 246 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 ns1.ridefix.bike.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

246 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

91.98.128.4

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 ns1.ridefix.bike

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
34 2026-08-25 12:00 639232556111768563
37 ms 91.98.128.4
33 2026-08-25 11:43 639232545839529039
18 ms 91.98.128.4
32 2026-08-25 11:26 639232535349285207
65 ms 91.98.128.4
31 2026-08-25 11:09 639232524938080723
34 ms 91.98.128.4
30 2026-08-25 10:15 639232492740373468
22 ms 91.98.128.4
29 2026-08-25 09:58 639232482235303141
22 ms 91.98.128.4
28 2026-08-25 09:40 639232471861770303
26 ms 91.98.128.4
27 2026-08-25 09:23 639232461630217327
32 ms 91.98.128.4
26 2026-08-25 09:06 639232451282965990
2031 ms 91.98.128.4
25 2026-08-25 08:48 639232440814614938
169 ms 91.98.128.4
24 2026-08-25 08:31 639232430410720425
326 ms 91.98.128.4
23 2026-08-25 08:14 639232420003096185
17 ms 91.98.128.4
22 2026-08-25 07:56 639232409467287444
420 ms 91.98.128.4
21 2026-08-25 07:39 639232399077195997
33 ms 91.98.128.4
20 2026-08-25 07:22 639232388731528337
21 ms 91.98.128.4
19 2026-08-25 07:04 639232378288598612
237 ms 91.98.128.4
18 2026-08-25 06:11 639232346196373643
179 ms 91.98.128.4
17 2026-08-25 05:54 639232336112370741
22 ms 91.98.128.4
16 2026-08-25 05:37 639232326146508970
2046 ms 91.98.128.4
15 2026-08-25 05:21 639232316189381720
41 ms 91.98.128.4
14 2026-08-25 05:04 639232306217998913
15 ms 91.98.128.4
13 2026-08-25 04:47 639232296255744174
20 ms 91.98.128.4
12 2026-08-25 04:31 639232286095760789
43 ms 91.98.128.4
11 2026-08-25 04:14 639232276086186273
43 ms 91.98.128.4
10 2026-08-25 03:57 639232265900986425
57 ms 91.98.128.4
9 2026-08-25 03:40 639232255723518075
2025 ms 91.98.128.4
8 2026-08-25 03:23 639232245484452890
47 ms 91.98.128.4
7 2026-08-25 03:06 639232235157175331
35 ms 91.98.128.4
6 2026-08-25 02:12 639232203197189095
59 ms 91.98.128.4
5 2026-08-25 01:55 639232192844564298
28 ms 91.98.128.4
4 2026-08-25 01:38 639232182496008942
39 ms 91.98.128.4
3 2026-08-25 01:21 639232172197053132
51 ms 91.98.128.4
2 2026-08-25 00:27 639232140250307418
39 ms 91.98.128.4
1 2026-08-25 00:10 639232129927860324
48 ms 91.98.128.4