DNS response history for ns1.watchbuyerbirmingham.com

ns1.watchbuyerbirmingham.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 275 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.watchbuyerbirmingham.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

275 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:11

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.148.173.149

Most recently resolved hosting IP on selected date

Successful Responses

35

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.watchbuyerbirmingham.com

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:11 639234253963286387
242 ms 135.148.173.149
34 2026-08-27 10:54 639234243654907465
101 ms 135.148.173.149
33 2026-08-27 10:36 639234233269654413
116 ms 135.148.173.149
32 2026-08-27 10:19 639234222943951923
130 ms 135.148.173.149
31 2026-08-27 10:02 639234212558002823
246 ms 135.148.173.149
30 2026-08-27 09:45 639234202117531850
241 ms 135.148.173.149
29 2026-08-27 09:27 639234191649612722
247 ms 135.148.173.149
28 2026-08-27 09:10 639234181105879568
243 ms 135.148.173.149
27 2026-08-27 08:52 639234170713214496
2298 ms 135.148.173.149
26 2026-08-27 08:35 639234160341037652
253 ms 135.148.173.149
25 2026-08-27 08:17 639234149799404224
236 ms 135.148.173.149
24 2026-08-27 08:00 639234139553286469
248 ms 135.148.173.149
23 2026-08-27 07:07 639234107183588293
96 ms 135.148.173.149
22 2026-08-27 06:49 639234096905435724
100 ms 135.148.173.149
21 2026-08-27 06:32 639234086579410775
10 ms 135.148.173.149
20 2026-08-27 06:15 639234076291157956
209 ms 135.148.173.149
19 2026-08-27 05:58 639234065981939454
206 ms 135.148.173.149
18 2026-08-27 05:41 639234055548642997
202 ms 135.148.173.149
17 2026-08-27 05:23 639234045267979603
2017 ms 135.148.173.149
16 2026-08-27 05:06 639234034999717463
104 ms 135.148.173.149
15 2026-08-27 04:49 639234024739225358
105 ms 135.148.173.149
14 2026-08-27 04:32 639234014311170162
206 ms 135.148.173.149
13 2026-08-27 04:14 639234003806017640
100 ms 135.148.173.149
12 2026-08-27 03:57 639233993356203030
202 ms 135.148.173.149
11 2026-08-27 03:03 639233961301716608
204 ms 135.148.173.149
10 2026-08-27 02:46 639233950834200647
103 ms 135.148.173.149
9 2026-08-27 02:29 639233940431849026
116 ms 135.148.173.149
8 2026-08-27 02:11 639233930110596398
203 ms 135.148.173.149
7 2026-08-27 01:54 639233919705434540
8 ms 135.148.173.149
6 2026-08-27 01:37 639233909452807845
103 ms 135.148.173.149
5 2026-08-27 01:20 639233899096420820
9 ms 135.148.173.149
4 2026-08-27 01:02 639233888707824939
224 ms 135.148.173.149
3 2026-08-27 00:45 639233878461203802
199 ms 135.148.173.149
2 2026-08-27 00:28 639233868060868209
210 ms 135.148.173.149
1 2026-08-27 00:10 639233857450922991
103 ms 135.148.173.149