DNS response history for ns2.trlhost.com

ns2.trlhost.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 321 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.trlhost.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

321 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

198.12.225.171

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.trlhost.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
330 ms 198.12.225.171
27 2026-08-28 11:21 639235121907744088
389 ms 198.12.225.171
26 2026-08-28 11:03 639235111428014262
336 ms 198.12.225.171
25 2026-08-28 10:46 639235100921813626
348 ms 198.12.225.171
24 2026-08-28 09:52 639235068670703481
3 ms 198.12.225.171
23 2026-08-28 09:35 639235058337459445
344 ms 198.12.225.171
22 2026-08-28 09:17 639235047825109146
354 ms 198.12.225.171
21 2026-08-28 09:00 639235037383229033
341 ms 198.12.225.171
20 2026-08-28 08:07 639235005619242711
338 ms 198.12.225.171
19 2026-08-28 07:50 639234995310346584
332 ms 198.12.225.171
18 2026-08-28 07:32 639234984946548933
181 ms 198.12.225.171
17 2026-08-28 07:15 639234974608077290
344 ms 198.12.225.171
16 2026-08-28 06:22 639234942529845595
368 ms 198.12.225.171
15 2026-08-28 06:05 639234932259126627
342 ms 198.12.225.171
14 2026-08-28 05:47 639234921916735988
347 ms 198.12.225.171
13 2026-08-28 05:30 639234911470038027
350 ms 198.12.225.171
12 2026-08-28 04:37 639234879588411654
335 ms 198.12.225.171
11 2026-08-28 04:20 639234869341589104
371 ms 198.12.225.171
10 2026-08-28 04:02 639234859012216675
348 ms 198.12.225.171
9 2026-08-28 03:45 639234848695364934
351 ms 198.12.225.171
8 2026-08-28 02:52 639234816952458162
341 ms 198.12.225.171
7 2026-08-28 02:35 639234806773081598
341 ms 198.12.225.171
6 2026-08-28 02:18 639234796382955255
351 ms 198.12.225.171
5 2026-08-28 02:01 639234786015782563
346 ms 198.12.225.171
4 2026-08-28 01:07 639234753811917646
335 ms 198.12.225.171
3 2026-08-28 00:50 639234743739767811
159 ms 198.12.225.171
2 2026-08-28 00:33 639234733372362811
336 ms 198.12.225.171
1 2026-08-28 00:16 639234723048550337
339 ms 198.12.225.171