DNS response history for brickstravels.com

brickstravels.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-25. For this date, NameServerHistory found 34 DNS check records, 30 successful responses, 4 failed responses, and 2702 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 brickstravels.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

2702 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

217.26.48.101

Most recently resolved hosting IP on selected date

Successful Responses

30

Checks that returned a measurable response

Failed Responses

4

Checks with no response or no returned latency

Failure Rate

12%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for brickstravels.com

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
34 2026-08-25 11:53 639232545839529039
2019 ms 217.26.48.101
33 2026-08-25 11:35 639232535349285207
3528 ms 217.26.48.101
32 2026-08-25 11:18 639232524938080723
4021 ms 217.26.48.101
31 2026-08-25 10:24 639232492740373468
2130 ms 217.26.48.101
30 2026-08-25 10:07 639232482235303141
3530 ms 217.26.48.101
29 2026-08-25 09:49 639232471861770303
2023 ms 217.26.48.101
28 2026-08-25 09:32 639232461630217327
2023 ms 217.26.48.101
27 2026-08-25 09:15 639232451282965990
2021 ms 217.26.48.101
26 2026-08-25 08:58 639232440814614938
2021 ms 217.26.48.101
25 2026-08-25 08:40 639232430410720425
4019 ms 217.26.48.101
24 2026-08-25 08:23 639232420003096185
-
23 2026-08-25 08:06 639232409467287444
2062 ms 217.26.48.101
22 2026-08-25 07:48 639232399077195997
-
21 2026-08-25 07:31 639232388731528337
3560 ms 217.26.48.101
20 2026-08-25 07:14 639232378288598612
2062 ms 217.26.48.101
19 2026-08-25 06:19 639232346196373643
2036 ms 217.26.48.101
18 2026-08-25 06:03 639232336112370741
2037 ms 217.26.48.101
17 2026-08-25 05:46 639232326146508970
2109 ms 217.26.48.101
16 2026-08-25 05:29 639232316189381720
2020 ms 217.26.48.101
15 2026-08-25 05:13 639232306217998913
-
14 2026-08-25 04:56 639232296255744174
2031 ms 217.26.48.101
13 2026-08-25 04:39 639232286095760789
-
12 2026-08-25 04:23 639232276086186273
3524 ms 217.26.48.101
11 2026-08-25 04:06 639232265900986425
3518 ms 217.26.48.101
10 2026-08-25 03:49 639232255723518075
2020 ms 217.26.48.101
9 2026-08-25 03:32 639232245484452890
4018 ms 217.26.48.101
8 2026-08-25 03:15 639232235157175331
2021 ms 217.26.48.101
7 2026-08-25 02:21 639232203197189095
3520 ms 217.26.48.101
6 2026-08-25 02:04 639232192844564298
4086 ms 217.26.48.101
5 2026-08-25 01:47 639232182496008942
2019 ms 217.26.48.101
4 2026-08-25 01:30 639232172197053132
2022 ms 217.26.48.101
3 2026-08-25 00:36 639232140250307418
3517 ms 217.26.48.101
2 2026-08-25 00:20 639232129927860324
2024 ms 217.26.48.101
1 2026-08-25 00:02 639232119551972438
3520 ms 217.26.48.101