DNS response history for ns2.playmax.buzz

ns2.playmax.buzz 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-27. For this date, NameServerHistory found 37 DNS check records, 36 successful responses, 1 failed responses, and 375 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.playmax.buzz.
Records on Selected Date

37

Historical checks stored for this nameserver on selected date

Average Latency

375 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 12:23

All timestamps shown in UTC

Latest Resolved IP on Selected Date

82.180.144.51

Most recently resolved hosting IP on selected date

Successful Responses

36

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.playmax.buzz

Showing DNS history for 2026-08-27 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
37 2026-08-27 12:23 639234296664302575
246 ms 82.180.144.51
36 2026-08-27 12:06 639234286253196126
2225 ms 82.180.144.51
35 2026-08-27 11:12 639234253963286387
240 ms 82.180.144.51
34 2026-08-27 10:55 639234243654907465
259 ms 82.180.144.51
33 2026-08-27 10:38 639234233269654413
247 ms 82.180.144.51
32 2026-08-27 10:20 639234222943951923
2370 ms 82.180.144.51
31 2026-08-27 10:03 639234212558002823
242 ms 82.180.144.51
30 2026-08-27 09:46 639234202117531850
246 ms 82.180.144.51
29 2026-08-27 09:28 639234191649612722
235 ms 82.180.144.51
28 2026-08-27 09:11 639234181105879568
233 ms 82.180.144.51
27 2026-08-27 08:53 639234170713214496
240 ms 82.180.144.51
26 2026-08-27 08:36 639234160341037652
269 ms 82.180.144.51
25 2026-08-27 08:19 639234149799404224
245 ms 82.180.144.51
24 2026-08-27 08:01 639234139553286469
244 ms 82.180.144.51
23 2026-08-27 07:08 639234107183588293
13 ms 82.180.144.51
22 2026-08-27 06:50 639234096905435724
239 ms 82.180.144.51
21 2026-08-27 06:33 639234086579410775
257 ms 82.180.144.51
20 2026-08-27 06:16 639234076291157956
238 ms 82.180.144.51
19 2026-08-27 05:59 639234065981939454
2158 ms 82.180.144.51
18 2026-08-27 05:42 639234055548642997
237 ms 82.180.144.51
17 2026-08-27 05:24 639234045267979603
244 ms 82.180.144.51
16 2026-08-27 05:07 639234034999717463
237 ms 82.180.144.51
15 2026-08-27 04:50 639234024739225358
259 ms 82.180.144.51
14 2026-08-27 04:33 639234014311170162
21 ms 82.180.144.51
13 2026-08-27 04:15 639234003806017640
157 ms 82.180.144.51
12 2026-08-27 03:58 639233993356203030
269 ms 82.180.144.51
11 2026-08-27 03:05 639233961301716608
242 ms 82.180.144.51
10 2026-08-27 02:47 639233950834200647
376 ms 82.180.144.51
9 2026-08-27 02:30 639233940431849026
247 ms 82.180.144.51
8 2026-08-27 02:13 639233930110596398
249 ms 82.180.144.51
7 2026-08-27 01:55 639233919705434540
7 ms 82.180.144.51
6 2026-08-27 01:38 639233909452807845
-
5 2026-08-27 01:21 639233899096420820
10 ms 82.180.144.51
4 2026-08-27 01:04 639233888707824939
7 ms 82.180.144.51
3 2026-08-27 00:46 639233878461203802
240 ms 82.180.144.51
2 2026-08-27 00:29 639233868060868209
135 ms 82.180.144.51
1 2026-08-27 00:11 639233857450922991
134 ms 82.180.144.51