DNS response history for ns2.2amores.com

ns2.2amores.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-26. For this date, NameServerHistory found 33 DNS check records, 33 successful responses, 0 failed responses, and 423 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.2amores.com.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

423 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.138.188.239

Most recently resolved hosting IP on selected date

Successful Responses

33

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.2amores.com

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
33 2026-08-26 10:27 639233360361507238
338 ms 103.138.188.239
32 2026-08-26 10:09 639233350067824371
318 ms 103.138.188.239
31 2026-08-26 09:52 639233339545274518
324 ms 103.138.188.239
30 2026-08-26 09:35 639233329214918079
323 ms 103.138.188.239
29 2026-08-26 09:17 639233318749762337
270 ms 103.138.188.239
28 2026-08-26 09:00 639233308387917838
336 ms 103.138.188.239
27 2026-08-26 08:43 639233297961740122
319 ms 103.138.188.239
26 2026-08-26 08:25 639233287487159094
333 ms 103.138.188.239
25 2026-08-26 08:08 639233276995531707
343 ms 103.138.188.239
24 2026-08-26 07:50 639233266521568229
322 ms 103.138.188.239
23 2026-08-26 07:33 639233256081047431
328 ms 103.138.188.239
22 2026-08-26 06:39 639233223620132921
311 ms 103.138.188.239
21 2026-08-26 06:22 639233213287814244
322 ms 103.138.188.239
20 2026-08-26 06:04 639233202925983161
164 ms 103.138.188.239
19 2026-08-26 05:47 639233192644780696
319 ms 103.138.188.239
18 2026-08-26 05:30 639233182401183833
337 ms 103.138.188.239
17 2026-08-26 05:13 639233172074181051
2195 ms 103.138.188.239
16 2026-08-26 04:56 639233161808421455
175 ms 103.138.188.239
15 2026-08-26 04:38 639233151357344052
330 ms 103.138.188.239
14 2026-08-26 04:21 639233141034116946
2172 ms 103.138.188.239
13 2026-08-26 04:04 639233130828334142
334 ms 103.138.188.239
12 2026-08-26 03:47 639233120373450007
318 ms 103.138.188.239
11 2026-08-26 03:29 639233110066216193
318 ms 103.138.188.239
10 2026-08-26 02:36 639233078065410564
345 ms 103.138.188.239
9 2026-08-26 02:19 639233067787457832
333 ms 103.138.188.239
8 2026-08-26 02:02 639233057501801162
313 ms 103.138.188.239
7 2026-08-26 01:45 639233047089431703
319 ms 103.138.188.239
6 2026-08-26 01:27 639233036754790688
332 ms 103.138.188.239
5 2026-08-26 01:10 639233026412602472
320 ms 103.138.188.239
4 2026-08-26 00:53 639233016064066127
190 ms 103.138.188.239
3 2026-08-26 00:36 639233005922655772
333 ms 103.138.188.239
2 2026-08-26 00:19 639232995672256907
307 ms 103.138.188.239
1 2026-08-26 00:02 639232985300872416
322 ms 103.138.188.239