What is beacon-6.newrelic.com?

[KevanGuy]

And why is Chrome constantly waiting for it on CP?

[DOOM]

[photon]

New Relic is a monitoring site that monitors site performance and such, that's weird that it's waiting for it, I've never seen that.

[KevanGuy]

Hey pho, this is still happening (not all the time but off an on). When it happens the page doesn't "finish" loading, just keeps waiting for beacon-6.newrelic.com and the loading circle thing at the top left of the tab in Chrome keeps spinning.

Any suggestions?

[photon]

What do you get when you try and ping that address?

[KevanGuy]

It isn't hanging now, should I wait for it to hang again before pinging it?

[photon]

Could do it at both times to see if there's any difference.

[KevanGuy]

K thanks. Not hanging:

Pinging beacon-6.newrelic.com.cdn.cloudflare.net [50.31.164.192] with 32 bytes o
f data:
Reply from 50.31.164.192: bytes=32 time=53ms TTL=247
Reply from 50.31.164.192: bytes=32 time=46ms TTL=247
Reply from 50.31.164.192: bytes=32 time=51ms TTL=247
Reply from 50.31.164.192: bytes=32 time=50ms TTL=247

Ping statistics for 50.31.164.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 53ms, Average = 50ms

[KevanGuy]

Hanging:

Pinging beacon-6.newrelic.com.cdn.cloudflare.net [50.31.164.192] with 32 bytes o
f data:
Reply from 50.31.164.192: bytes=32 time=59ms TTL=247
Reply from 50.31.164.192: bytes=32 time=46ms TTL=248
Reply from 50.31.164.192: bytes=32 time=53ms TTL=247
Reply from 50.31.164.192: bytes=32 time=51ms TTL=247

Ping statistics for 50.31.164.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 59ms, Average = 52ms

[KevanGuy]

Finally figured it out, it was a cookie issue on Chrome.

[DOOM]