DNS response history for ns2.bridalmums.com

ns2.bridalmums.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-25. For this date, NameServerHistory found 30 DNS check records, 30 successful responses, 0 failed responses, and 394 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.bridalmums.com.
Records on Selected Date

30

Historical checks stored for this nameserver on selected date

Average Latency

394 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 10:06

All timestamps shown in UTC

Latest Resolved IP on Selected Date

37.49.151.28

Most recently resolved hosting IP on selected date

Successful Responses

30

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

Showing DNS history for 2026-08-25 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
30 2026-08-25 10:06 639232482235303141
399 ms 37.49.151.28
29 2026-08-25 09:48 639232471861770303
405 ms 37.49.151.28
28 2026-08-25 09:31 639232461630217327
414 ms 37.49.151.28
27 2026-08-25 09:14 639232451282965990
419 ms 37.49.151.28
26 2026-08-25 08:57 639232440814614938
418 ms 37.49.151.28
25 2026-08-25 08:39 639232430410720425
417 ms 37.49.151.28
24 2026-08-25 08:22 639232420003096185
418 ms 37.49.151.28
23 2026-08-25 08:05 639232409467287444
424 ms 37.49.151.28
22 2026-08-25 07:47 639232399077195997
405 ms 37.49.151.28
21 2026-08-25 07:30 639232388731528337
422 ms 37.49.151.28
20 2026-08-25 07:12 639232378288598612
4 ms 37.49.151.28
19 2026-08-25 06:18 639232346196373643
432 ms 37.49.151.28
18 2026-08-25 06:02 639232336112370741
1016 ms 37.49.151.28
17 2026-08-25 05:45 639232326146508970
420 ms 37.49.151.28
16 2026-08-25 05:28 639232316189381720
3 ms 37.49.151.28
15 2026-08-25 05:12 639232306217998913
419 ms 37.49.151.28
14 2026-08-25 04:55 639232296255744174
2 ms 37.49.151.28
13 2026-08-25 04:38 639232286095760789
412 ms 37.49.151.28
12 2026-08-25 04:21 639232276086186273
409 ms 37.49.151.28
11 2026-08-25 04:05 639232265900986425
413 ms 37.49.151.28
10 2026-08-25 03:48 639232255723518075
408 ms 37.49.151.28
9 2026-08-25 03:31 639232245484452890
413 ms 37.49.151.28
8 2026-08-25 03:14 639232235157175331
409 ms 37.49.151.28
7 2026-08-25 02:20 639232203197189095
416 ms 37.49.151.28
6 2026-08-25 02:03 639232192844564298
415 ms 37.49.151.28
5 2026-08-25 01:46 639232182496008942
401 ms 37.49.151.28
4 2026-08-25 01:29 639232172197053132
419 ms 37.49.151.28
3 2026-08-25 00:35 639232140250307418
424 ms 37.49.151.28
2 2026-08-25 00:18 639232129927860324
414 ms 37.49.151.28
1 2026-08-25 00:01 639232119551972438
417 ms 37.49.151.28