DNS response history for ns2.premtravelsonline.com

ns2.premtravelsonline.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-25. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 511 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.premtravelsonline.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

511 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:24

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.171.96.122

Most recently resolved hosting IP on selected date

Successful Responses

35

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.premtravelsonline.com

Showing DNS history for 2026-08-25 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
35 2026-08-25 12:24 639232566381512620
1510 ms 103.171.96.122
34 2026-08-25 12:07 639232556111768563
390 ms 103.171.96.122
33 2026-08-25 11:49 639232545839529039
155 ms 103.171.96.122
32 2026-08-25 11:32 639232535349285207
370 ms 103.171.96.122
31 2026-08-25 11:15 639232524938080723
731 ms 103.171.96.122
30 2026-08-25 10:21 639232492740373468
93 ms 103.171.96.122
29 2026-08-25 10:04 639232482235303141
362 ms 103.171.96.122
28 2026-08-25 09:46 639232471861770303
197 ms 103.171.96.122
27 2026-08-25 09:29 639232461630217327
914 ms 103.171.96.122
26 2026-08-25 09:12 639232451282965990
4 ms 103.171.96.122
25 2026-08-25 08:55 639232440814614938
404 ms 103.171.96.122
24 2026-08-25 08:37 639232430410720425
3687 ms 103.171.96.122
23 2026-08-25 08:20 639232420003096185
982 ms 103.171.96.122
22 2026-08-25 08:02 639232409467287444
368 ms 103.171.96.122
21 2026-08-25 07:45 639232399077195997
1889 ms 103.171.96.122
20 2026-08-25 07:28 639232388731528337
307 ms 103.171.96.122
19 2026-08-25 07:10 639232378288598612
4 ms 103.171.96.122
18 2026-08-25 06:17 639232346196373643
6 ms 103.171.96.122
17 2026-08-25 06:00 639232336112370741
149 ms 103.171.96.122
16 2026-08-25 05:43 639232326146508970
2 ms 103.171.96.122
15 2026-08-25 05:26 639232316189381720
156 ms 103.171.96.122
14 2026-08-25 05:10 639232306217998913
367 ms 103.171.96.122
13 2026-08-25 04:53 639232296255744174
172 ms 103.171.96.122
12 2026-08-25 04:36 639232286095760789
164 ms 103.171.96.122
11 2026-08-25 04:19 639232276086186273
199 ms 103.171.96.122
10 2026-08-25 04:03 639232265900986425
418 ms 103.171.96.122
9 2026-08-25 03:46 639232255723518075
404 ms 103.171.96.122
8 2026-08-25 03:29 639232245484452890
202 ms 103.171.96.122
7 2026-08-25 03:12 639232235157175331
193 ms 103.171.96.122
6 2026-08-25 02:18 639232203197189095
159 ms 103.171.96.122
5 2026-08-25 02:01 639232192844564298
1701 ms 103.171.96.122
4 2026-08-25 01:44 639232182496008942
199 ms 103.171.96.122
3 2026-08-25 01:27 639232172197053132
369 ms 103.171.96.122
2 2026-08-25 00:33 639232140250307418
421 ms 103.171.96.122
1 2026-08-25 00:16 639232129927860324
247 ms 103.171.96.122