DNS response history for ns2.boundandtabbed.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

689 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

16.144.200.150

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

Showing DNS history for 2026-08-28 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-28 11:38 639235132147470568
352 ms 16.144.200.150
27 2026-08-28 11:21 639235121907744088
354 ms 16.144.200.150
26 2026-08-28 11:03 639235111428014262
352 ms 16.144.200.150
25 2026-08-28 10:46 639235100921813626
368 ms 16.144.200.150
24 2026-08-28 09:52 639235068670703481
371 ms 16.144.200.150
23 2026-08-28 09:35 639235058337459445
347 ms 16.144.200.150
22 2026-08-28 09:17 639235047825109146
362 ms 16.144.200.150
21 2026-08-28 09:00 639235037383229033
373 ms 16.144.200.150
20 2026-08-28 08:07 639235005619242711
379 ms 16.144.200.150
19 2026-08-28 07:50 639234995310346584
2273 ms 16.144.200.150
18 2026-08-28 07:33 639234984946548933
344 ms 16.144.200.150
17 2026-08-28 07:15 639234974608077290
377 ms 16.144.200.150
16 2026-08-28 06:22 639234942529845595
2179 ms 16.144.200.150
15 2026-08-28 06:05 639234932259126627
346 ms 16.144.200.150
14 2026-08-28 05:47 639234921916735988
334 ms 16.144.200.150
13 2026-08-28 05:30 639234911470038027
380 ms 16.144.200.150
12 2026-08-28 04:37 639234879588411654
348 ms 16.144.200.150
11 2026-08-28 04:20 639234869341589104
351 ms 16.144.200.150
10 2026-08-28 04:03 639234859012216675
2181 ms 16.144.200.150
9 2026-08-28 03:45 639234848695364934
346 ms 16.144.200.150
8 2026-08-28 02:52 639234816952458162
2286 ms 16.144.200.150
7 2026-08-28 02:36 639234806773081598
339 ms 16.144.200.150
6 2026-08-28 02:18 639234796382955255
2198 ms 16.144.200.150
5 2026-08-28 02:01 639234786015782563
353 ms 16.144.200.150
4 2026-08-28 01:07 639234753811917646
366 ms 16.144.200.150
3 2026-08-28 00:50 639234743739767811
342 ms 16.144.200.150
2 2026-08-28 00:33 639234733372362811
356 ms 16.144.200.150
1 2026-08-28 00:16 639234723048550337
347 ms 16.144.200.150