DNS response history for ns1.birbebek.com

ns1.birbebek.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 376 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.birbebek.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

376 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.21.7.170

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.birbebek.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 11:32 639233403515141099
94 ms 185.21.7.170
33 2026-08-26 10:37 639233370841350248
93 ms 185.21.7.170
32 2026-08-26 10:20 639233360361507238
97 ms 185.21.7.170
31 2026-08-26 10:03 639233350067824371
2073 ms 185.21.7.170
30 2026-08-26 09:45 639233339545274518
8 ms 185.21.7.170
29 2026-08-26 09:28 639233329214918079
94 ms 185.21.7.170
28 2026-08-26 09:11 639233318749762337
113 ms 185.21.7.170
27 2026-08-26 08:53 639233308387917838
97 ms 185.21.7.170
26 2026-08-26 08:36 639233297961740122
2091 ms 185.21.7.170
25 2026-08-26 08:19 639233287487159094
87 ms 185.21.7.170
24 2026-08-26 08:01 639233276995531707
99 ms 185.21.7.170
23 2026-08-26 07:44 639233266521568229
46 ms 185.21.7.170
22 2026-08-26 07:26 639233256081047431
7 ms 185.21.7.170
21 2026-08-26 06:32 639233223620132921
82 ms 185.21.7.170
20 2026-08-26 06:15 639233213287814244
92 ms 185.21.7.170
19 2026-08-26 05:58 639233202925983161
100 ms 185.21.7.170
18 2026-08-26 05:40 639233192644780696
93 ms 185.21.7.170
17 2026-08-26 05:23 639233182401183833
193 ms 185.21.7.170
16 2026-08-26 05:06 639233172074181051
111 ms 185.21.7.170
15 2026-08-26 04:49 639233161808421455
107 ms 185.21.7.170
14 2026-08-26 04:32 639233151357344052
2059 ms 185.21.7.170
13 2026-08-26 04:14 639233141034116946
75 ms 185.21.7.170
12 2026-08-26 03:57 639233130828334142
194 ms 185.21.7.170
11 2026-08-26 03:40 639233120373450007
45 ms 185.21.7.170
10 2026-08-26 03:23 639233110066216193
2068 ms 185.21.7.170
9 2026-08-26 02:29 639233078065410564
98 ms 185.21.7.170
8 2026-08-26 02:12 639233067787457832
10 ms 185.21.7.170
7 2026-08-26 01:55 639233057501801162
88 ms 185.21.7.170
6 2026-08-26 01:38 639233047089431703
91 ms 185.21.7.170
5 2026-08-26 01:21 639233036754790688
7 ms 185.21.7.170
4 2026-08-26 01:03 639233026412602472
7 ms 185.21.7.170
3 2026-08-26 00:46 639233016064066127
99 ms 185.21.7.170
2 2026-08-26 00:29 639233005922655772
96 ms 185.21.7.170
1 2026-08-26 00:12 639232995672256907
2064 ms 185.21.7.170