Can't get to Sangoma Support - Anybody else seeing this


(Greg Snover) #1

support.sangoma.com

And yes, I have cleared my Cookies several times…


(TheJames) #2

just clicked and works here…


(Dickson) #3

Check DNS. Its always DNS. Always.


(TheJames) #4

This seems to have been a theme on twitter this weekend :slight_smile:


(Simon Telephonics) #5

OK… what might someone check in DNS for a web browser error that reports “too many redirects”?

DNS-blaming is easy. :slight_smile: but in truth, not usually the problem.


(Greg Snover) #6

DNS-Blaming - My new thought for the day! :wink:

We are using 1.1.1.1 as a primary but checking 8.8.8.8, 9.9.9.9 and 75.75.75.75 all gives the same answer, so I don’t think it’s DNS - I think it’s a Route Issue (probably with Comcast - they are Comcastic!)

Here is a traceroute from my office (Comcast):

Tracing route to support.sangoma.com.cdn.cloudflare.net [172.67.37.154]
over a maximum of 30 hops:

1 8 ms 8 ms 16 ms 96.120.1.233
2 12 ms 10 ms 8 ms po-302-1209-rur01.montbel.nm.albuq.comcast.net [69.139.177.85]
3 11 ms 10 ms 17 ms be-13-ar01.albuquerque.nm.albuq.comcast.net [162.151.97.245]
4 10 ms 8 ms 12 ms 96.108.67.226
5 20 ms 18 ms 18 ms be-36821-cs02.1601milehigh.co.ibone.comcast.net [96.110.44.21]
6 17 ms 15 ms 16 ms be-3202-pe02.910fifteenth.co.ibone.comcast.net [96.110.38.118]
7 20 ms 22 ms 24 ms 50.208.232.118
8 15 ms 15 ms 19 ms 172.67.37.154

Trace complete.

8 Hops is pretty good - Here is a traceroute from Bigleaf (SDN Provider we use):

traceroute to support.sangoma.com (104.22.48.100), 30 hops max, 60 byte packets
1 72.42.244.189.bigleaf.net (72.42.244.189) 1.131 ms 1.115 ms 1.472 ms
2 100.127.0.2 (100.127.0.2) 31.052 ms 29.932 ms 100.127.0.1 (100.127.0.1) 25.817 ms
3 dc-vl101-te-1.cr1.dal.bigleaf.net (162.219.101.49) 26.145 ms 25.328 ms 25.758 ms
4 xe-0-0-57-0.a00.dllstx04.us.bb.gin.ntt.net (128.241.4.205) 26.478 ms 26.460 ms 25.584 ms
5 ae-8.r24.dllstx09.us.bb.gin.ntt.net (129.250.4.169) 31.366 ms 28.044 ms 32.825 ms
6 ae-2.r22.miamfl02.us.bb.gin.ntt.net (129.250.2.218) 56.565 ms 63.594 ms 63.952 ms
7 ae-11.r04.miamfl02.us.bb.gin.ntt.net (129.250.4.21) 57.372 ms 57.047 ms 58.871 ms
8 ae-0.cloudflare.miamfl02.us.bb.gin.ntt.net (131.103.117.62) 62.840 ms 60.431 ms 62.798 ms

The end up at different destinations? And the Bigleaf times out on the trace.


(system) closed #7

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.