DNS response history for ns2.syber.com.br

ns2.syber.com.br 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 33 DNS check records, 33 successful responses, 0 failed responses, and 422 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.syber.com.br.
Records on Selected Date

33

Historical checks stored for this nameserver on selected date

Average Latency

422 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:27

All timestamps shown in UTC

Latest Resolved IP on Selected Date

177.38.229.82

Most recently resolved hosting IP on selected date

Successful Responses

33

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.syber.com.br

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
33 2026-08-26 10:27 639233360361507238
363 ms 177.38.229.82
32 2026-08-26 10:09 639233350067824371
355 ms 177.38.229.82
31 2026-08-26 09:52 639233339545274518
2008 ms 177.38.229.82
30 2026-08-26 09:34 639233329214918079
359 ms 177.38.229.82
29 2026-08-26 09:17 639233318749762337
209 ms 177.38.229.82
28 2026-08-26 09:00 639233308387917838
175 ms 177.38.229.82
27 2026-08-26 08:43 639233297961740122
371 ms 177.38.229.82
26 2026-08-26 08:25 639233287487159094
365 ms 177.38.229.82
25 2026-08-26 08:08 639233276995531707
484 ms 177.38.229.82
24 2026-08-26 07:50 639233266521568229
377 ms 177.38.229.82
23 2026-08-26 07:33 639233256081047431
362 ms 177.38.229.82
22 2026-08-26 06:39 639233223620132921
360 ms 177.38.229.82
21 2026-08-26 06:21 639233213287814244
367 ms 177.38.229.82
20 2026-08-26 06:04 639233202925983161
346 ms 177.38.229.82
19 2026-08-26 05:47 639233192644780696
171 ms 177.38.229.82
18 2026-08-26 05:30 639233182401183833
356 ms 177.38.229.82
17 2026-08-26 05:13 639233172074181051
176 ms 177.38.229.82
16 2026-08-26 04:55 639233161808421455
374 ms 177.38.229.82
15 2026-08-26 04:38 639233151357344052
367 ms 177.38.229.82
14 2026-08-26 04:21 639233141034116946
180 ms 177.38.229.82
13 2026-08-26 04:04 639233130828334142
357 ms 177.38.229.82
12 2026-08-26 03:47 639233120373450007
356 ms 177.38.229.82
11 2026-08-26 03:29 639233110066216193
357 ms 177.38.229.82
10 2026-08-26 02:36 639233078065410564
361 ms 177.38.229.82
9 2026-08-26 02:19 639233067787457832
363 ms 177.38.229.82
8 2026-08-26 02:02 639233057501801162
359 ms 177.38.229.82
7 2026-08-26 01:45 639233047089431703
2222 ms 177.38.229.82
6 2026-08-26 01:27 639233036754790688
385 ms 177.38.229.82
5 2026-08-26 01:10 639233026412602472
4 ms 177.38.229.82
4 2026-08-26 00:53 639233016064066127
175 ms 177.38.229.82
3 2026-08-26 00:36 639233005922655772
3 ms 177.38.229.82
2 2026-08-26 00:18 639232995672256907
354 ms 177.38.229.82
1 2026-08-26 00:01 639232985300872416
492 ms 177.38.229.82