DNS response history for ns1.twofiddy.bet

ns1.twofiddy.bet 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 38 DNS check records, 38 successful responses, 0 failed responses, and 282 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.twofiddy.bet.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

282 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 13:13

All timestamps shown in UTC

Latest Resolved IP on Selected Date

108.39.217.251

Most recently resolved hosting IP on selected date

Successful Responses

38

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.twofiddy.bet

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
38 2026-08-25 13:13 639232597643611557
250 ms 108.39.217.251
37 2026-08-25 12:55 639232587225721862
253 ms 108.39.217.251
36 2026-08-25 12:38 639232576780683689
259 ms 108.39.217.251
35 2026-08-25 12:21 639232566381512620
263 ms 108.39.217.251
34 2026-08-25 12:03 639232556111768563
260 ms 108.39.217.251
33 2026-08-25 11:46 639232545839529039
265 ms 108.39.217.251
32 2026-08-25 11:29 639232535349285207
114 ms 108.39.217.251
31 2026-08-25 11:11 639232524938080723
253 ms 108.39.217.251
30 2026-08-25 10:18 639232492740373468
246 ms 108.39.217.251
29 2026-08-25 10:01 639232482235303141
505 ms 108.39.217.251
28 2026-08-25 09:43 639232471861770303
256 ms 108.39.217.251
27 2026-08-25 09:26 639232461630217327
243 ms 108.39.217.251
26 2026-08-25 09:09 639232451282965990
108 ms 108.39.217.251
25 2026-08-25 08:51 639232440814614938
132 ms 108.39.217.251
24 2026-08-25 08:34 639232430410720425
244 ms 108.39.217.251
23 2026-08-25 08:17 639232420003096185
426 ms 108.39.217.251
22 2026-08-25 07:59 639232409467287444
285 ms 108.39.217.251
21 2026-08-25 07:42 639232399077195997
187 ms 108.39.217.251
20 2026-08-25 07:24 639232388731528337
117 ms 108.39.217.251
19 2026-08-25 07:07 639232378288598612
246 ms 108.39.217.251
18 2026-08-25 06:13 639232346196373643
246 ms 108.39.217.251
17 2026-08-25 05:56 639232336112370741
239 ms 108.39.217.251
16 2026-08-25 05:40 639232326146508970
120 ms 108.39.217.251
15 2026-08-25 05:23 639232316189381720
133 ms 108.39.217.251
14 2026-08-25 05:07 639232306217998913
243 ms 108.39.217.251
13 2026-08-25 04:50 639232296255744174
249 ms 108.39.217.251
12 2026-08-25 04:33 639232286095760789
111 ms 108.39.217.251
11 2026-08-25 04:16 639232276086186273
257 ms 108.39.217.251
10 2026-08-25 04:00 639232265900986425
240 ms 108.39.217.251
9 2026-08-25 03:43 639232255723518075
246 ms 108.39.217.251
8 2026-08-25 03:26 639232245484452890
243 ms 108.39.217.251
7 2026-08-25 03:08 639232235157175331
247 ms 108.39.217.251
6 2026-08-25 02:15 639232203197189095
2152 ms 108.39.217.251
5 2026-08-25 01:58 639232192844564298
108 ms 108.39.217.251
4 2026-08-25 01:41 639232182496008942
241 ms 108.39.217.251
3 2026-08-25 01:23 639232172197053132
252 ms 108.39.217.251
2 2026-08-25 00:30 639232140250307418
241 ms 108.39.217.251
1 2026-08-25 00:13 639232129927860324
247 ms 108.39.217.251