DNS response history for ns2.apamedcentral.org

ns2.apamedcentral.org 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 1066 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.apamedcentral.org.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

1066 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:08

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.109.250.126

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.apamedcentral.org

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:08 639232556111768563
1194 ms 61.109.250.126
34 2026-08-25 11:51 639232545839529039
252 ms 61.109.250.126
33 2026-08-25 11:34 639232535349285207
1357 ms 61.109.250.126
32 2026-08-25 11:17 639232524938080723
1311 ms 61.109.250.126
31 2026-08-25 10:23 639232492740373468
945 ms 61.109.250.126
30 2026-08-25 10:06 639232482235303141
957 ms 61.109.250.126
29 2026-08-25 09:48 639232471861770303
1407 ms 61.109.250.126
28 2026-08-25 09:31 639232461630217327
998 ms 61.109.250.126
27 2026-08-25 09:14 639232451282965990
1077 ms 61.109.250.126
26 2026-08-25 08:57 639232440814614938
1082 ms 61.109.250.126
25 2026-08-25 08:39 639232430410720425
1097 ms 61.109.250.126
24 2026-08-25 08:22 639232420003096185
1058 ms 61.109.250.126
23 2026-08-25 08:04 639232409467287444
1058 ms 61.109.250.126
22 2026-08-25 07:47 639232399077195997
1043 ms 61.109.250.126
21 2026-08-25 07:29 639232388731528337
962 ms 61.109.250.126
20 2026-08-25 07:12 639232378288598612
1090 ms 61.109.250.126
19 2026-08-25 06:18 639232346196373643
951 ms 61.109.250.126
18 2026-08-25 06:01 639232336112370741
1114 ms 61.109.250.126
17 2026-08-25 05:45 639232326146508970
1047 ms 61.109.250.126
16 2026-08-25 05:28 639232316189381720
1308 ms 61.109.250.126
15 2026-08-25 05:12 639232306217998913
1047 ms 61.109.250.126
14 2026-08-25 04:55 639232296255744174
1049 ms 61.109.250.126
13 2026-08-25 04:38 639232286095760789
1068 ms 61.109.250.126
12 2026-08-25 04:21 639232276086186273
963 ms 61.109.250.126
11 2026-08-25 04:05 639232265900986425
1297 ms 61.109.250.126
10 2026-08-25 03:48 639232255723518075
950 ms 61.109.250.126
9 2026-08-25 03:31 639232245484452890
1078 ms 61.109.250.126
8 2026-08-25 03:14 639232235157175331
1084 ms 61.109.250.126
7 2026-08-25 02:20 639232203197189095
1252 ms 61.109.250.126
6 2026-08-25 02:03 639232192844564298
1048 ms 61.109.250.126
5 2026-08-25 01:46 639232182496008942
1076 ms 61.109.250.126
4 2026-08-25 01:29 639232172197053132
1087 ms 61.109.250.126
3 2026-08-25 00:35 639232140250307418
946 ms 61.109.250.126
2 2026-08-25 00:18 639232129927860324
1071 ms 61.109.250.126
1 2026-08-25 00:01 639232119551972438
973 ms 61.109.250.126