DNS response history for ns2.blueshingle.com

ns2.blueshingle.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 29 DNS check records, 29 successful responses, 0 failed responses, and 84 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.blueshingle.com.
Records on Selected Date

29

Historical checks stored for this nameserver on selected date

Average Latency

84 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-29 10:26

All timestamps shown in UTC

Latest Resolved IP on Selected Date

208.101.250.130

Most recently resolved hosting IP on selected date

Successful Responses

29

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.blueshingle.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
29 2026-08-29 10:26 639235956590882003
9 ms 208.101.250.130
28 2026-08-29 09:32 639235924465736791
15 ms 208.101.250.130
27 2026-08-29 09:15 639235914430611197
7 ms 208.101.250.130
26 2026-08-29 08:59 639235904343784853
176 ms 208.101.250.130
25 2026-08-29 08:42 639235894201078068
58 ms 208.101.250.130
24 2026-08-29 08:25 639235884233447452
51 ms 208.101.250.130
23 2026-08-29 08:08 639235874142207309
52 ms 208.101.250.130
22 2026-08-29 07:51 639235863974652466
9 ms 208.101.250.130
21 2026-08-29 07:34 639235853716243436
46 ms 208.101.250.130
20 2026-08-29 07:18 639235843614494759
93 ms 208.101.250.130
19 2026-08-29 07:00 639235833401459551
26 ms 208.101.250.130
18 2026-08-29 06:43 639235823220464528
44 ms 208.101.250.130
17 2026-08-29 06:26 639235812997510905
49 ms 208.101.250.130
16 2026-08-29 05:33 639235781101962521
54 ms 208.101.250.130
15 2026-08-29 05:17 639235771207673260
58 ms 208.101.250.130
14 2026-08-29 05:00 639235761047429642
165 ms 208.101.250.130
13 2026-08-29 04:43 639235750964347246
252 ms 208.101.250.130
12 2026-08-29 04:26 639235740923490874
65 ms 208.101.250.130
11 2026-08-29 04:09 639235730842894399
154 ms 208.101.250.130
10 2026-08-29 03:53 639235720760084717
54 ms 208.101.250.130
9 2026-08-29 03:36 639235710843666743
87 ms 208.101.250.130
8 2026-08-29 03:19 639235700733510561
167 ms 208.101.250.130
7 2026-08-29 03:02 639235690509906192
97 ms 208.101.250.130
6 2026-08-29 02:45 639235680156673501
7 ms 208.101.250.130
5 2026-08-29 02:28 639235669720606443
66 ms 208.101.250.130
4 2026-08-29 01:34 639235637451417084
50 ms 208.101.250.130
3 2026-08-29 01:17 639235627307383453
276 ms 208.101.250.130
2 2026-08-29 01:00 639235616906386856
103 ms 208.101.250.130
1 2026-08-29 00:42 639235606582912691
160 ms 208.101.250.130