DNS response history for ns1.metrotvnews.tv

ns1.metrotvnews.tv 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-28. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 553 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.metrotvnews.tv.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

553 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 14:35

All timestamps shown in UTC

Latest Resolved IP on Selected Date

103.61.116.10

Most recently resolved hosting IP on selected date

Successful Responses

34

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.metrotvnews.tv

Showing DNS history for 2026-08-28 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
34 2026-08-28 14:35 639235238225955920
348 ms 103.61.116.10
33 2026-08-28 14:18 639235227727862105
339 ms 103.61.116.10
32 2026-08-28 13:24 639235195230848570
342 ms 103.61.116.10
31 2026-08-28 13:07 639235184840503274
338 ms 103.61.116.10
30 2026-08-28 12:49 639235174453894956
329 ms 103.61.116.10
29 2026-08-28 12:32 639235163898672622
348 ms 103.61.116.10
28 2026-08-28 11:39 639235132147470568
337 ms 103.61.116.10
27 2026-08-28 11:21 639235121907744088
2259 ms 103.61.116.10
26 2026-08-28 11:04 639235111428014262
195 ms 103.61.116.10
25 2026-08-28 10:47 639235100921813626
338 ms 103.61.116.10
24 2026-08-28 09:53 639235068670703481
337 ms 103.61.116.10
23 2026-08-28 09:36 639235058337459445
2230 ms 103.61.116.10
22 2026-08-28 09:18 639235047825109146
342 ms 103.61.116.10
21 2026-08-28 09:01 639235037383229033
2286 ms 103.61.116.10
20 2026-08-28 08:08 639235005619242711
333 ms 103.61.116.10
19 2026-08-28 07:51 639234995310346584
333 ms 103.61.116.10
18 2026-08-28 07:33 639234984946548933
364 ms 103.61.116.10
17 2026-08-28 07:16 639234974608077290
344 ms 103.61.116.10
16 2026-08-28 06:22 639234942529845595
339 ms 103.61.116.10
15 2026-08-28 06:05 639234932259126627
341 ms 103.61.116.10
14 2026-08-28 05:48 639234921916735988
335 ms 103.61.116.10
13 2026-08-28 05:31 639234911470038027
334 ms 103.61.116.10
12 2026-08-28 04:38 639234879588411654
342 ms 103.61.116.10
11 2026-08-28 04:21 639234869341589104
338 ms 103.61.116.10
10 2026-08-28 04:03 639234859012216675
332 ms 103.61.116.10
9 2026-08-28 03:46 639234848695364934
334 ms 103.61.116.10
8 2026-08-28 02:53 639234816952458162
335 ms 103.61.116.10
7 2026-08-28 02:36 639234806773081598
2176 ms 103.61.116.10
6 2026-08-28 02:19 639234796382955255
336 ms 103.61.116.10
5 2026-08-28 02:02 639234786015782563
334 ms 103.61.116.10
4 2026-08-28 01:08 639234753811917646
334 ms 103.61.116.10
3 2026-08-28 00:51 639234743739767811
334 ms 103.61.116.10
2 2026-08-28 00:34 639234733372362811
177 ms 103.61.116.10
1 2026-08-28 00:17 639234723048550337
338 ms 103.61.116.10