DNS response history for ns2.regiware.com

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

26

Historical checks stored for this nameserver on selected date

Average Latency

136 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 10:56

All timestamps shown in UTC

Latest Resolved IP on Selected Date

212.50.79.169

Most recently resolved hosting IP on selected date

Successful Responses

26

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.regiware.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
26 2026-08-28 10:56 639235111428014262
99 ms 212.50.79.169
25 2026-08-28 10:39 639235100921813626
81 ms 212.50.79.169
24 2026-08-28 09:45 639235068670703481
7 ms 212.50.79.169
23 2026-08-28 09:28 639235058337459445
75 ms 212.50.79.169
22 2026-08-28 09:10 639235047825109146
76 ms 212.50.79.169
21 2026-08-28 08:53 639235037383229033
77 ms 212.50.79.169
20 2026-08-28 08:00 639235005619242711
26 ms 212.50.79.169
19 2026-08-28 07:43 639234995310346584
10 ms 212.50.79.169
18 2026-08-28 07:25 639234984946548933
29 ms 212.50.79.169
17 2026-08-28 07:08 639234974608077290
46 ms 212.50.79.169
16 2026-08-28 06:15 639234942529845595
8 ms 212.50.79.169
15 2026-08-28 05:58 639234932259126627
126 ms 212.50.79.169
14 2026-08-28 05:40 639234921916735988
18 ms 212.50.79.169
13 2026-08-28 05:23 639234911470038027
78 ms 212.50.79.169
12 2026-08-28 04:30 639234879588411654
2090 ms 212.50.79.169
11 2026-08-28 04:13 639234869341589104
68 ms 212.50.79.169
10 2026-08-28 03:56 639234859012216675
64 ms 212.50.79.169
9 2026-08-28 03:38 639234848695364934
75 ms 212.50.79.169
8 2026-08-28 02:45 639234816952458162
78 ms 212.50.79.169
7 2026-08-28 02:29 639234806773081598
82 ms 212.50.79.169
6 2026-08-28 02:11 639234796382955255
70 ms 212.50.79.169
5 2026-08-28 01:54 639234786015782563
62 ms 212.50.79.169
4 2026-08-28 01:00 639234753811917646
57 ms 212.50.79.169
3 2026-08-28 00:43 639234743739767811
63 ms 212.50.79.169
2 2026-08-28 00:26 639234733372362811
17 ms 212.50.79.169
1 2026-08-28 00:09 639234723048550337
66 ms 212.50.79.169