DNS response history for ns1.gamapay.com.tw

ns1.gamapay.com.tw 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-26. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 1877 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 ns1.gamapay.com.tw.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

1877 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 11:42

All timestamps shown in UTC

Latest Resolved IP on Selected Date

112.121.99.1

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 ns1.gamapay.com.tw

Showing DNS history for 2026-08-26 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-26 11:42 639233403515141099
1365 ms 112.121.99.1
34 2026-08-26 10:47 639233370841350248
1777 ms 112.121.99.1
33 2026-08-26 10:30 639233360361507238
1883 ms 112.121.99.1
32 2026-08-26 10:12 639233350067824371
1778 ms 112.121.99.1
31 2026-08-26 09:55 639233339545274518
1786 ms 112.121.99.1
30 2026-08-26 09:38 639233329214918079
1780 ms 112.121.99.1
29 2026-08-26 09:20 639233318749762337
1768 ms 112.121.99.1
28 2026-08-26 09:03 639233308387917838
1781 ms 112.121.99.1
27 2026-08-26 08:46 639233297961740122
3509 ms 112.121.99.1
26 2026-08-26 08:28 639233287487159094
1772 ms 112.121.99.1
25 2026-08-26 08:11 639233276995531707
1889 ms 112.121.99.1
24 2026-08-26 07:53 639233266521568229
1776 ms 112.121.99.1
23 2026-08-26 07:36 639233256081047431
1777 ms 112.121.99.1
22 2026-08-26 06:42 639233223620132921
1879 ms 112.121.99.1
21 2026-08-26 06:25 639233213287814244
4288 ms 112.121.99.1
20 2026-08-26 06:07 639233202925983161
1891 ms 112.121.99.1
19 2026-08-26 05:50 639233192644780696
1756 ms 112.121.99.1
18 2026-08-26 05:33 639233182401183833
1757 ms 112.121.99.1
17 2026-08-26 05:16 639233172074181051
1761 ms 112.121.99.1
16 2026-08-26 04:59 639233161808421455
1753 ms 112.121.99.1
15 2026-08-26 04:41 639233151357344052
1184 ms 112.121.99.1
14 2026-08-26 04:24 639233141034116946
1764 ms 112.121.99.1
13 2026-08-26 04:07 639233130828334142
1892 ms 112.121.99.1
12 2026-08-26 03:50 639233120373450007
1772 ms 112.121.99.1
11 2026-08-26 03:32 639233110066216193
1961 ms 112.121.99.1
10 2026-08-26 02:39 639233078065410564
1196 ms 112.121.99.1
9 2026-08-26 02:22 639233067787457832
1769 ms 112.121.99.1
8 2026-08-26 02:05 639233057501801162
1757 ms 112.121.99.1
7 2026-08-26 01:48 639233047089431703
1762 ms 112.121.99.1
6 2026-08-26 01:30 639233036754790688
1747 ms 112.121.99.1
5 2026-08-26 01:13 639233026412602472
1890 ms 112.121.99.1
4 2026-08-26 00:56 639233016064066127
1781 ms 112.121.99.1
3 2026-08-26 00:39 639233005922655772
1774 ms 112.121.99.1
2 2026-08-26 00:22 639232995672256907
1919 ms 112.121.99.1
1 2026-08-26 00:05 639232985300872416
1785 ms 112.121.99.1