DNS response history for ns1.fibudns.com

ns1.fibudns.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 33 DNS check records, 32 successful responses, 1 failed responses, and 161 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.fibudns.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

161 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:40

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.135.82.23

Most recently resolved hosting IP on selected date

Successful Responses

32

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns1.fibudns.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
33 2026-08-26 10:40 639233370841350248
73 ms 78.135.82.23
32 2026-08-26 10:23 639233360361507238
129 ms 78.135.82.23
31 2026-08-26 10:05 639233350067824371
118 ms 78.135.82.23
30 2026-08-26 09:48 639233339545274518
117 ms 78.135.82.23
29 2026-08-26 09:30 639233329214918079
2098 ms 78.135.82.23
28 2026-08-26 09:13 639233318749762337
149 ms 78.135.82.23
27 2026-08-26 08:56 639233308387917838
119 ms 78.135.82.23
26 2026-08-26 08:38 639233297961740122
71 ms 78.135.82.23
25 2026-08-26 08:21 639233287487159094
64 ms 78.135.82.23
24 2026-08-26 08:04 639233276995531707
-
23 2026-08-26 07:46 639233266521568229
118 ms 78.135.82.23
22 2026-08-26 07:29 639233256081047431
116 ms 78.135.82.23
21 2026-08-26 06:35 639233223620132921
66 ms 78.135.82.23
20 2026-08-26 06:17 639233213287814244
60 ms 78.135.82.23
19 2026-08-26 06:00 639233202925983161
147 ms 78.135.82.23
18 2026-08-26 05:43 639233192644780696
60 ms 78.135.82.23
17 2026-08-26 05:26 639233182401183833
119 ms 78.135.82.23
16 2026-08-26 05:09 639233172074181051
27 ms 78.135.82.23
15 2026-08-26 04:51 639233161808421455
117 ms 78.135.82.23
14 2026-08-26 04:34 639233151357344052
158 ms 78.135.82.23
13 2026-08-26 04:17 639233141034116946
119 ms 78.135.82.23
12 2026-08-26 04:00 639233130828334142
66 ms 78.135.82.23
11 2026-08-26 03:43 639233120373450007
87 ms 78.135.82.23
10 2026-08-26 03:25 639233110066216193
60 ms 78.135.82.23
9 2026-08-26 02:32 639233078065410564
159 ms 78.135.82.23
8 2026-08-26 02:15 639233067787457832
59 ms 78.135.82.23
7 2026-08-26 01:58 639233057501801162
118 ms 78.135.82.23
6 2026-08-26 01:40 639233047089431703
70 ms 78.135.82.23
5 2026-08-26 01:23 639233036754790688
59 ms 78.135.82.23
4 2026-08-26 01:06 639233026412602472
118 ms 78.135.82.23
3 2026-08-26 00:49 639233016064066127
120 ms 78.135.82.23
2 2026-08-26 00:32 639233005922655772
121 ms 78.135.82.23
1 2026-08-26 00:15 639232995672256907
83 ms 78.135.82.23