Upc users

Rebel021

Limerick server


Dublin Server

Enigma IE

Shammy, you said Munster BB are part of BBNET? The INET matrix backs up the tracert results.

BBNET peer with both Eircom & Digiweb, but not UPC as we know. UPC need to peer with BBNET but UPC don't have an open peering policy for whatever reason. I'm still waiting for formal written response from UPC as to why they won't peer with BBNet/MunsterBB.

Tea_Bag

if anyone needs me to start complaining, i will help where possible. i gave them alot of grief over their EPC24 25 router they ship, so they know me well enough to not back down id say.

Shammy

Tea_Bag wrote: »

if anyone needs me to start complaining, i will help where possible. i gave them alot of grief over their EPC24 25 router they ship, so they know me well enough to not back down id say.

If your a upc customer mate , e-mail a complaint asking why upc wont peer with bbnet .

Enigma IE

Shammy wrote: »

If your a upc customer mate , e-mail a complaint asking why upc wont peer with bbnet .

+1

matt-dublin

Mbb support team, can I suggest you try adding a static route to shammys ip address on your core via Eircom for testing?

I don't mind u can use mine as well as I'm a UPC customer.

matt-dublin

munster bb, are you reselling another companies bb?

shammy, just curious what your ping times are like to other sites?
ive always notices fixed wireless broadband has high latency rates anyway but i do see the routing issue as well. even so, ping times shouldnt be more than 75-135-ms

as above ive suggested mbb route trybroute their traffic via eircom and see if that has an affect but i dont even know if its posible
cos im not well up on their infrastructure and bgp routing.

what you could do is log a call with upc to route their mbb staticly via eircom but again highly unlikely as youre not a business or enterprise class bb user.

from previous experience with ntl and my last company trying to get ntl to route my corporate traffic via level 3 to bosoton from dublin instead of cogent was a pain. the latency difference was over 200ms and it took me 6 weeks to get them to update their routing tables and weights.

this may be a losing battle youre fighting here. the quickest solution may be for mbb or their provider to purchase a fixed link to upc but from a business perspective for them it might not make sense.

Shammy

matt-dublin wrote: »

shammy, just curious what your ping times are like to other sites?
ive always notices fixed wireless broadband has high latency rates anyway but i do see the routing issue as well. even so, ping times shouldnt be more than 75-135-ms
.

http://www.boards.ie/vbulletin/showpost.php?p=70551758&postcount=59

matt-dublin

Don't think thisvwill be changing any time soon...
http://www.google.ie/search?q=UPC+ireland+inex+peers&ie=UTF-8&oe=UTF-8&hl=en&client=safari

Looks like they've been sending traffic to holland since before 2004

Should be easy enough for UPC to add static routes to pass mbb through their inex routers.

I'm wondering if UPC are recieving routes correctly for mbb subnets or are mbb advertising their routes correctly.

All very strange

beertons

bkehoe

Still no change in routing to Cogentco customers from UPC...

Here's a trace route to an IP in Dublin this morning, taking the same routing to New York as it has for months. About 5 months ago they were peering somewhere more sensible, London I think, as I didn't have bandwidth issues to Cogentco customers then.

Waterford - Dublin - London - New York - Boston - Liverpool - Manchester - Dublin!!

1  vigor.router (192.168.1.1)  1.148 ms  0.715 ms  0.698 ms
 2  my.router (192.168.2.190)  8.647 ms  11.358 ms  7.897 ms
 3  10.98.64.1 (10.98.64.1)  15.859 ms  13.502 ms  15.157 ms
 4  089-101-174078.ntlworld.ie (89.101.174.78)  21.265 ms  46.560 ms  21.712 ms
 5  uk-lon01b-rd1-xe-1-1-2.aorta.net (84.116.132.45)  118.739 ms  116.909 ms  134.552 ms
 6  84.116.132.226 (84.116.132.226)  110.668 ms
    84.116.132.234 (84.116.132.234)  102.050 ms  99.240 ms
 7  us-nyc01b-rd1-pos-10-0.aorta.net (213.46.160.154)  101.527 ms  133.648 ms  102.774 ms
 8  us-nyc01b-ri1-ge-0-1-0.aorta.net (213.46.190.178)  124.287 ms  104.299 ms  107.055 ms
 9  xe-4-1-0.edge1.newyork1.level3.net (4.78.132.93)  116.598 ms  117.068 ms
    xe-8-3-0.edge1.newyork1.level3.net (4.78.164.221)  140.357 ms
10  * * *
11  te0-3-0-5.mpd21.jfk02.atlas.cogentco.com (154.54.26.61)  152.471 ms
    te0-1-0-4.mpd21.jfk02.atlas.cogentco.com (154.54.31.1)  156.148 ms
    te0-1-0-4.mpd22.jfk02.atlas.cogentco.com (154.54.31.5)  152.911 ms
12  te0-2-0-6.ccr21.bos01.atlas.cogentco.com (154.54.44.22)  226.500 ms
    te0-4-0-3.ccr21.bos01.atlas.cogentco.com (154.54.44.18)  229.105 ms
    te0-3-0-5.ccr21.bos01.atlas.cogentco.com (154.54.44.34)  229.117 ms
13  te0-3-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.230)  241.017 ms
    te0-2-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.190)  227.103 ms
    te0-1-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.182)  224.973 ms
14  te3-2.ccr01.man01.atlas.cogentco.com (130.117.51.253)  236.195 ms  232.509 ms  239.429 ms
15  te1-1.ccr01.dub01.atlas.cogentco.com (130.117.3.213)  229.303 ms  228.688 ms  234.848 ms
16  149.6.4.166 (149.6.4.166)  223.717 ms  228.552 ms  234.914 ms

Shammy

bkehoe wrote: »

Still no change in routing to Cogentco customers from UPC...

Here's a trace route to an IP in Dublin this morning, taking the same routing to New York as it has for months. About 5 months ago they were peering somewhere more sensible, London I think, as I didn't have bandwidth issues to Cogentco customers then.

Waterford - Dublin - London - New York - Boston - Liverpool - Manchester - Dublin!!

1  vigor.router (192.168.1.1)  1.148 ms  0.715 ms  0.698 ms
 2  my.router (192.168.2.190)  8.647 ms  11.358 ms  7.897 ms
 3  10.98.64.1 (10.98.64.1)  15.859 ms  13.502 ms  15.157 ms
 4  089-101-174078.ntlworld.ie (89.101.174.78)  21.265 ms  46.560 ms  21.712 ms
 5  uk-lon01b-rd1-xe-1-1-2.aorta.net (84.116.132.45)  118.739 ms  116.909 ms  134.552 ms
 6  84.116.132.226 (84.116.132.226)  110.668 ms
    84.116.132.234 (84.116.132.234)  102.050 ms  99.240 ms
 7  us-nyc01b-rd1-pos-10-0.aorta.net (213.46.160.154)  101.527 ms  133.648 ms  102.774 ms
 8  us-nyc01b-ri1-ge-0-1-0.aorta.net (213.46.190.178)  124.287 ms  104.299 ms  107.055 ms
 9  xe-4-1-0.edge1.newyork1.level3.net (4.78.132.93)  116.598 ms  117.068 ms
    xe-8-3-0.edge1.newyork1.level3.net (4.78.164.221)  140.357 ms
10  * * *
11  te0-3-0-5.mpd21.jfk02.atlas.cogentco.com (154.54.26.61)  152.471 ms
    te0-1-0-4.mpd21.jfk02.atlas.cogentco.com (154.54.31.1)  156.148 ms
    te0-1-0-4.mpd22.jfk02.atlas.cogentco.com (154.54.31.5)  152.911 ms
12  te0-2-0-6.ccr21.bos01.atlas.cogentco.com (154.54.44.22)  226.500 ms
    te0-4-0-3.ccr21.bos01.atlas.cogentco.com (154.54.44.18)  229.105 ms
    te0-3-0-5.ccr21.bos01.atlas.cogentco.com (154.54.44.34)  229.117 ms
13  te0-3-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.230)  241.017 ms
    te0-2-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.190)  227.103 ms
    te0-1-0-1.ccr21.lpl01.atlas.cogentco.com (154.54.31.182)  224.973 ms
14  te3-2.ccr01.man01.atlas.cogentco.com (130.117.51.253)  236.195 ms  232.509 ms  239.429 ms
15  te1-1.ccr01.dub01.atlas.cogentco.com (130.117.3.213)  229.303 ms  228.688 ms  234.848 ms
16  149.6.4.166 (149.6.4.166)  223.717 ms  228.552 ms  234.914 ms

Yeah everything was fine up until last November .

jumbobreakfast

A re-occurrence perhaps?: http://www.boards.ie/vbulletin/showthread.php?t=2056214062

Enigma IE

jumbobreakfast wrote: »

A re-occurrence perhaps?: http://www.boards.ie/vbulletin/showthread.php?t=2056214062

The UPC & MunsterBB peering issue was never solved and won't be anytime soon unfortunately.