DNS response history for ns2.frontierisp.net

ns2.frontierisp.net 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-24. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 1056 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.frontierisp.net.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

1056 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 13:38

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.172.122.132

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.frontierisp.net

Showing DNS history for 2026-08-24 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-24 13:38 639231745628278877
8 ms 202.172.122.132
31 2026-08-24 13:21 639231735407682062
3 ms 202.172.122.132
30 2026-08-24 12:28 639231703815441688
3816 ms 202.172.122.132
29 2026-08-24 12:11 639231693747052549
2320 ms 202.172.122.132
28 2026-08-24 11:54 639231683712487276
5 ms 202.172.122.132
27 2026-08-24 11:38 639231673513573868
6 ms 202.172.122.132
26 2026-08-24 10:44 639231641791249939
3 ms 202.172.122.132
25 2026-08-24 10:28 639231631866211033
4 ms 202.172.122.132
24 2026-08-24 10:11 639231621644955316
3 ms 202.172.122.132
23 2026-08-24 09:54 639231611478799259
3823 ms 202.172.122.132
22 2026-08-24 09:01 639231579923718211
4 ms 202.172.122.132
21 2026-08-24 08:45 639231569810702936
2321 ms 202.172.122.132
20 2026-08-24 08:28 639231559762411619
2320 ms 202.172.122.132
19 2026-08-24 08:11 639231549663595407
3 ms 202.172.122.132
18 2026-08-24 07:18 639231518076817246
4 ms 202.172.122.132
17 2026-08-24 07:02 639231508078650885
2 ms 202.172.122.132
16 2026-08-24 06:45 639231498210697093
3837 ms 202.172.122.132
15 2026-08-24 06:29 639231488109699360
4 ms 202.172.122.132
14 2026-08-24 05:36 639231456772510692
2008 ms 202.172.122.132
13 2026-08-24 05:20 639231447084631185
3 ms 202.172.122.132
12 2026-08-24 05:03 639231437208519473
2 ms 202.172.122.132
11 2026-08-24 04:47 639231427209627490
2321 ms 202.172.122.132
10 2026-08-24 03:54 639231395791246644
3 ms 202.172.122.132
9 2026-08-24 03:38 639231386075551458
3 ms 202.172.122.132
8 2026-08-24 03:22 639231376208713791
4 ms 202.172.122.132
7 2026-08-24 03:05 639231366170589276
2009 ms 202.172.122.132
6 2026-08-24 02:13 639231334732159368
2008 ms 202.172.122.132
5 2026-08-24 01:56 639231325035670078
2325 ms 202.172.122.132
4 2026-08-24 01:40 639231315132253837
2298 ms 202.172.122.132
3 2026-08-24 01:23 639231305014280808
2 ms 202.172.122.132
2 2026-08-24 00:31 639231273779380675
3 ms 202.172.122.132
1 2026-08-24 00:15 639231264180839154
2326 ms 202.172.122.132