DNS response history for ns2.dctv.com.ph

ns2.dctv.com.ph 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-30. For this date, NameServerHistory found 36 DNS check records, 36 successful responses, 0 failed responses, and 516 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.dctv.com.ph.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

516 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-30 11:52

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.225.136.150

Most recently resolved hosting IP on selected date

Successful Responses

36

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.dctv.com.ph

Showing DNS history for 2026-08-30 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-30 11:52 639236867916029489
525 ms 103.225.136.150
35 2026-08-30 11:35 639236858088772005
523 ms 103.225.136.150
34 2026-08-30 11:18 639236848158742395
263 ms 103.225.136.150
33 2026-08-30 11:02 639236838137395574
260 ms 103.225.136.150
32 2026-08-30 10:45 639236827967386881
260 ms 103.225.136.150
31 2026-08-30 10:28 639236817708615077
522 ms 103.225.136.150
30 2026-08-30 09:35 639236785770651804
263 ms 103.225.136.150
29 2026-08-30 09:18 639236775820686373
261 ms 103.225.136.150
28 2026-08-30 09:01 639236765768339082
521 ms 103.225.136.150
27 2026-08-30 08:45 639236755602384085
321 ms 103.225.136.150
26 2026-08-30 08:27 639236745600094925
11 ms 103.225.136.150
25 2026-08-30 08:11 639236735311262753
2257 ms 103.225.136.150
24 2026-08-30 07:54 639236724996745235
526 ms 103.225.136.150
23 2026-08-30 07:36 639236714839899761
522 ms 103.225.136.150
22 2026-08-30 07:20 639236704748431488
1022 ms 103.225.136.150
21 2026-08-30 07:03 639236694430128550
4 ms 103.225.136.150
20 2026-08-30 06:45 639236684143292417
524 ms 103.225.136.150
19 2026-08-30 06:28 639236673972499943
4 ms 103.225.136.150
18 2026-08-30 05:35 639236642126522802
976 ms 103.225.136.150
17 2026-08-30 05:18 639236632183518198
520 ms 103.225.136.150
16 2026-08-30 05:02 639236622289312589
525 ms 103.225.136.150
15 2026-08-30 04:45 639236612490676525
539 ms 103.225.136.150
14 2026-08-30 04:29 639236602582494852
3 ms 103.225.136.150
13 2026-08-30 04:13 639236592511706469
261 ms 103.225.136.150
12 2026-08-30 03:56 639236582441006869
519 ms 103.225.136.150
11 2026-08-30 03:39 639236572478785089
3 ms 103.225.136.150
10 2026-08-30 03:22 639236562556749999
294 ms 103.225.136.150
9 2026-08-30 03:06 639236552353482281
522 ms 103.225.136.150
8 2026-08-30 02:49 639236542188881607
522 ms 103.225.136.150
7 2026-08-30 02:32 639236531885440105
210 ms 103.225.136.150
6 2026-08-30 01:38 639236499922985383
261 ms 103.225.136.150
5 2026-08-30 01:21 639236489713594431
524 ms 103.225.136.150
4 2026-08-30 01:05 639236479750443901
5 ms 103.225.136.150
3 2026-08-30 00:48 639236469719936375
2011 ms 103.225.136.150
2 2026-08-30 00:31 639236459579244885
2015 ms 103.225.136.150
1 2026-08-30 00:14 639236449582837549
262 ms 103.225.136.150