DNS response history for ns2.bangkokmuaynews.com

ns2.bangkokmuaynews.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-24. For this date, NameServerHistory found 28 DNS check records, 28 successful responses, 0 failed responses, and 188 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.bangkokmuaynews.com.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

188 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-24 11:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

5.135.175.220

Most recently resolved hosting IP on selected date

Successful Responses

28

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.bangkokmuaynews.com

Showing DNS history for 2026-08-24 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
28 2026-08-24 11:45 639231683712487276
2062 ms 5.135.175.220
27 2026-08-24 11:28 639231673513573868
35 ms 5.135.175.220
26 2026-08-24 10:35 639231641791249939
40 ms 5.135.175.220
25 2026-08-24 10:18 639231631866211033
48 ms 5.135.175.220
24 2026-08-24 10:01 639231621644955316
39 ms 5.135.175.220
23 2026-08-24 09:44 639231611478799259
2034 ms 5.135.175.220
22 2026-08-24 08:52 639231579923718211
46 ms 5.135.175.220
21 2026-08-24 08:35 639231569810702936
29 ms 5.135.175.220
20 2026-08-24 08:18 639231559762411619
22 ms 5.135.175.220
19 2026-08-24 08:01 639231549663595407
32 ms 5.135.175.220
18 2026-08-24 07:09 639231518076817246
104 ms 5.135.175.220
17 2026-08-24 06:52 639231508078650885
38 ms 5.135.175.220
16 2026-08-24 06:35 639231498210697093
83 ms 5.135.175.220
15 2026-08-24 06:19 639231488109699360
46 ms 5.135.175.220
14 2026-08-24 05:27 639231456772510692
49 ms 5.135.175.220
13 2026-08-24 05:10 639231447084631185
36 ms 5.135.175.220
12 2026-08-24 04:54 639231437208519473
68 ms 5.135.175.220
11 2026-08-24 04:37 639231427209627490
39 ms 5.135.175.220
10 2026-08-24 03:45 639231395791246644
35 ms 5.135.175.220
9 2026-08-24 03:29 639231386075551458
46 ms 5.135.175.220
8 2026-08-24 03:12 639231376208713791
47 ms 5.135.175.220
7 2026-08-24 02:56 639231366170589276
50 ms 5.135.175.220
6 2026-08-24 02:03 639231334732159368
35 ms 5.135.175.220
5 2026-08-24 01:47 639231325035670078
17 ms 5.135.175.220
4 2026-08-24 01:30 639231315132253837
46 ms 5.135.175.220
3 2026-08-24 01:14 639231305014280808
46 ms 5.135.175.220
2 2026-08-24 00:22 639231273779380675
46 ms 5.135.175.220
1 2026-08-24 00:06 639231264180839154
36 ms 5.135.175.220