DNS response history for ns2.premoweb.com

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

38

Historical checks stored for this nameserver on selected date

Average Latency

345 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:09

All timestamps shown in UTC

Latest Resolved IP on Selected Date

173.199.96.97

Most recently resolved hosting IP on selected date

Successful Responses

38

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.premoweb.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
38 2026-08-25 13:09 639232597643611557
26 ms 173.199.96.97
37 2026-08-25 12:51 639232587225721862
2032 ms 173.199.96.97
36 2026-08-25 12:34 639232576780683689
20 ms 173.199.96.97
35 2026-08-25 12:17 639232566381512620
12 ms 173.199.96.97
34 2026-08-25 11:59 639232556111768563
46 ms 173.199.96.97
33 2026-08-25 11:42 639232545839529039
41 ms 173.199.96.97
32 2026-08-25 11:25 639232535349285207
2014 ms 173.199.96.97
31 2026-08-25 11:08 639232524938080723
21 ms 173.199.96.97
30 2026-08-25 10:14 639232492740373468
37 ms 173.199.96.97
29 2026-08-25 09:57 639232482235303141
35 ms 173.199.96.97
28 2026-08-25 09:39 639232471861770303
63 ms 173.199.96.97
27 2026-08-25 09:22 639232461630217327
33 ms 173.199.96.97
26 2026-08-25 09:05 639232451282965990
18 ms 173.199.96.97
25 2026-08-25 08:47 639232440814614938
3 ms 173.199.96.97
24 2026-08-25 08:30 639232430410720425
23 ms 173.199.96.97
23 2026-08-25 08:13 639232420003096185
35 ms 173.199.96.97
22 2026-08-25 07:55 639232409467287444
57 ms 173.199.96.97
21 2026-08-25 07:38 639232399077195997
2020 ms 173.199.96.97
20 2026-08-25 07:21 639232388731528337
28 ms 173.199.96.97
19 2026-08-25 07:03 639232378288598612
20 ms 173.199.96.97
18 2026-08-25 06:10 639232346196373643
23 ms 173.199.96.97
17 2026-08-25 05:53 639232336112370741
13 ms 173.199.96.97
16 2026-08-25 05:36 639232326146508970
55 ms 173.199.96.97
15 2026-08-25 05:20 639232316189381720
2030 ms 173.199.96.97
14 2026-08-25 05:03 639232306217998913
27 ms 173.199.96.97
13 2026-08-25 04:46 639232296255744174
13 ms 173.199.96.97
12 2026-08-25 04:30 639232286095760789
12 ms 173.199.96.97
11 2026-08-25 04:13 639232276086186273
27 ms 173.199.96.97
10 2026-08-25 03:56 639232265900986425
2023 ms 173.199.96.97
9 2026-08-25 03:39 639232255723518075
43 ms 173.199.96.97
8 2026-08-25 03:22 639232245484452890
2012 ms 173.199.96.97
7 2026-08-25 03:05 639232235157175331
24 ms 173.199.96.97
6 2026-08-25 02:11 639232203197189095
12 ms 173.199.96.97
5 2026-08-25 01:54 639232192844564298
135 ms 173.199.96.97
4 2026-08-25 01:37 639232182496008942
8 ms 173.199.96.97
3 2026-08-25 01:20 639232172197053132
39 ms 173.199.96.97
2 2026-08-25 00:26 639232140250307418
19 ms 173.199.96.97
1 2026-08-25 00:09 639232129927860324
17 ms 173.199.96.97