DNS response history for ns1.bingger.net

ns1.bingger.net 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 245 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.bingger.net.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

245 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:34

All timestamps shown in UTC

Latest Resolved IP on Selected Date

38.154.88.248

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.bingger.net

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:34 639233403515141099
235 ms 38.154.88.248
33 2026-08-26 10:40 639233370841350248
242 ms 38.154.88.248
32 2026-08-26 10:22 639233360361507238
276 ms 38.154.88.248
31 2026-08-26 10:05 639233350067824371
230 ms 38.154.88.248
30 2026-08-26 09:48 639233339545274518
238 ms 38.154.88.248
29 2026-08-26 09:30 639233329214918079
9 ms 38.154.88.248
28 2026-08-26 09:13 639233318749762337
249 ms 38.154.88.248
27 2026-08-26 08:56 639233308387917838
253 ms 38.154.88.248
26 2026-08-26 08:38 639233297961740122
343 ms 38.154.88.248
25 2026-08-26 08:21 639233287487159094
234 ms 38.154.88.248
24 2026-08-26 08:03 639233276995531707
298 ms 38.154.88.248
23 2026-08-26 07:46 639233266521568229
335 ms 38.154.88.248
22 2026-08-26 07:28 639233256081047431
234 ms 38.154.88.248
21 2026-08-26 06:35 639233223620132921
248 ms 38.154.88.248
20 2026-08-26 06:17 639233213287814244
323 ms 38.154.88.248
19 2026-08-26 06:00 639233202925983161
288 ms 38.154.88.248
18 2026-08-26 05:43 639233192644780696
234 ms 38.154.88.248
17 2026-08-26 05:26 639233182401183833
262 ms 38.154.88.248
16 2026-08-26 05:09 639233172074181051
249 ms 38.154.88.248
15 2026-08-26 04:51 639233161808421455
269 ms 38.154.88.248
14 2026-08-26 04:34 639233151357344052
232 ms 38.154.88.248
13 2026-08-26 04:17 639233141034116946
135 ms 38.154.88.248
12 2026-08-26 04:00 639233130828334142
249 ms 38.154.88.248
11 2026-08-26 03:42 639233120373450007
243 ms 38.154.88.248
10 2026-08-26 03:25 639233110066216193
241 ms 38.154.88.248
9 2026-08-26 02:32 639233078065410564
236 ms 38.154.88.248
8 2026-08-26 02:15 639233067787457832
227 ms 38.154.88.248
7 2026-08-26 01:57 639233057501801162
232 ms 38.154.88.248
6 2026-08-26 01:40 639233047089431703
264 ms 38.154.88.248
5 2026-08-26 01:23 639233036754790688
245 ms 38.154.88.248
4 2026-08-26 01:06 639233026412602472
235 ms 38.154.88.248
3 2026-08-26 00:48 639233016064066127
243 ms 38.154.88.248
2 2026-08-26 00:31 639233005922655772
266 ms 38.154.88.248
1 2026-08-26 00:14 639232995672256907
246 ms 38.154.88.248