DNS response history for ns2.evibrate.com

ns2.evibrate.com 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 34 DNS check records, 34 successful responses, 0 failed responses, and 452 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.evibrate.com.
Records on Selected Date

34

Historical checks stored for this nameserver on selected date

Average Latency

452 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 10:45

All timestamps shown in UTC

Latest Resolved IP on Selected Date

67.222.143.126

Most recently resolved hosting IP on selected date

Successful Responses

34

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.evibrate.com

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
34 2026-08-26 10:45 639233370841350248
468 ms 67.222.143.126
33 2026-08-26 10:27 639233360361507238
475 ms 67.222.143.126
32 2026-08-26 10:10 639233350067824371
466 ms 67.222.143.126
31 2026-08-26 09:53 639233339545274518
465 ms 67.222.143.126
30 2026-08-26 09:35 639233329214918079
469 ms 67.222.143.126
29 2026-08-26 09:18 639233318749762337
306 ms 67.222.143.126
28 2026-08-26 09:01 639233308387917838
478 ms 67.222.143.126
27 2026-08-26 08:43 639233297961740122
469 ms 67.222.143.126
26 2026-08-26 08:26 639233287487159094
477 ms 67.222.143.126
25 2026-08-26 08:09 639233276995531707
465 ms 67.222.143.126
24 2026-08-26 07:51 639233266521568229
467 ms 67.222.143.126
23 2026-08-26 07:33 639233256081047431
468 ms 67.222.143.126
22 2026-08-26 06:39 639233223620132921
466 ms 67.222.143.126
21 2026-08-26 06:22 639233213287814244
469 ms 67.222.143.126
20 2026-08-26 06:05 639233202925983161
495 ms 67.222.143.126
19 2026-08-26 05:48 639233192644780696
465 ms 67.222.143.126
18 2026-08-26 05:30 639233182401183833
464 ms 67.222.143.126
17 2026-08-26 05:13 639233172074181051
477 ms 67.222.143.126
16 2026-08-26 04:56 639233161808421455
311 ms 67.222.143.126
15 2026-08-26 04:39 639233151357344052
466 ms 67.222.143.126
14 2026-08-26 04:22 639233141034116946
312 ms 67.222.143.126
13 2026-08-26 04:04 639233130828334142
462 ms 67.222.143.126
12 2026-08-26 03:47 639233120373450007
463 ms 67.222.143.126
11 2026-08-26 03:30 639233110066216193
463 ms 67.222.143.126
10 2026-08-26 02:37 639233078065410564
464 ms 67.222.143.126
9 2026-08-26 02:20 639233067787457832
462 ms 67.222.143.126
8 2026-08-26 02:02 639233057501801162
499 ms 67.222.143.126
7 2026-08-26 01:45 639233047089431703
311 ms 67.222.143.126
6 2026-08-26 01:28 639233036754790688
471 ms 67.222.143.126
5 2026-08-26 01:11 639233026412602472
481 ms 67.222.143.126
4 2026-08-26 00:53 639233016064066127
472 ms 67.222.143.126
3 2026-08-26 00:36 639233005922655772
473 ms 67.222.143.126
2 2026-08-26 00:19 639232995672256907
475 ms 67.222.143.126
1 2026-08-26 00:02 639232985300872416
478 ms 67.222.143.126