Inconsistencies between DC's

We have a client that is unable to access a website, in this case We’ve also had an employee verify the issue at home as well, over the same ISP (Charter). Anycast on Charter has this client and this employee routing into the SIX and hitting CF’s services there. Running nslookup through a different ISP and route goes into San Jose and the domain resolves correctly in that DC. I’m hoping someone in CF support hangs out here and can either check out the different resolutions in different DC’s. It’s been ongoing for more than 2 days.

This is an ongoing issue:

Thanks @sdayman.

1 Like