DNS response history for ns1.911blimp.net

ns1.911blimp.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 30 DNS check records, 30 successful responses, 0 failed responses, and 284 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.911blimp.net.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

284 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:17

All timestamps shown in UTC

Latest Resolved IP on Selected Date

74.208.106.232

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 ns1.911blimp.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
30 2026-08-25 10:17 639232492740373468
282 ms 74.208.106.232
29 2026-08-25 09:59 639232482235303141
290 ms 74.208.106.232
28 2026-08-25 09:42 639232471861770303
5 ms 74.208.106.232
27 2026-08-25 09:25 639232461630217327
281 ms 74.208.106.232
26 2026-08-25 09:07 639232451282965990
254 ms 74.208.106.232
25 2026-08-25 08:50 639232440814614938
296 ms 74.208.106.232
24 2026-08-25 08:33 639232430410720425
268 ms 74.208.106.232
23 2026-08-25 08:15 639232420003096185
285 ms 74.208.106.232
22 2026-08-25 07:58 639232409467287444
259 ms 74.208.106.232
21 2026-08-25 07:40 639232399077195997
276 ms 74.208.106.232
20 2026-08-25 07:23 639232388731528337
4 ms 74.208.106.232
19 2026-08-25 07:06 639232378288598612
291 ms 74.208.106.232
18 2026-08-25 06:12 639232346196373643
269 ms 74.208.106.232
17 2026-08-25 05:55 639232336112370741
269 ms 74.208.106.232
16 2026-08-25 05:39 639232326146508970
122 ms 74.208.106.232
15 2026-08-25 05:22 639232316189381720
296 ms 74.208.106.232
14 2026-08-25 05:06 639232306217998913
150 ms 74.208.106.232
13 2026-08-25 04:49 639232296255744174
2142 ms 74.208.106.232
12 2026-08-25 04:32 639232286095760789
286 ms 74.208.106.232
11 2026-08-25 04:15 639232276086186273
3 ms 74.208.106.232
10 2026-08-25 03:59 639232265900986425
104 ms 74.208.106.232
9 2026-08-25 03:42 639232255723518075
251 ms 74.208.106.232
8 2026-08-25 03:24 639232245484452890
256 ms 74.208.106.232
7 2026-08-25 03:07 639232235157175331
4 ms 74.208.106.232
6 2026-08-25 02:14 639232203197189095
260 ms 74.208.106.232
5 2026-08-25 01:57 639232192844564298
257 ms 74.208.106.232
4 2026-08-25 01:39 639232182496008942
244 ms 74.208.106.232
3 2026-08-25 01:22 639232172197053132
278 ms 74.208.106.232
2 2026-08-25 00:29 639232140250307418
270 ms 74.208.106.232
1 2026-08-25 00:12 639232129927860324
265 ms 74.208.106.232