DNS response history for ns3.net2cyber.net

ns3.net2cyber.net 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-26. For this date, NameServerHistory found 27 DNS check records, 27 successful responses, 0 failed responses, and 625 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.net2cyber.net.
Records on Selected Date

27

Historical checks stored for this nameserver on selected date

Average Latency

625 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 08:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

203.153.99.122

Most recently resolved hosting IP on selected date

Successful Responses

27

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.net2cyber.net

Showing DNS history for 2026-08-26 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
27 2026-08-26 08:41 639233297961740122
179 ms 203.153.99.122
26 2026-08-26 08:24 639233287487159094
332 ms 203.153.99.122
25 2026-08-26 08:06 639233276995531707
333 ms 203.153.99.122
24 2026-08-26 07:49 639233266521568229
354 ms 203.153.99.122
23 2026-08-26 07:31 639233256081047431
170 ms 203.153.99.122
22 2026-08-26 06:37 639233223620132921
329 ms 203.153.99.122
21 2026-08-26 06:20 639233213287814244
331 ms 203.153.99.122
20 2026-08-26 06:03 639233202925983161
497 ms 203.153.99.122
19 2026-08-26 05:45 639233192644780696
334 ms 203.153.99.122
18 2026-08-26 05:28 639233182401183833
164 ms 203.153.99.122
17 2026-08-26 05:11 639233172074181051
505 ms 203.153.99.122
16 2026-08-26 04:54 639233161808421455
336 ms 203.153.99.122
15 2026-08-26 04:37 639233151357344052
338 ms 203.153.99.122
14 2026-08-26 04:19 639233141034116946
492 ms 203.153.99.122
13 2026-08-26 04:02 639233130828334142
330 ms 203.153.99.122
12 2026-08-26 03:45 639233120373450007
326 ms 203.153.99.122
11 2026-08-26 03:28 639233110066216193
334 ms 203.153.99.122
10 2026-08-26 02:35 639233078065410564
327 ms 203.153.99.122
9 2026-08-26 02:17 639233067787457832
9 ms 203.153.99.122
8 2026-08-26 02:00 639233057501801162
2186 ms 203.153.99.122
7 2026-08-26 01:43 639233047089431703
2233 ms 203.153.99.122
6 2026-08-26 01:26 639233036754790688
496 ms 203.153.99.122
5 2026-08-26 01:09 639233026412602472
495 ms 203.153.99.122
4 2026-08-26 00:51 639233016064066127
496 ms 203.153.99.122
3 2026-08-26 00:34 639233005922655772
2007 ms 203.153.99.122
2 2026-08-26 00:17 639232995672256907
2440 ms 203.153.99.122
1 2026-08-26 00:00 639232985300872416
493 ms 203.153.99.122