DNS response history for ns3.bltc.net

ns3.bltc.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-25. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 32 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.bltc.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

32 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:37

All timestamps shown in UTC

Latest Resolved IP on Selected Date

35.160.203.180

Most recently resolved hosting IP on selected date

Successful Responses

28

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

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
28 2026-08-25 09:37 639232471861770303
32 ms 35.160.203.180
27 2026-08-25 09:20 639232461630217327
31 ms 35.160.203.180
26 2026-08-25 09:03 639232451282965990
8 ms 35.160.203.180
25 2026-08-25 08:46 639232440814614938
31 ms 35.160.203.180
24 2026-08-25 08:28 639232430410720425
15 ms 35.160.203.180
23 2026-08-25 08:11 639232420003096185
91 ms 35.160.203.180
22 2026-08-25 07:54 639232409467287444
28 ms 35.160.203.180
21 2026-08-25 07:36 639232399077195997
94 ms 35.160.203.180
20 2026-08-25 07:19 639232388731528337
20 ms 35.160.203.180
19 2026-08-25 07:02 639232378288598612
12 ms 35.160.203.180
18 2026-08-25 06:08 639232346196373643
24 ms 35.160.203.180
17 2026-08-25 05:51 639232336112370741
29 ms 35.160.203.180
16 2026-08-25 05:35 639232326146508970
31 ms 35.160.203.180
15 2026-08-25 05:18 639232316189381720
10 ms 35.160.203.180
14 2026-08-25 05:01 639232306217998913
111 ms 35.160.203.180
13 2026-08-25 04:45 639232296255744174
11 ms 35.160.203.180
12 2026-08-25 04:28 639232286095760789
16 ms 35.160.203.180
11 2026-08-25 04:11 639232276086186273
27 ms 35.160.203.180
10 2026-08-25 03:54 639232265900986425
25 ms 35.160.203.180
9 2026-08-25 03:37 639232255723518075
48 ms 35.160.203.180
8 2026-08-25 03:20 639232245484452890
11 ms 35.160.203.180
7 2026-08-25 03:03 639232235157175331
12 ms 35.160.203.180
6 2026-08-25 02:10 639232203197189095
63 ms 35.160.203.180
5 2026-08-25 01:52 639232192844564298
23 ms 35.160.203.180
4 2026-08-25 01:35 639232182496008942
24 ms 35.160.203.180
3 2026-08-25 01:18 639232172197053132
7 ms 35.160.203.180
2 2026-08-25 00:25 639232140250307418
46 ms 35.160.203.180
1 2026-08-25 00:08 639232129927860324
28 ms 35.160.203.180