DNS response history for ns2.rayzerdigital.com

ns2.rayzerdigital.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-28. For this date, NameServerHistory found 25 DNS check records, 24 successful responses, 1 failed responses, and 156 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.rayzerdigital.com.
Records on Selected Date

25

Historical checks stored for this nameserver on selected date

Average Latency

156 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 10:41

All timestamps shown in UTC

Latest Resolved IP on Selected Date

78.111.111.132

Most recently resolved hosting IP on selected date

Successful Responses

24

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

4%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.rayzerdigital.com

Showing DNS history for 2026-08-28 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
25 2026-08-28 10:41 639235100921813626
8 ms 78.111.111.132
24 2026-08-28 09:47 639235068670703481
78 ms 78.111.111.132
23 2026-08-28 09:30 639235058337459445
87 ms 78.111.111.132
22 2026-08-28 09:13 639235047825109146
83 ms 78.111.111.132
21 2026-08-28 08:55 639235037383229033
104 ms 78.111.111.132
20 2026-08-28 08:02 639235005619242711
88 ms 78.111.111.132
19 2026-08-28 07:45 639234995310346584
84 ms 78.111.111.132
18 2026-08-28 07:28 639234984946548933
83 ms 78.111.111.132
17 2026-08-28 07:11 639234974608077290
-
16 2026-08-28 06:17 639234942529845595
9 ms 78.111.111.132
15 2026-08-28 06:00 639234932259126627
87 ms 78.111.111.132
14 2026-08-28 05:43 639234921916735988
2069 ms 78.111.111.132
13 2026-08-28 05:25 639234911470038027
86 ms 78.111.111.132
12 2026-08-28 04:32 639234879588411654
89 ms 78.111.111.132
11 2026-08-28 04:15 639234869341589104
75 ms 78.111.111.132
10 2026-08-28 03:58 639234859012216675
80 ms 78.111.111.132
9 2026-08-28 03:41 639234848695364934
75 ms 78.111.111.132
8 2026-08-28 02:48 639234816952458162
99 ms 78.111.111.132
7 2026-08-28 02:31 639234806773081598
26 ms 78.111.111.132
6 2026-08-28 02:14 639234796382955255
74 ms 78.111.111.132
5 2026-08-28 01:56 639234786015782563
104 ms 78.111.111.132
4 2026-08-28 01:03 639234753811917646
77 ms 78.111.111.132
3 2026-08-28 00:46 639234743739767811
52 ms 78.111.111.132
2 2026-08-28 00:29 639234733372362811
45 ms 78.111.111.132
1 2026-08-28 00:11 639234723048550337
77 ms 78.111.111.132