DNS response history for ns2.texanhost.com

ns2.texanhost.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-26. For this date, NameServerHistory found 34 DNS check records, 33 successful responses, 1 failed responses, and 666 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.texanhost.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

666 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:44

All timestamps shown in UTC

Latest Resolved IP on Selected Date

131.153.9.80

Most recently resolved hosting IP on selected date

Successful Responses

33

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.texanhost.com

Showing DNS history for 2026-08-26 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-26 10:44 639233370841350248
173 ms 131.153.9.80
33 2026-08-26 10:27 639233360361507238
305 ms 131.153.9.80
32 2026-08-26 10:09 639233350067824371
302 ms 131.153.9.80
31 2026-08-26 09:52 639233339545274518
-
30 2026-08-26 09:35 639233329214918079
746 ms 131.153.9.80
29 2026-08-26 09:17 639233318749762337
564 ms 131.153.9.80
28 2026-08-26 09:00 639233308387917838
332 ms 131.153.9.80
27 2026-08-26 08:43 639233297961740122
352 ms 131.153.9.80
26 2026-08-26 08:25 639233287487159094
335 ms 131.153.9.80
25 2026-08-26 08:08 639233276995531707
2190 ms 131.153.9.80
24 2026-08-26 07:50 639233266521568229
323 ms 131.153.9.80
23 2026-08-26 07:33 639233256081047431
316 ms 131.153.9.80
22 2026-08-26 06:39 639233223620132921
2204 ms 131.153.9.80
21 2026-08-26 06:22 639233213287814244
319 ms 131.153.9.80
20 2026-08-26 06:04 639233202925983161
310 ms 131.153.9.80
19 2026-08-26 05:47 639233192644780696
182 ms 131.153.9.80
18 2026-08-26 05:30 639233182401183833
318 ms 131.153.9.80
17 2026-08-26 05:13 639233172074181051
312 ms 131.153.9.80
16 2026-08-26 04:56 639233161808421455
317 ms 131.153.9.80
15 2026-08-26 04:39 639233151357344052
206 ms 131.153.9.80
14 2026-08-26 04:21 639233141034116946
312 ms 131.153.9.80
13 2026-08-26 04:04 639233130828334142
311 ms 131.153.9.80
12 2026-08-26 03:47 639233120373450007
319 ms 131.153.9.80
11 2026-08-26 03:29 639233110066216193
316 ms 131.153.9.80
10 2026-08-26 02:36 639233078065410564
2200 ms 131.153.9.80
9 2026-08-26 02:19 639233067787457832
311 ms 131.153.9.80
8 2026-08-26 02:02 639233057501801162
314 ms 131.153.9.80
7 2026-08-26 01:45 639233047089431703
4177 ms 131.153.9.80
6 2026-08-26 01:27 639233036754790688
2009 ms 131.153.9.80
5 2026-08-26 01:10 639233026412602472
322 ms 131.153.9.80
4 2026-08-26 00:53 639233016064066127
322 ms 131.153.9.80
3 2026-08-26 00:36 639233005922655772
319 ms 131.153.9.80
2 2026-08-26 00:19 639232995672256907
327 ms 131.153.9.80
1 2026-08-26 00:02 639232985300872416
313 ms 131.153.9.80