cancel
Showing results for 
Search instead for 
Did you mean: 

Internet with modem

Highlighted
Supporting Actor TV
3 0 0

Peering/routing issue

In times like these a lot of people work from home and rely on their Internet connection for that. In my case working from home requires me to connect to a VPN server located in the networks of another Swiss ISP (Init 7).

 

The problem is that although internet access works flawlessly, the connection to said ISP has been a hit and (mostly) miss. This makes it impossible to work at times and pushes me to resort to tethering on my mobile to work around the issue.

 

A colleague of mine (also a customer of UPC) doesn't have the problem, so I did some investigation and found out the following:

 

  • The public IPv4 address that I'm normally assigned comes from the following network:

 

route:          178.82.0.0/16
descr:          cablecom GmbH
descr:          CH-8021 Zuerich
descr:          Switzerland
origin:         AS6830
mnt-by:         AS8404-MNT

 

  • Traceroute to said provider looks like that:

 

 

traceroute to init7.ch (77.109.144.219), 30 hops max, 60 byte packets
 1  10.0.2.2 (10.0.2.2)  0.389 ms  0.641 ms  0.298 ms
 2  192.168.43.1 (192.168.43.1)  5.710 ms  6.248 ms  6.234 ms
 3  10.216.0.1 (10.216.0.1)  141.979 ms  141.929 ms  142.871 ms
 4  192.168.66.130 (192.168.66.130)  142.815 ms  142.808 ms  142.789 ms
 5  1787.eth-trunk20.zhbmb00p-cgn002.bluewin.ch (213.3.229.78)  142.726 ms  142.706 ms  142.664 ms
 6  1187.bundle-ether20.zhbmbbbp-msn002.bluewin.ch (213.3.229.13)  142.727 ms  29.952 ms  42.664 ms
 7  213.3.229.6 (213.3.229.6)  42.336 ms  182.944 ms  35.310 ms
 8  i79tix-055-hun2-0-2.bb.ip-plus.net (138.187.129.223)  35.306 ms  35.295 ms  181.474 ms
 9  init7-tix-ten1.bb.ip-plus.net (193.5.122.250)  182.559 ms  182.627 ms  182.620 ms
10  r1glb1.core.init7.net (77.109.128.238)  182.461 ms  182.440 ms  182.534 ms
11  r1glb3.core.init7.net (82.197.163.128)  182.098 ms  182.069 ms  24.867 ms
12  * * *
  • The address, that my colleague has, comes from the following network:

 

route:          77.56.0.0/15
descr:          Cablecom GmbH
descr:          Zollstrasse42
descr:          CH-8021 Zuerich
descr:          SWITZERLAND
origin:         AS6830
mnt-by:         AS6830-MNT

 

  • Traceroute from his PC looks like that:
traceroute to init7.ch (77.109.144.219), 64 hops max, 52 byte packets
 1  192.168.1.1 (192.168.1.1)  2.396 ms  1.444 ms  2.131 ms
 2  192.168.0.1 (192.168.0.1)  4.234 ms  4.793 ms  3.006 ms
 3  * * *
 4  217-168-54-41.static.cablecom.ch (217.168.54.41)  21.810 ms  16.429 ms  11.739 ms
 5  ch-otf01b-rc1-ae-51-0.aorta.net (84.116.202.237)  16.392 ms  16.658 ms  13.830 ms
 6  ch-zrh01b-ra1-ae-9-0.aorta.net (84.116.134.22)  17.057 ms  18.399 ms  12.835 ms
 7  213.46.171.14 (213.46.171.14)  24.438 ms  22.640 ms  23.474 ms
 8  r1zrh2.core.init7.net (77.109.128.241)  21.277 ms  25.144 ms  25.750 ms
 9  r1glb1.core.init7.net (77.109.128.238)  26.569 ms  23.242 ms  31.961 ms
10  r1glb3.core.init7.net (82.197.163.128)  18.169 ms  22.215 ms  19.716 ms
11  * * *

My question here is:

Can something be done to resolve that issue? I have constant problems during working hours, my colleague has no problems at all.

 

 

4 REPLIES 4
Highlighted
Supporting Actor TV
3 0 0

Re: Peering/routing issue

I'm sorry the first traceroute output was false. Here is the correct one:
traceroute to init7.ch (77.109.144.219), 30 hops max, 60 byte packets
1 10.0.2.2 (10.0.2.2) 0.318 ms 0.298 ms 0.172 ms
2 192.168.1.1 (192.168.1.1) 10.219 ms 10.321 ms 10.447 ms
3 * * *
4 * * *
5 217-168-53-205.static.cablecom.ch (217.168.53.205) 24.248 ms 24.496 ms 24.544 ms
6 ch-zrh03a-rc1-ae-50-0.aorta.net (84.116.200.241) 35.536 ms 23.108 ms 23.164 ms
7 ch-zrh01b-ra1-ae-1-0.aorta.net (84.116.134.142) 22.313 ms 44.287 ms 14.100 ms
8 213.46.171.14 (213.46.171.14) 29.138 ms 32.044 ms 31.721 ms
9 r1zrh2.core.init7.net (77.109.128.241) 30.740 ms 30.837 ms 30.959 ms
10 r1glb1.core.init7.net (77.109.128.238) 36.696 ms 30.807 ms 26.082 ms
11 r1glb3.core.init7.net (82.197.163.128) 25.549 ms 25.219 ms 27.746 ms
12 * * *
Highlighted
Community Manager
5537 1440 425

Re: Peering/routing issue

@STM , Welcome to the community! 

 

I recommend you to contact our support, as your request will be processed by the specialists and a ticket will be opened.

 

Greetings

Daniele


Member of @UPC_Team
Highlighted
Supporting Actor TV
3 0 0

Re: Peering/routing issue

Hi Daniele,

 

Thanks for the quick response. Where do I open a ticket?

 

I called support yesterday and my experience was let's say "suboptimal".

 

Greetings,

Stefan

Highlighted
Community Manager
5537 1440 425

Re: Peering/routing issue

@STM , Please contact them again and ask them to open a ticket for the specialists. Explain to them exactly what your error pattern is.

 

Greetings
Daniele


Member of @UPC_Team