DNS response history for ns2.tflow.com.br

ns2.tflow.com.br 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, 34 successful responses, 0 failed responses, and 410 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.tflow.com.br.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

410 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

150.230.80.170

Most recently resolved hosting IP on selected date

Successful Responses

34

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.tflow.com.br

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:43 639233370841350248
284 ms 150.230.80.170
33 2026-08-26 10:25 639233360361507238
290 ms 150.230.80.170
32 2026-08-26 10:08 639233350067824371
451 ms 150.230.80.170
31 2026-08-26 09:51 639233339545274518
279 ms 150.230.80.170
30 2026-08-26 09:33 639233329214918079
298 ms 150.230.80.170
29 2026-08-26 09:16 639233318749762337
292 ms 150.230.80.170
28 2026-08-26 08:59 639233308387917838
295 ms 150.230.80.170
27 2026-08-26 08:41 639233297961740122
292 ms 150.230.80.170
26 2026-08-26 08:24 639233287487159094
287 ms 150.230.80.170
25 2026-08-26 08:07 639233276995531707
287 ms 150.230.80.170
24 2026-08-26 07:49 639233266521568229
285 ms 150.230.80.170
23 2026-08-26 07:31 639233256081047431
296 ms 150.230.80.170
22 2026-08-26 06:38 639233223620132921
279 ms 150.230.80.170
21 2026-08-26 06:20 639233213287814244
290 ms 150.230.80.170
20 2026-08-26 06:03 639233202925983161
288 ms 150.230.80.170
19 2026-08-26 05:46 639233192644780696
284 ms 150.230.80.170
18 2026-08-26 05:28 639233182401183833
2202 ms 150.230.80.170
17 2026-08-26 05:12 639233172074181051
2215 ms 150.230.80.170
16 2026-08-26 04:54 639233161808421455
294 ms 150.230.80.170
15 2026-08-26 04:37 639233151357344052
293 ms 150.230.80.170
14 2026-08-26 04:20 639233141034116946
273 ms 150.230.80.170
13 2026-08-26 04:03 639233130828334142
288 ms 150.230.80.170
12 2026-08-26 03:45 639233120373450007
287 ms 150.230.80.170
11 2026-08-26 03:28 639233110066216193
298 ms 150.230.80.170
10 2026-08-26 02:35 639233078065410564
297 ms 150.230.80.170
9 2026-08-26 02:18 639233067787457832
274 ms 150.230.80.170
8 2026-08-26 02:00 639233057501801162
294 ms 150.230.80.170
7 2026-08-26 01:43 639233047089431703
279 ms 150.230.80.170
6 2026-08-26 01:26 639233036754790688
448 ms 150.230.80.170
5 2026-08-26 01:09 639233026412602472
292 ms 150.230.80.170
4 2026-08-26 00:51 639233016064066127
279 ms 150.230.80.170
3 2026-08-26 00:34 639233005922655772
291 ms 150.230.80.170
2 2026-08-26 00:17 639232995672256907
281 ms 150.230.80.170
1 2026-08-26 00:00 639232985300872416
277 ms 150.230.80.170