DNS response history for ns3.breaked.me

ns3.breaked.me 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 28 DNS check records, 28 successful responses, 0 failed responses, and 371 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 ns3.breaked.me.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

371 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:43

All timestamps shown in UTC

Latest Resolved IP on Selected Date

135.181.202.8

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 ns3.breaked.me

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
28 2026-08-25 09:43 639232471861770303
135 ms 135.181.202.8
27 2026-08-25 09:26 639232461630217327
60 ms 135.181.202.8
26 2026-08-25 09:09 639232451282965990
3800 ms 135.181.202.8
25 2026-08-25 08:51 639232440814614938
62 ms 135.181.202.8
24 2026-08-25 08:34 639232430410720425
133 ms 135.181.202.8
23 2026-08-25 08:17 639232420003096185
2113 ms 135.181.202.8
22 2026-08-25 07:59 639232409467287444
1822 ms 135.181.202.8
21 2026-08-25 07:42 639232399077195997
122 ms 135.181.202.8
20 2026-08-25 07:24 639232388731528337
150 ms 135.181.202.8
19 2026-08-25 07:07 639232378288598612
138 ms 135.181.202.8
18 2026-08-25 06:13 639232346196373643
38 ms 135.181.202.8
17 2026-08-25 05:57 639232336112370741
236 ms 135.181.202.8
16 2026-08-25 05:40 639232326146508970
74 ms 135.181.202.8
15 2026-08-25 05:23 639232316189381720
61 ms 135.181.202.8
14 2026-08-25 05:07 639232306217998913
55 ms 135.181.202.8
13 2026-08-25 04:50 639232296255744174
60 ms 135.181.202.8
12 2026-08-25 04:33 639232286095760789
134 ms 135.181.202.8
11 2026-08-25 04:16 639232276086186273
68 ms 135.181.202.8
10 2026-08-25 04:00 639232265900986425
65 ms 135.181.202.8
9 2026-08-25 03:43 639232255723518075
50 ms 135.181.202.8
8 2026-08-25 03:26 639232245484452890
124 ms 135.181.202.8
7 2026-08-25 03:08 639232235157175331
131 ms 135.181.202.8
6 2026-08-25 02:15 639232203197189095
58 ms 135.181.202.8
5 2026-08-25 01:58 639232192844564298
140 ms 135.181.202.8
4 2026-08-25 01:41 639232182496008942
126 ms 135.181.202.8
3 2026-08-25 01:23 639232172197053132
122 ms 135.181.202.8
2 2026-08-25 00:30 639232140250307418
187 ms 135.181.202.8
1 2026-08-25 00:13 639232129927860324
121 ms 135.181.202.8