DNS response history for ns2.zipapay.com

ns2.zipapay.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 36 DNS check records, 35 successful responses, 1 failed responses, and 274 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.zipapay.com.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

274 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:00

All timestamps shown in UTC

Latest Resolved IP on Selected Date

161.97.76.90

Most recently resolved hosting IP on selected date

Successful Responses

35

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.zipapay.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
36 2026-08-28 15:00 639235258803654519
40 ms 161.97.76.90
35 2026-08-28 14:43 639235248596087996
36 ms 161.97.76.90
34 2026-08-28 14:26 639235238225955920
32 ms 161.97.76.90
33 2026-08-28 14:08 639235227727862105
46 ms 161.97.76.90
32 2026-08-28 13:14 639235195230848570
18 ms 161.97.76.90
31 2026-08-28 12:57 639235184840503274
30 ms 161.97.76.90
30 2026-08-28 12:39 639235174453894956
39 ms 161.97.76.90
29 2026-08-28 12:22 639235163898672622
-
28 2026-08-28 11:29 639235132147470568
38 ms 161.97.76.90
27 2026-08-28 11:12 639235121907744088
38 ms 161.97.76.90
26 2026-08-28 10:55 639235111428014262
70 ms 161.97.76.90
25 2026-08-28 10:37 639235100921813626
55 ms 161.97.76.90
24 2026-08-28 09:43 639235068670703481
16 ms 161.97.76.90
23 2026-08-28 09:26 639235058337459445
47 ms 161.97.76.90
22 2026-08-28 09:08 639235047825109146
49 ms 161.97.76.90
21 2026-08-28 08:51 639235037383229033
36 ms 161.97.76.90
20 2026-08-28 07:58 639235005619242711
2026 ms 161.97.76.90
19 2026-08-28 07:41 639234995310346584
75 ms 161.97.76.90
18 2026-08-28 07:24 639234984946548933
2057 ms 161.97.76.90
17 2026-08-28 07:06 639234974608077290
2028 ms 161.97.76.90
16 2026-08-28 06:13 639234942529845595
2061 ms 161.97.76.90
15 2026-08-28 05:56 639234932259126627
80 ms 161.97.76.90
14 2026-08-28 05:39 639234921916735988
51 ms 161.97.76.90
13 2026-08-28 05:21 639234911470038027
32 ms 161.97.76.90
12 2026-08-28 04:28 639234879588411654
57 ms 161.97.76.90
11 2026-08-28 04:11 639234869341589104
41 ms 161.97.76.90
10 2026-08-28 03:54 639234859012216675
87 ms 161.97.76.90
9 2026-08-28 03:37 639234848695364934
74 ms 161.97.76.90
8 2026-08-28 02:44 639234816952458162
38 ms 161.97.76.90
7 2026-08-28 02:27 639234806773081598
26 ms 161.97.76.90
6 2026-08-28 02:09 639234796382955255
41 ms 161.97.76.90
5 2026-08-28 01:52 639234786015782563
33 ms 161.97.76.90
4 2026-08-28 00:58 639234753811917646
63 ms 161.97.76.90
3 2026-08-28 00:42 639234743739767811
42 ms 161.97.76.90
2 2026-08-28 00:24 639234733372362811
24 ms 161.97.76.90
1 2026-08-28 00:07 639234723048550337
80 ms 161.97.76.90