DNS response history for ns2.playtech.bingo

ns2.playtech.bingo 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-25. For this date, NameServerHistory found 34 DNS check records, 34 successful responses, 0 failed responses, and 865 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.playtech.bingo.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

865 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:51

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.110.20.5

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 ns2.playtech.bingo

Showing DNS history for 2026-08-25 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-25 11:51 639232545839529039
3535 ms 78.110.20.5
33 2026-08-25 11:33 639232535349285207
35 ms 78.110.20.5
32 2026-08-25 11:16 639232524938080723
39 ms 78.110.20.5
31 2026-08-25 10:22 639232492740373468
29 ms 78.110.20.5
30 2026-08-25 10:05 639232482235303141
2008 ms 78.110.20.5
29 2026-08-25 09:47 639232471861770303
43 ms 78.110.20.5
28 2026-08-25 09:30 639232461630217327
3 ms 78.110.20.5
27 2026-08-25 09:13 639232451282965990
35 ms 78.110.20.5
26 2026-08-25 08:56 639232440814614938
38 ms 78.110.20.5
25 2026-08-25 08:38 639232430410720425
2029 ms 78.110.20.5
24 2026-08-25 08:21 639232420003096185
2028 ms 78.110.20.5
23 2026-08-25 08:04 639232409467287444
613 ms 78.110.20.5
22 2026-08-25 07:46 639232399077195997
31 ms 78.110.20.5
21 2026-08-25 07:29 639232388731528337
31 ms 78.110.20.5
20 2026-08-25 07:11 639232378288598612
33 ms 78.110.20.5
19 2026-08-25 06:18 639232346196373643
22 ms 78.110.20.5
18 2026-08-25 06:01 639232336112370741
2012 ms 78.110.20.5
17 2026-08-25 05:44 639232326146508970
3527 ms 78.110.20.5
16 2026-08-25 05:27 639232316189381720
34 ms 78.110.20.5
15 2026-08-25 05:11 639232306217998913
3676 ms 78.110.20.5
14 2026-08-25 04:54 639232296255744174
2015 ms 78.110.20.5
13 2026-08-25 04:37 639232286095760789
27 ms 78.110.20.5
12 2026-08-25 04:21 639232276086186273
3542 ms 78.110.20.5
11 2026-08-25 04:04 639232265900986425
26 ms 78.110.20.5
10 2026-08-25 03:47 639232255723518075
21 ms 78.110.20.5
9 2026-08-25 03:30 639232245484452890
36 ms 78.110.20.5
8 2026-08-25 03:13 639232235157175331
38 ms 78.110.20.5
7 2026-08-25 02:19 639232203197189095
34 ms 78.110.20.5
6 2026-08-25 02:02 639232192844564298
31 ms 78.110.20.5
5 2026-08-25 01:45 639232182496008942
34 ms 78.110.20.5
4 2026-08-25 01:28 639232172197053132
42 ms 78.110.20.5
3 2026-08-25 00:34 639232140250307418
42 ms 78.110.20.5
2 2026-08-25 00:18 639232129927860324
3691 ms 78.110.20.5
1 2026-08-25 00:00 639232119551972438
38 ms 78.110.20.5