DNS response history for ns1.texascreditrepair411.com

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

29

Historical checks stored for this nameserver on selected date

Average Latency

280 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 09:29

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.101.146.180

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 ns1.texascreditrepair411.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
29 2026-08-27 09:29 639234191649612722
53 ms 5.101.146.180
28 2026-08-27 09:12 639234181105879568
2062 ms 5.101.146.180
27 2026-08-27 08:54 639234170713214496
45 ms 5.101.146.180
26 2026-08-27 08:37 639234160341037652
77 ms 5.101.146.180
25 2026-08-27 08:19 639234149799404224
47 ms 5.101.146.180
24 2026-08-27 08:02 639234139553286469
56 ms 5.101.146.180
23 2026-08-27 07:08 639234107183588293
48 ms 5.101.146.180
22 2026-08-27 06:51 639234096905435724
3561 ms 5.101.146.180
21 2026-08-27 06:34 639234086579410775
47 ms 5.101.146.180
20 2026-08-27 06:17 639234076291157956
45 ms 5.101.146.180
19 2026-08-27 06:00 639234065981939454
45 ms 5.101.146.180
18 2026-08-27 05:43 639234055548642997
44 ms 5.101.146.180
17 2026-08-27 05:25 639234045267979603
42 ms 5.101.146.180
16 2026-08-27 05:08 639234034999717463
42 ms 5.101.146.180
15 2026-08-27 04:51 639234024739225358
49 ms 5.101.146.180
14 2026-08-27 04:34 639234014311170162
65 ms 5.101.146.180
13 2026-08-27 04:16 639234003806017640
47 ms 5.101.146.180
12 2026-08-27 03:59 639233993356203030
48 ms 5.101.146.180
11 2026-08-27 03:05 639233961301716608
46 ms 5.101.146.180
10 2026-08-27 02:48 639233950834200647
44 ms 5.101.146.180
9 2026-08-27 02:31 639233940431849026
44 ms 5.101.146.180
8 2026-08-27 02:13 639233930110596398
47 ms 5.101.146.180
7 2026-08-27 01:56 639233919705434540
43 ms 5.101.146.180
6 2026-08-27 01:39 639233909452807845
44 ms 5.101.146.180
5 2026-08-27 01:22 639233899096420820
639 ms 5.101.146.180
4 2026-08-27 01:04 639233888707824939
50 ms 5.101.146.180
3 2026-08-27 00:47 639233878461203802
57 ms 5.101.146.180
2 2026-08-27 00:30 639233868060868209
624 ms 5.101.146.180
1 2026-08-27 00:12 639233857450922991
47 ms 5.101.146.180