DNS response history for ns2.urigor.com

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

28

Historical checks stored for this nameserver on selected date

Average Latency

259 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 11:33

All timestamps shown in UTC

Latest Resolved IP on Selected Date

85.215.117.175

Most recently resolved hosting IP on selected date

Successful Responses

28

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.urigor.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
28 2026-08-28 11:33 639235132147470568
21 ms 85.215.117.175
27 2026-08-28 11:16 639235121907744088
51 ms 85.215.117.175
26 2026-08-28 10:59 639235111428014262
45 ms 85.215.117.175
25 2026-08-28 10:41 639235100921813626
38 ms 85.215.117.175
24 2026-08-28 09:47 639235068670703481
51 ms 85.215.117.175
23 2026-08-28 09:30 639235058337459445
46 ms 85.215.117.175
22 2026-08-28 09:13 639235047825109146
47 ms 85.215.117.175
21 2026-08-28 08:55 639235037383229033
52 ms 85.215.117.175
20 2026-08-28 08:02 639235005619242711
69 ms 85.215.117.175
19 2026-08-28 07:45 639234995310346584
53 ms 85.215.117.175
18 2026-08-28 07:28 639234984946548933
42 ms 85.215.117.175
17 2026-08-28 07:11 639234974608077290
44 ms 85.215.117.175
16 2026-08-28 06:17 639234942529845595
30 ms 85.215.117.175
15 2026-08-28 06:00 639234932259126627
2098 ms 85.215.117.175
14 2026-08-28 05:43 639234921916735988
40 ms 85.215.117.175
13 2026-08-28 05:25 639234911470038027
79 ms 85.215.117.175
12 2026-08-28 04:32 639234879588411654
2036 ms 85.215.117.175
11 2026-08-28 04:15 639234869341589104
43 ms 85.215.117.175
10 2026-08-28 03:58 639234859012216675
39 ms 85.215.117.175
9 2026-08-28 03:41 639234848695364934
40 ms 85.215.117.175
8 2026-08-28 02:48 639234816952458162
44 ms 85.215.117.175
7 2026-08-28 02:31 639234806773081598
74 ms 85.215.117.175
6 2026-08-28 02:14 639234796382955255
2013 ms 85.215.117.175
5 2026-08-28 01:56 639234786015782563
43 ms 85.215.117.175
4 2026-08-28 01:03 639234753811917646
9 ms 85.215.117.175
3 2026-08-28 00:46 639234743739767811
46 ms 85.215.117.175
2 2026-08-28 00:29 639234733372362811
9 ms 85.215.117.175
1 2026-08-28 00:11 639234723048550337
49 ms 85.215.117.175