DNS response history for ns3.inbyin.de

ns3.inbyin.de 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 30 DNS check records, 30 successful responses, 0 failed responses, and 304 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 ns3.inbyin.de.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

304 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

46.16.79.198

Most recently resolved hosting IP on selected date

Successful Responses

30

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 ns3.inbyin.de

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
30 2026-08-25 10:09 639232492740373468
2019 ms 46.16.79.198
29 2026-08-25 09:51 639232482235303141
40 ms 46.16.79.198
28 2026-08-25 09:34 639232471861770303
68 ms 46.16.79.198
27 2026-08-25 09:17 639232461630217327
68 ms 46.16.79.198
26 2026-08-25 09:00 639232451282965990
39 ms 46.16.79.198
25 2026-08-25 08:42 639232440814614938
53 ms 46.16.79.198
24 2026-08-25 08:25 639232430410720425
29 ms 46.16.79.198
23 2026-08-25 08:08 639232420003096185
31 ms 46.16.79.198
22 2026-08-25 07:50 639232409467287444
51 ms 46.16.79.198
21 2026-08-25 07:33 639232399077195997
2065 ms 46.16.79.198
20 2026-08-25 07:16 639232388731528337
56 ms 46.16.79.198
19 2026-08-25 06:58 639232378288598612
2022 ms 46.16.79.198
18 2026-08-25 06:05 639232346196373643
55 ms 46.16.79.198
17 2026-08-25 05:48 639232336112370741
61 ms 46.16.79.198
16 2026-08-25 05:31 639232326146508970
2021 ms 46.16.79.198
15 2026-08-25 05:15 639232316189381720
5 ms 46.16.79.198
14 2026-08-25 04:58 639232306217998913
3 ms 46.16.79.198
13 2026-08-25 04:42 639232296255744174
16 ms 46.16.79.198
12 2026-08-25 04:25 639232286095760789
14 ms 46.16.79.198
11 2026-08-25 04:08 639232276086186273
43 ms 46.16.79.198
10 2026-08-25 03:51 639232265900986425
23 ms 46.16.79.198
9 2026-08-25 03:34 639232255723518075
26 ms 46.16.79.198
8 2026-08-25 03:17 639232245484452890
32 ms 46.16.79.198
7 2026-08-25 03:00 639232235157175331
39 ms 46.16.79.198
6 2026-08-25 02:06 639232203197189095
64 ms 46.16.79.198
5 2026-08-25 01:49 639232192844564298
32 ms 46.16.79.198
4 2026-08-25 01:32 639232182496008942
23 ms 46.16.79.198
3 2026-08-25 01:15 639232172197053132
39 ms 46.16.79.198
2 2026-08-25 00:21 639232140250307418
40 ms 46.16.79.198
1 2026-08-25 00:04 639232129927860324
28 ms 46.16.79.198