DNS response history for ns2.serexcorp.com

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

36

Historical checks stored for this nameserver on selected date

Average Latency

322 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:07

All timestamps shown in UTC

Latest Resolved IP on Selected Date

162.240.26.108

Most recently resolved hosting IP on selected date

Successful Responses

36

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.serexcorp.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
36 2026-08-28 15:07 639235258803654519
289 ms 162.240.26.108
35 2026-08-28 14:50 639235248596087996
290 ms 162.240.26.108
34 2026-08-28 14:32 639235238225955920
295 ms 162.240.26.108
33 2026-08-28 14:15 639235227727862105
296 ms 162.240.26.108
32 2026-08-28 13:21 639235195230848570
5 ms 162.240.26.108
31 2026-08-28 13:04 639235184840503274
172 ms 162.240.26.108
30 2026-08-28 12:46 639235174453894956
7 ms 162.240.26.108
29 2026-08-28 12:29 639235163898672622
3 ms 162.240.26.108
28 2026-08-28 11:36 639235132147470568
295 ms 162.240.26.108
27 2026-08-28 11:19 639235121907744088
290 ms 162.240.26.108
26 2026-08-28 11:01 639235111428014262
145 ms 162.240.26.108
25 2026-08-28 10:44 639235100921813626
293 ms 162.240.26.108
24 2026-08-28 09:50 639235068670703481
3 ms 162.240.26.108
23 2026-08-28 09:33 639235058337459445
293 ms 162.240.26.108
22 2026-08-28 09:15 639235047825109146
299 ms 162.240.26.108
21 2026-08-28 08:58 639235037383229033
297 ms 162.240.26.108
20 2026-08-28 08:05 639235005619242711
291 ms 162.240.26.108
19 2026-08-28 07:48 639234995310346584
702 ms 162.240.26.108
18 2026-08-28 07:30 639234984946548933
290 ms 162.240.26.108
17 2026-08-28 07:13 639234974608077290
298 ms 162.240.26.108
16 2026-08-28 06:20 639234942529845595
303 ms 162.240.26.108
15 2026-08-28 06:03 639234932259126627
2171 ms 162.240.26.108
14 2026-08-28 05:45 639234921916735988
295 ms 162.240.26.108
13 2026-08-28 05:28 639234911470038027
290 ms 162.240.26.108
12 2026-08-28 04:35 639234879588411654
287 ms 162.240.26.108
11 2026-08-28 04:18 639234869341589104
158 ms 162.240.26.108
10 2026-08-28 04:01 639234859012216675
288 ms 162.240.26.108
9 2026-08-28 03:43 639234848695364934
306 ms 162.240.26.108
8 2026-08-28 02:50 639234816952458162
290 ms 162.240.26.108
7 2026-08-28 02:34 639234806773081598
300 ms 162.240.26.108
6 2026-08-28 02:16 639234796382955255
153 ms 162.240.26.108
5 2026-08-28 01:59 639234786015782563
349 ms 162.240.26.108
4 2026-08-28 01:05 639234753811917646
348 ms 162.240.26.108
3 2026-08-28 00:48 639234743739767811
456 ms 162.240.26.108
2 2026-08-28 00:31 639234733372362811
376 ms 162.240.26.108
1 2026-08-28 00:14 639234723048550337
356 ms 162.240.26.108