DNS response history for ns2.weborizer.com

ns2.weborizer.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-27. For this date, NameServerHistory found 35 DNS check records, 35 successful responses, 0 failed responses, and 310 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.weborizer.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

310 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:10

All timestamps shown in UTC

Latest Resolved IP on Selected Date

147.135.122.245

Most recently resolved hosting IP on selected date

Successful Responses

35

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

Showing DNS history for 2026-08-27 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
35 2026-08-27 11:10 639234253963286387
343 ms 147.135.122.245
34 2026-08-27 10:53 639234243654907465
368 ms 147.135.122.245
33 2026-08-27 10:35 639234233269654413
343 ms 147.135.122.245
32 2026-08-27 10:18 639234222943951923
260 ms 147.135.122.245
31 2026-08-27 10:01 639234212558002823
341 ms 147.135.122.245
30 2026-08-27 09:43 639234202117531850
287 ms 147.135.122.245
29 2026-08-27 09:26 639234191649612722
299 ms 147.135.122.245
28 2026-08-27 09:08 639234181105879568
346 ms 147.135.122.245
27 2026-08-27 08:51 639234170713214496
349 ms 147.135.122.245
26 2026-08-27 08:34 639234160341037652
569 ms 147.135.122.245
25 2026-08-27 08:16 639234149799404224
287 ms 147.135.122.245
24 2026-08-27 07:59 639234139553286469
288 ms 147.135.122.245
23 2026-08-27 07:05 639234107183588293
369 ms 147.135.122.245
22 2026-08-27 06:48 639234096905435724
293 ms 147.135.122.245
21 2026-08-27 06:31 639234086579410775
364 ms 147.135.122.245
20 2026-08-27 06:14 639234076291157956
344 ms 147.135.122.245
19 2026-08-27 05:57 639234065981939454
250 ms 147.135.122.245
18 2026-08-27 05:39 639234055548642997
275 ms 147.135.122.245
17 2026-08-27 05:22 639234045267979603
323 ms 147.135.122.245
16 2026-08-27 05:05 639234034999717463
288 ms 147.135.122.245
15 2026-08-27 04:48 639234024739225358
284 ms 147.135.122.245
14 2026-08-27 04:31 639234014311170162
307 ms 147.135.122.245
13 2026-08-27 04:13 639234003806017640
219 ms 147.135.122.245
12 2026-08-27 03:55 639233993356203030
524 ms 147.135.122.245
11 2026-08-27 03:02 639233961301716608
250 ms 147.135.122.245
10 2026-08-27 02:45 639233950834200647
292 ms 147.135.122.245
9 2026-08-27 02:27 639233940431849026
233 ms 147.135.122.245
8 2026-08-27 02:10 639233930110596398
205 ms 147.135.122.245
7 2026-08-27 01:53 639233919705434540
257 ms 147.135.122.245
6 2026-08-27 01:36 639233909452807845
280 ms 147.135.122.245
5 2026-08-27 01:18 639233899096420820
259 ms 147.135.122.245
4 2026-08-27 01:01 639233888707824939
268 ms 147.135.122.245
3 2026-08-27 00:44 639233878461203802
327 ms 147.135.122.245
2 2026-08-27 00:27 639233868060868209
275 ms 147.135.122.245
1 2026-08-27 00:09 639233857450922991
298 ms 147.135.122.245