Jump to content
EN
Play

Forum

network issues oct 13


Recommended Posts

issues today too :(

 

 

Target Name: tankionline.com

IP: 62.152.57.2

Date/Time: 2011-10-13 20:00:00 to 2011-10-13 20:00:30

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

12 24 0 0,0 33 98 40 xe-8-2-0.ams12.ip4.tinet.net [89.149.185.250]

13 24 0 0,0 33 40 33 ge-5-1.hsa3.SanJose1.Level3.net [4.68.110.141]

14 24 0 0,0 33 35 33 ae-33-51.ebr1.Amsterdam1.Level3.net [4.69.139.129]

15 24 0 0,0 31 41 34 ae-47-47.ebr2.Dusseldorf1.Level3.net [4.69.143.206]

16 24 0 0,0 31 42 34 ae-22-22.ebr1.Dusseldorf1.Level3.net [4.69.143.185]

17 24 0 0,0 32 38 33 ae-47-47.ebr2.Frankfurt1.Level3.net [4.69.143.174]

18 24 0 0,0 31 36 31 ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]

19 24 0 0,0 32 99 45 ae-4-90.edge3.Frankfurt1.Level3.net [4.69.154.199]

20 23 0 0,0 32 231 49 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 22 22 100,0 0 0 0 [-]

22 22 22 100,0 0 0 0 [-]

23 22 22 100,0 0 0 0 [-]

24 22 22 100,0 0 0 0 [-]

25 22 22 100,0 0 0 0 [-]

26 22 22 100,0 0 0 0 [-]

27 22 22 100,0 0 0 0 [-]

28 22 22 100,0 0 0 0 [-]

29 22 22 100,0 0 0 0 [-]

30 22 22 100,0 0 0 0 [-]

31 22 22 100,0 0 0 0 [-]

32 22 22 100,0 0 0 0 [-]

33 22 22 100,0 0 0 0 [-]

34 22 22 100,0 0 0 0 [-]

35 22 22 100,0 0 0 0 [-]

 

Destination not reached in 35 hops

 

 

Target Name: tankionline.com

IP: 62.152.57.2

Date/Time: 2011-10-13 20:04:20 to 2011-10-13 20:06:21

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

12 120 0 0,0 31 93 35 xe-5-2-0.ams21.ip4.tinet.net [89.149.187.205]

13 120 0 0,0 30 78 31 te3-7.ccr01.ams05.atlas.cogentco.com [130.117.14.245]

14 120 0 0,0 30 54 31 te0-3-0-6.ccr21.ams03.atlas.cogentco.com [130.117.1.81]

15 120 1 0,8 34 58 34 te0-3-0-3.ccr21.fra03.atlas.cogentco.com [154.54.39.182]

16 120 0 0,0 60 67 60 te0-1-0-0.ccr21.muc01.atlas.cogentco.com [130.117.0.66]

17 120 0 0,0 60 73 60 te0-0-0-5.ccr21.bts01.atlas.cogentco.com [154.54.38.242]

18 120 0 0,0 60 225 63 te7-1.ccr01.kbp01.atlas.cogentco.com [154.54.39.121]

19 117 117 100,0 0 0 0 [149.11.94.2]

20 117 117 100,0 0 0 0 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 117 117 100,0 0 0 0 te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250]

22 117 117 100,0 0 0 0 tankionline.com [62.152.57.2]

 

 

Target Name: tankionline.com

IP: 62.152.57.2

Date/Time: 2011-10-13 20:06:57 to 2011-10-13 20:08:54

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

12 82 0 0,0 31 95 36 xe-5-2-0.ams21.ip4.tinet.net [89.149.187.205]

13 82 0 0,0 30 227 33 te3-7.ccr01.ams05.atlas.cogentco.com [130.117.14.245]

14 82 0 0,0 30 32 30 te0-3-0-6.ccr21.ams03.atlas.cogentco.com [130.117.1.81]

15 82 0 0,0 34 36 34 te0-3-0-3.ccr21.fra03.atlas.cogentco.com [154.54.39.182]

16 82 0 0,0 60 62 60 te0-1-0-0.ccr21.muc01.atlas.cogentco.com [130.117.0.66]

17 82 0 0,0 60 61 60 te0-0-0-5.ccr21.bts01.atlas.cogentco.com [154.54.38.242]

18 82 0 0,0 60 178 66 te7-1.ccr01.kbp01.atlas.cogentco.com [154.54.39.121]

19 80 80 100,0 0 0 0 [-]

20 80 80 100,0 0 0 0 [-]

21 80 80 100,0 0 0 0 [-]

22 80 80 100,0 0 0 0 [-]

23 80 80 100,0 0 0 0 [-]

24 80 80 100,0 0 0 0 [-]

25 80 80 100,0 0 0 0 [-]

26 80 80 100,0 0 0 0 [-]

27 80 80 100,0 0 0 0 [-]

28 80 80 100,0 0 0 0 [-]

29 80 80 100,0 0 0 0 [-]

30 80 80 100,0 0 0 0 [-]

31 80 80 100,0 0 0 0 [-]

32 80 80 100,0 0 0 0 [-]

33 80 80 100,0 0 0 0 [-]

34 80 80 100,0 0 0 0 [-]

35 80 80 100,0 0 0 0 [-]

 

Destination not reached in 35 hops

 

Target Name: tankionline.com

IP: 62.152.57.2

Date/Time: 2011-10-13 20:11:53 to 2011-10-13 20:13:54

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

12 120 0 0,0 31 98 34 xe-5-2-0.ams21.ip4.tinet.net [89.149.187.205]

13 120 0 0,0 30 223 35 te3-7.ccr01.ams05.atlas.cogentco.com [130.117.14.245]

14 120 0 0,0 30 34 30 te0-3-0-6.ccr21.ams03.atlas.cogentco.com [130.117.1.81]

15 120 0 0,0 34 37 34 te0-3-0-3.ccr21.fra03.atlas.cogentco.com [154.54.39.182]

16 120 0 0,0 60 61 60 te0-1-0-0.ccr21.muc01.atlas.cogentco.com [130.117.0.66]

17 120 0 0,0 60 65 60 te0-0-0-5.ccr21.bts01.atlas.cogentco.com [154.54.38.242]

18 120 1 0,8 60 270 79 te7-1.ccr01.kbp01.atlas.cogentco.com [154.54.39.121]

19 120 31 25,8 60 416 121 [149.11.94.2]

20 117 117 100,0 0 0 0 te4-1-10-alpha.msk.citytelecom.ru [217.65.1.241]

21 117 117 100,0 0 0 0 te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250]

22 117 117 100,0 0 0 0 tankionline.com [62.152.57.2]

Share this post


Link to post
Share on other sites

I used PingPlotter, kind of like cmd->ping but on steroids.

 

Hop Sent Err PL% Min Max Avg Host Name / [iP]

Hop= routernumber along the way

Sent= number of pings sent

Err= Errors, usually an indicator that something is very very wrong with hardware/software on that Hop. Such as "no route to host"

PL%= PacketLoss Percentage

Min= quickest ping of the [sent-number](120 in this case) pings

Max= slowest ping of the [sent-number](120 in this case) pings

Avg= averages ping time of the [sent-number](120 in this case) pings

 

17 120 0 0,0 60 65 60 te0-0-0-5.ccr21.bts01.atlas.cogentco.com [154.54.38.242]

18 120 1 0,8 60 270 79 te7-1.ccr01.kbp01.atlas.cogentco.com [154.54.39.121]

19 120 31 25,8 60 416 121 [149.11.94.2]

20 117 117 100,0 0 0 0 te4-1-10-alpha.msk.citytelecom.ru [217.65.1.241]

21 117 117 100,0 0 0 0 te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250]

22 117 117 100,0 0 0 0 tankionline.com [62.152.57.2]

 

Here one sees that when traffic is going from the cogentco.com network to the citytelecom.ru network it gets lost, the network infrastructure is until that point.

Share this post


Link to post
Share on other sites

:hunf: are you a super brain or something ?

ho can understand that thingy ? :?

 

I think no one does :?.

I dont understand than neither o.o

Send it to dev.. so they will break their head to understand that..

I didnt even understand what i wrote myself

Share this post


Link to post
Share on other sites

If that is a traceroute' date=' then you stopped getting reply after a specific location. Pretty sure it's related to your ISP. If it still persists you might want to contact them.[/quote']

 

Do you really understand this :shock:

Share this post


Link to post
Share on other sites

If that is a traceroute' date=' then you stopped getting reply after a specific location. Pretty sure it's related to your ISP. If it still persists you might want to contact them.[/quote']

I doubt it's my ISPs problem since it's way way outside my ISPs network.

12 24 0 0,0 33 98 40 xe-8-2-0.ams12.ip4.tinet.net [89.149.185.250]

13 24 0 0,0 33 40 33 ge-5-1.hsa3.SanJose1.Level3.net [4.68.110.141]

14 24 0 0,0 33 35 33 ae-33-51.ebr1.Amsterdam1.Level3.net [4.69.139.129]

15 24 0 0,0 31 41 34 ae-47-47.ebr2.Dusseldorf1.Level3.net [4.69.143.206]

16 24 0 0,0 31 42 34 ae-22-22.ebr1.Dusseldorf1.Level3.net [4.69.143.185]

17 24 0 0,0 32 38 33 ae-47-47.ebr2.Frankfurt1.Level3.net [4.69.143.174]

18 24 0 0,0 31 36 31 ae-92-92.csw4.Frankfurt1.Level3.net [4.69.140.30]

19 24 0 0,0 32 99 45 ae-4-90.edge3.Frankfurt1.Level3.net [4.69.154.199]

20 23 0 0,0 32 231 49 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 22 22 100,0 0 0 0 [-]

22 22 22 100,0 0 0 0 [-]

[....]

35 22 22 100,0 0 0 0 [-]

 

Destination not reached in 35 hops

 

Here is a sample of a working route

 

12 xe-8-2-0.ams12.ip4.tinet.net [89.149.185.250]

13 ge-5-1.hsa3.SanJose1.Level3.net [4.68.110.141]

14 ae-33-51.ebr1.Amsterdam1.Level3.net [4.69.139.129]

15 ae-47-47.ebr2.Dusseldorf1.Level3.net [4.69.143.206]

16 ae-22-22.ebr1.Dusseldorf1.Level3.net [4.69.143.185]

17 ae-48-48.ebr2.Frankfurt1.Level3.net [4.69.143.178]

18 ae-72-72.csw2.Frankfurt1.Level3.net [4.69.140.22]

19 ae-2-70.edge3.Frankfurt1.Level3.net [4.69.154.71]

20 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 te4-2-740-altera.spb.citytelecom.ru [217.65.1.229]

22 te4-1-21-alpha.msk.citytelecom.ru [217.65.1.197]

23 te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250]

24 tankionline.com [62.152.57.2]

 

 

tinet is the route my ISP takes to tankionline, as tinet is what my ISP has peering with when it comes to traffic outside my country it seems,

tinet then uses Level3 to reach citytelecom as Level3 has peering with citytelecom it seems

citytelecom is the(only one??) ISP of the datacenter where tankionline has its servers.

 

One notices the

20 23 0 0,0 32 231 49 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 22 22 100,0 0 0 0 [-]

 

Likely cause is Level3 is unable to reach the citytelecom network for some reason.

 

 

After a while, tinet then tries an alternative backup route

12 120 0 0,0 31 93 35 xe-5-2-0.ams21.ip4.tinet.net [89.149.187.205]

13 120 0 0,0 30 78 31 te3-7.ccr01.ams05.atlas.cogentco.com [130.117.14.245]

14 120 0 0,0 30 54 31 te0-3-0-6.ccr21.ams03.atlas.cogentco.com [130.117.1.81]

15 120 1 0,8 34 58 34 te0-3-0-3.ccr21.fra03.atlas.cogentco.com [154.54.39.182]

16 120 0 0,0 60 67 60 te0-1-0-0.ccr21.muc01.atlas.cogentco.com [130.117.0.66]

17 120 0 0,0 60 73 60 te0-0-0-5.ccr21.bts01.atlas.cogentco.com [154.54.38.242]

18 120 0 0,0 60 225 63 te7-1.ccr01.kbp01.atlas.cogentco.com [154.54.39.121]

19 117 117 100,0 0 0 0 [149.11.94.2]

20 117 117 100,0 0 0 0 IPTRIPLEPLA.edge3.Frankfurt1.Level3.net [212.162.40.194]

21 117 117 100,0 0 0 0 te4-4-9-fibius.msk.citytelecom.ru [217.65.1.250]

22 117 117 100,0 0 0 0 tankionline.com [62.152.57.2]

it is now going via the cogentco network

and then via 149.11.94.2 (which i have no idea who it belong to, probably a peering) then enters the Level3 network which somehow then jumps all the way to te4-4-9-fibius.msk.citytelecom.ru.

100% packetloss starting from 149.11.94.2 though, and the 3 missing packets (117 vs 120) is probably due to the routechange or something.

 

The issues were experienced on oct 12 and oct 13, but since I play very irregularly it's probably not limited to that, but it could also be so.

 

A guess is a malfunctioning router somewhere around where citytelecom has it's peering with Level3, 149.11.94.2 and cogentco.

 

For the record, I don't experience the issue currently.

 

And for those that find all these numbers etc very confusing, here is a brief simple explanation:

Sometimes when you browse the web, some sites doesn't load/respond(but almost all other sites works), sites that you know should work, and then a few hour later they work again, that is sometimes caused by routing issues as described above.

Where the routing issues occur will result in different impact.

Think of networking as roads/railways and things will be a lot easier.

Here is are videos that somewhat explains what's going on:

http://www.youtube.com/watch?v=HOaIqQAeaik

Share this post


Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

This topic is now closed to further replies.
×
×
  • Create New...