DNS response history for ns2.911blimp.com

ns2.911blimp.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-29. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 228 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 ns2.911blimp.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

228 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 09:37

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

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 ns2.911blimp.com

Showing DNS history for 2026-08-29 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-29 09:37 639235924465736791
269 ms 74.208.106.232
27 2026-08-29 09:20 639235914430611197
260 ms 74.208.106.232
26 2026-08-29 09:03 639235904343784853
252 ms 74.208.106.232
25 2026-08-29 08:47 639235894201078068
287 ms 74.208.106.232
24 2026-08-29 08:30 639235884233447452
276 ms 74.208.106.232
23 2026-08-29 08:13 639235874142207309
269 ms 74.208.106.232
22 2026-08-29 07:56 639235863974652466
4 ms 74.208.106.232
21 2026-08-29 07:39 639235853716243436
135 ms 74.208.106.232
20 2026-08-29 07:22 639235843614494759
197 ms 74.208.106.232
19 2026-08-29 07:05 639235833401459551
245 ms 74.208.106.232
18 2026-08-29 06:48 639235823220464528
5 ms 74.208.106.232
17 2026-08-29 06:31 639235812997510905
264 ms 74.208.106.232
16 2026-08-29 05:38 639235781101962521
249 ms 74.208.106.232
15 2026-08-29 05:21 639235771207673260
276 ms 74.208.106.232
14 2026-08-29 05:05 639235761047429642
241 ms 74.208.106.232
13 2026-08-29 04:48 639235750964347246
2 ms 74.208.106.232
12 2026-08-29 04:31 639235740923490874
261 ms 74.208.106.232
11 2026-08-29 04:14 639235730842894399
243 ms 74.208.106.232
10 2026-08-29 03:58 639235720760084717
267 ms 74.208.106.232
9 2026-08-29 03:41 639235710843666743
281 ms 74.208.106.232
8 2026-08-29 03:24 639235700733510561
267 ms 74.208.106.232
7 2026-08-29 03:07 639235690509906192
248 ms 74.208.106.232
6 2026-08-29 02:50 639235680156673501
271 ms 74.208.106.232
5 2026-08-29 02:33 639235669720606443
271 ms 74.208.106.232
4 2026-08-29 01:39 639235637451417084
253 ms 74.208.106.232
3 2026-08-29 01:22 639235627307383453
293 ms 74.208.106.232
2 2026-08-29 01:05 639235616906386856
246 ms 74.208.106.232
1 2026-08-29 00:47 639235606582912691
266 ms 74.208.106.232