Connectivity problems

August 25th, 2003, 10:59 PM

FYI: 3DG has been on the wrong end of some serious connectivity problems for several months now. It's not accessible from at least one large ISP in Canada (my former ISP); it's anyone's guess how many other parts of the internet can't get through. I can't post traceroutes because I've switched ISPs but the system which is blackholing packets is within two or three hops of the server which hosts this site.

August 26th, 2003, 12:00 AM

Which ISP ?

I know 3DG works though Sympatico, and Rogers.. Which last I checked where the big 2

Ryoken

General Phoenix · August 26th, 2003, 11:52 PM

Actually, this has been a problem for several of our users over the last couple months. Fabio has been working to find out where the problem lies, but we've been unable to find many commonalities between the traceroutes of the users affected.

Last I heard, it was still being researched.

August 27th, 2003, 12:05 AM

over here I've had quite often that 3dg appears like uhm...

well like as if my computer couldn't connect to the internet

but the other sites work fine at that point.

though if you go back an hour later, it's magically there again.

as far as I know chris had a similar if not the same problem.

moovok · August 29th, 2003, 01:45 PM

Several times I haven't been able to get on, its' been about a day, and then the next I'm able. So, no major worry there

October 3rd, 2003, 05:45 PM

I finally got around to running a traceroute from an effected ISP/area (Sympatico DSL in Toronto):

Tracing route to 3dgladiators.net [209.197.236.22]
over a maximum of 30 hops:

Code:

  1    10 ms    10 ms    10 ms  HSE-Kingston-ppp193398.sympatico.ca [64.229.9.1]

  2   <10 ms    10 ms    10 ms  64.230.244.130
  3    20 ms   <10 ms    10 ms  206.108.107.173
  4    20 ms    20 ms    20 ms  206.108.103.114
  5    10 ms    20 ms    10 ms  206.108.108.246
  6    10 ms    10 ms    10 ms  core-02-ge-0-3-0-0.chcg.twtelecom.net [168.215.53.193]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.

The really weird thing, however, is that a traceroute from Telus/Vancouver also dies inside Time Warner's network even though this is the connection I'm using to post this message.

Code:

[c:\documents]tracert www.3dgladiators.net

Tracing route to 3dgladiators.net [209.197.236.22]
over a maximum of 30 hops:

  1    10 ms     *       10 ms  209.53.1.233
  2    10 ms    10 ms    10 ms  209.53.142.26
  3    10 ms    10 ms    10 ms  nwmrbc01gr01.bb.telus.com [154.11.4.98]
  4    30 ms    40 ms    41 ms  nwmrbc01br01.bb.telus.com [154.11.10.53]
  5    30 ms    30 ms    40 ms  sttlwa01gr02.bb.telus.com [209.53.75.178]
  6    31 ms    40 ms    40 ms  plalca01gr00.bb.telus.com [154.11.10.2]
  7    30 ms    40 ms    40 ms  peer.plalca01gr00.bb.telus.com [154.11.3.98]
  8    30 ms    40 ms    40 ms  dist-01-so-3-2-0-0.okld.twtelecom.net [66.192.250.37]
  9    40 ms    40 ms    41 ms  core-01-so-0-0-0-0.mdso.twtelecom.net [168.215.55.78]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.