DNS response history for ns2.prakitflow.com

ns2.prakitflow.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 32 DNS check records, 32 successful responses, 0 failed responses, and 591 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.prakitflow.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

591 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

141.98.17.7

Most recently resolved hosting IP on selected date

Successful Responses

32

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.prakitflow.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
32 2026-08-28 13:23 639235195230848570
366 ms 141.98.17.7
31 2026-08-28 13:06 639235184840503274
223 ms 141.98.17.7
30 2026-08-28 12:48 639235174453894956
370 ms 141.98.17.7
29 2026-08-28 12:31 639235163898672622
377 ms 141.98.17.7
28 2026-08-28 11:38 639235132147470568
359 ms 141.98.17.7
27 2026-08-28 11:21 639235121907744088
2238 ms 141.98.17.7
26 2026-08-28 11:03 639235111428014262
374 ms 141.98.17.7
25 2026-08-28 10:46 639235100921813626
382 ms 141.98.17.7
24 2026-08-28 09:52 639235068670703481
239 ms 141.98.17.7
23 2026-08-28 09:35 639235058337459445
365 ms 141.98.17.7
22 2026-08-28 09:17 639235047825109146
381 ms 141.98.17.7
21 2026-08-28 09:00 639235037383229033
2221 ms 141.98.17.7
20 2026-08-28 08:07 639235005619242711
2304 ms 141.98.17.7
19 2026-08-28 07:50 639234995310346584
2214 ms 141.98.17.7
18 2026-08-28 07:32 639234984946548933
367 ms 141.98.17.7
17 2026-08-28 07:15 639234974608077290
376 ms 141.98.17.7
16 2026-08-28 06:22 639234942529845595
375 ms 141.98.17.7
15 2026-08-28 06:05 639234932259126627
381 ms 141.98.17.7
14 2026-08-28 05:47 639234921916735988
369 ms 141.98.17.7
13 2026-08-28 05:30 639234911470038027
371 ms 141.98.17.7
12 2026-08-28 04:37 639234879588411654
367 ms 141.98.17.7
11 2026-08-28 04:20 639234869341589104
368 ms 141.98.17.7
10 2026-08-28 04:02 639234859012216675
370 ms 141.98.17.7
9 2026-08-28 03:45 639234848695364934
377 ms 141.98.17.7
8 2026-08-28 02:52 639234816952458162
215 ms 141.98.17.7
7 2026-08-28 02:36 639234806773081598
357 ms 141.98.17.7
6 2026-08-28 02:18 639234796382955255
366 ms 141.98.17.7
5 2026-08-28 02:01 639234786015782563
365 ms 141.98.17.7
4 2026-08-28 01:07 639234753811917646
373 ms 141.98.17.7
3 2026-08-28 00:50 639234743739767811
362 ms 141.98.17.7
2 2026-08-28 00:33 639234733372362811
362 ms 141.98.17.7
1 2026-08-28 00:16 639234723048550337
363 ms 141.98.17.7