DNS response history for ns2.oolim.net

ns2.oolim.net 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 591 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.oolim.net.
Records on Selected Date

36

Historical checks stored for this nameserver on selected date

Average Latency

591 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 15:12

All timestamps shown in UTC

Latest Resolved IP on Selected Date

115.68.29.124

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.oolim.net

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:12 639235258803654519
578 ms 115.68.29.124
35 2026-08-28 14:55 639235248596087996
554 ms 115.68.29.124
34 2026-08-28 14:38 639235238225955920
513 ms 115.68.29.124
33 2026-08-28 14:21 639235227727862105
504 ms 115.68.29.124
32 2026-08-28 13:26 639235195230848570
544 ms 115.68.29.124
31 2026-08-28 13:09 639235184840503274
510 ms 115.68.29.124
30 2026-08-28 12:52 639235174453894956
764 ms 115.68.29.124
29 2026-08-28 12:34 639235163898672622
761 ms 115.68.29.124
28 2026-08-28 11:41 639235132147470568
574 ms 115.68.29.124
27 2026-08-28 11:24 639235121907744088
486 ms 115.68.29.124
26 2026-08-28 11:07 639235111428014262
782 ms 115.68.29.124
25 2026-08-28 10:49 639235100921813626
493 ms 115.68.29.124
24 2026-08-28 09:55 639235068670703481
517 ms 115.68.29.124
23 2026-08-28 09:38 639235058337459445
509 ms 115.68.29.124
22 2026-08-28 09:21 639235047825109146
496 ms 115.68.29.124
21 2026-08-28 09:03 639235037383229033
728 ms 115.68.29.124
20 2026-08-28 08:10 639235005619242711
526 ms 115.68.29.124
19 2026-08-28 07:53 639234995310346584
486 ms 115.68.29.124
18 2026-08-28 07:36 639234984946548933
509 ms 115.68.29.124
17 2026-08-28 07:19 639234974608077290
774 ms 115.68.29.124
16 2026-08-28 06:25 639234942529845595
492 ms 115.68.29.124
15 2026-08-28 06:08 639234932259126627
512 ms 115.68.29.124
14 2026-08-28 05:51 639234921916735988
775 ms 115.68.29.124
13 2026-08-28 05:33 639234911470038027
787 ms 115.68.29.124
12 2026-08-28 04:40 639234879588411654
489 ms 115.68.29.124
11 2026-08-28 04:23 639234869341589104
511 ms 115.68.29.124
10 2026-08-28 04:06 639234859012216675
752 ms 115.68.29.124
9 2026-08-28 03:49 639234848695364934
517 ms 115.68.29.124
8 2026-08-28 02:56 639234816952458162
531 ms 115.68.29.124
7 2026-08-28 02:39 639234806773081598
747 ms 115.68.29.124
6 2026-08-28 02:22 639234796382955255
499 ms 115.68.29.124
5 2026-08-28 02:04 639234786015782563
520 ms 115.68.29.124
4 2026-08-28 01:11 639234753811917646
758 ms 115.68.29.124
3 2026-08-28 00:53 639234743739767811
499 ms 115.68.29.124
2 2026-08-28 00:37 639234733372362811
755 ms 115.68.29.124
1 2026-08-28 00:19 639234723048550337
513 ms 115.68.29.124