DNS response history for ns3.c2yweb.be

ns3.c2yweb.be 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 31 DNS check records, 31 successful responses, 0 failed responses, and 353 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.c2yweb.be.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

353 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 11:05

All timestamps shown in UTC

Latest Resolved IP on Selected Date

185.136.98.133

Most recently resolved hosting IP on selected date

Successful Responses

31

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.c2yweb.be

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
31 2026-08-25 11:05 639232524938080723
2077 ms 185.136.98.133
30 2026-08-25 10:11 639232492740373468
19 ms 185.136.98.133
29 2026-08-25 09:54 639232482235303141
43 ms 185.136.98.133
28 2026-08-25 09:36 639232471861770303
8 ms 185.136.98.133
27 2026-08-25 09:19 639232461630217327
28 ms 185.136.98.133
26 2026-08-25 09:02 639232451282965990
44 ms 185.136.98.133
25 2026-08-25 08:45 639232440814614938
2039 ms 185.136.98.133
24 2026-08-25 08:27 639232430410720425
38 ms 185.136.98.133
23 2026-08-25 08:10 639232420003096185
51 ms 185.136.98.133
22 2026-08-25 07:52 639232409467287444
17 ms 185.136.98.133
21 2026-08-25 07:35 639232399077195997
5 ms 185.136.98.133
20 2026-08-25 07:18 639232388731528337
33 ms 185.136.98.133
19 2026-08-25 07:00 639232378288598612
25 ms 185.136.98.133
18 2026-08-25 06:07 639232346196373643
18 ms 185.136.98.133
17 2026-08-25 05:50 639232336112370741
47 ms 185.136.98.133
16 2026-08-25 05:33 639232326146508970
2025 ms 185.136.98.133
15 2026-08-25 05:17 639232316189381720
23 ms 185.136.98.133
14 2026-08-25 05:00 639232306217998913
36 ms 185.136.98.133
13 2026-08-25 04:44 639232296255744174
23 ms 185.136.98.133
12 2026-08-25 04:27 639232286095760789
49 ms 185.136.98.133
11 2026-08-25 04:10 639232276086186273
33 ms 185.136.98.133
10 2026-08-25 03:53 639232265900986425
45 ms 185.136.98.133
9 2026-08-25 03:36 639232255723518075
2028 ms 185.136.98.133
8 2026-08-25 03:19 639232245484452890
2025 ms 185.136.98.133
7 2026-08-25 03:02 639232235157175331
16 ms 185.136.98.133
6 2026-08-25 02:08 639232203197189095
30 ms 185.136.98.133
5 2026-08-25 01:51 639232192844564298
32 ms 185.136.98.133
4 2026-08-25 01:34 639232182496008942
12 ms 185.136.98.133
3 2026-08-25 01:17 639232172197053132
17 ms 185.136.98.133
2 2026-08-25 00:24 639232140250307418
18 ms 185.136.98.133
1 2026-08-25 00:06 639232129927860324
45 ms 185.136.98.133