DNS response history for ns110122.phdns11.es

ns110122.phdns11.es 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 27 DNS check records, 27 successful responses, 0 failed responses, and 317 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 ns110122.phdns11.es.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

317 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.63.110.122

Most recently resolved hosting IP on selected date

Successful Responses

27

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 ns110122.phdns11.es

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
27 2026-08-26 08:52 639233308387917838
15 ms 212.63.110.122
26 2026-08-26 08:34 639233297961740122
28 ms 212.63.110.122
25 2026-08-26 08:17 639233287487159094
6 ms 212.63.110.122
24 2026-08-26 08:00 639233276995531707
34 ms 212.63.110.122
23 2026-08-26 07:42 639233266521568229
39 ms 212.63.110.122
22 2026-08-26 07:25 639233256081047431
5 ms 212.63.110.122
21 2026-08-26 06:31 639233223620132921
18 ms 212.63.110.122
20 2026-08-26 06:13 639233213287814244
2027 ms 212.63.110.122
19 2026-08-26 05:56 639233202925983161
16 ms 212.63.110.122
18 2026-08-26 05:39 639233192644780696
60 ms 212.63.110.122
17 2026-08-26 05:22 639233182401183833
2020 ms 212.63.110.122
16 2026-08-26 05:05 639233172074181051
6 ms 212.63.110.122
15 2026-08-26 04:48 639233161808421455
31 ms 212.63.110.122
14 2026-08-26 04:30 639233151357344052
25 ms 212.63.110.122
13 2026-08-26 04:13 639233141034116946
2014 ms 212.63.110.122
12 2026-08-26 03:56 639233130828334142
18 ms 212.63.110.122
11 2026-08-26 03:39 639233120373450007
19 ms 212.63.110.122
10 2026-08-26 03:21 639233110066216193
38 ms 212.63.110.122
9 2026-08-26 02:28 639233078065410564
4 ms 212.63.110.122
8 2026-08-26 02:11 639233067787457832
12 ms 212.63.110.122
7 2026-08-26 01:54 639233057501801162
8 ms 212.63.110.122
6 2026-08-26 01:36 639233047089431703
5 ms 212.63.110.122
5 2026-08-26 01:19 639233036754790688
3 ms 212.63.110.122
4 2026-08-26 01:02 639233026412602472
5 ms 212.63.110.122
3 2026-08-26 00:45 639233016064066127
2059 ms 212.63.110.122
2 2026-08-26 00:28 639233005922655772
3 ms 212.63.110.122
1 2026-08-26 00:11 639232995672256907
37 ms 212.63.110.122