DNS response history for ns1.bilgitec.com

ns1.bilgitec.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, 33 successful responses, 1 failed responses, and 216 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.bilgitec.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

216 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.98.50.38

Most recently resolved hosting IP on selected date

Successful Responses

33

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.bilgitec.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:29 639233403515141099
36 ms 141.98.50.38
33 2026-08-26 10:34 639233370841350248
37 ms 141.98.50.38
32 2026-08-26 10:17 639233360361507238
34 ms 141.98.50.38
31 2026-08-26 10:00 639233350067824371
79 ms 141.98.50.38
30 2026-08-26 09:42 639233339545274518
2043 ms 141.98.50.38
29 2026-08-26 09:25 639233329214918079
107 ms 141.98.50.38
28 2026-08-26 09:08 639233318749762337
129 ms 141.98.50.38
27 2026-08-26 08:50 639233308387917838
16 ms 141.98.50.38
26 2026-08-26 08:33 639233297961740122
35 ms 141.98.50.38
25 2026-08-26 08:15 639233287487159094
30 ms 141.98.50.38
24 2026-08-26 07:58 639233276995531707
11 ms 141.98.50.38
23 2026-08-26 07:40 639233266521568229
2041 ms 141.98.50.38
22 2026-08-26 07:23 639233256081047431
13 ms 141.98.50.38
21 2026-08-26 06:29 639233223620132921
81 ms 141.98.50.38
20 2026-08-26 06:12 639233213287814244
30 ms 141.98.50.38
19 2026-08-26 05:54 639233202925983161
7 ms 141.98.50.38
18 2026-08-26 05:37 639233192644780696
12 ms 141.98.50.38
17 2026-08-26 05:20 639233182401183833
24 ms 141.98.50.38
16 2026-08-26 05:03 639233172074181051
28 ms 141.98.50.38
15 2026-08-26 04:46 639233161808421455
26 ms 141.98.50.38
14 2026-08-26 04:28 639233151357344052
21 ms 141.98.50.38
13 2026-08-26 04:11 639233141034116946
32 ms 141.98.50.38
12 2026-08-26 03:54 639233130828334142
14 ms 141.98.50.38
11 2026-08-26 03:37 639233120373450007
17 ms 141.98.50.38
10 2026-08-26 03:20 639233110066216193
10 ms 141.98.50.38
9 2026-08-26 02:26 639233078065410564
44 ms 141.98.50.38
8 2026-08-26 02:09 639233067787457832
-
7 2026-08-26 01:52 639233057501801162
2039 ms 141.98.50.38
6 2026-08-26 01:35 639233047089431703
29 ms 141.98.50.38
5 2026-08-26 01:17 639233036754790688
38 ms 141.98.50.38
4 2026-08-26 01:00 639233026412602472
12 ms 141.98.50.38
3 2026-08-26 00:43 639233016064066127
8 ms 141.98.50.38
2 2026-08-26 00:26 639233005922655772
14 ms 141.98.50.38
1 2026-08-26 00:09 639232995672256907
40 ms 141.98.50.38