Upc users

Shammy

Lads any of ye that have upc can ye do me a favour ?

go to www.speedtest.net and do a speedtest to the limerick server and post your results , please.

Thanks

meemeep

hope those links work - download 2.91, upload 0.45, ping 323

Compare against Dublin

down: 4.91, up 0.48 and ping 34

Spear

Shammy wrote: »

Lads any of ye that have upc can ye do me a favour ?

go to www.speedtest.net and do a speedtest to the limerick server and post your results , please.

Thanks

Hmm,

Limerick:

2.24 down
2.71 up

Dublin:

29.48 down,
2.89 up

I seem to recall mention before that the Limerick node was always a bit screwed up.

Shammy

Spear wrote: »

Hmm,

Limerick:

2.24 down
2.71 up

Dublin:

29.48 down,
2.89 up

I seem to recall mention before that the Limerick node was always a bit screwed up.

The problem is i am with a different provider and find it near impossible to play online with upc users, i thought it was my connection until a mate told me he did this . I did a tracert on it and it seem before upc can hit limerick it stops off in the States :eek:

edit: only had a problem connecting with upc customers since last thursday , so now i'm wondering if its the same for anyone else in limerick that isnt with upc.

jeckle

Spear

Shammy wrote: »

The problem is i am with a different provider and find it near impossible to play online with upc users, i thought it was my connection until a mate told me he did this . I did a tracert on it and it seem before upc can hit limerick it stops off in the States :eek:

That sounds very weird and very unlikely, can I see the tracert results?

Shammy

Spear wrote: »

That sounds very weird and very unlikely, can I see the tracert results?

Not really when you look at the ping times.
I'll pm you the results.

Croc

DemoniK

don't assume it's a UPC issue
the speedtest.net server in limerick is run by a 3rd party if I remember and it can be an issue with them.

I never use the Limerick server for testing - even for other providers.
(currently seeing over 300ms ping)

Have no issue with connecting with other UPC or non-UPC in Limerick or other parts of the country

EDIT
Found the links I was looking for - first up here from boards http://www.boards.ie/vbulletin/showthread.php?t=2055687896
And if you click on the server for Limerick it's now Arra comms http://www.arra.ie/index.php/about-us.html

thefinalstage

The limerick servers are messed up on speedtest.net

DemoniK

update for others
Shammy and I tracert to each other and there is indeed a routing issue between his provider and UPC

here's the results (removed our public IPs)

======================
From DemoniK (UPC) to Shammy
======================

Tracing route to Shammy over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  READYSHARE [192.168.1.1] 
  2    23 ms    12 ms    11 ms  DemoniK 
  3    13 ms    12 ms    20 ms  188.141.126.81 
  4    19 ms    50 ms    17 ms  089-101-175110.ntlworld.ie [89.101.175.110] 
  5   110 ms   110 ms   119 ms  fr-par02a-rd2-gi-13-0-0.aorta.net [213.46.160.97] 
  6   119 ms   109 ms   109 ms  84-116-130-30.aorta.net [84.116.130.30] 
  7   110 ms   111 ms   110 ms  us-nyc01b-ri1-ge-0-1-0.aorta.net [213.46.190.178] 
  8   178 ms   179 ms   179 ms  xe-8-3-0.edge1.NewYork1.Level3.net [4.78.164.221] 
  9     *        *        *     Request timed out.
 10   216 ms   217 ms   217 ms  te0-1-0-4.mpd21.jfk02.atlas.cogentco.com [154.54.31.1] 
 11   291 ms   286 ms   292 ms  te0-2-0-1.ccr21.lpl01.atlas.cogentco.com [154.54.31.190] 
 12   295 ms   287 ms   287 ms  te3-2.ccr01.man01.atlas.cogentco.com [130.117.51.253] 
 13     *        *      296 ms  te1-1.ccr01.dub01.atlas.cogentco.com [130.117.3.213] 
 14   299 ms   294 ms   294 ms  149.6.4.242 
 15   322 ms   312 ms   297 ms  79.140.208.42 
 16     *        *        *     Request timed out.
 17   300 ms   300 ms   303 ms  Shammy 

Trace complete.

======================
From Shammy to DemoniK	
======================

Tracing route to DemoniK over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.254
2 3 ms 1 ms 1 ms Shammy
3 2 ms 5 ms 1 ms 10.200.2.33
4 4 ms 4 ms 4 ms 10.200.2.5
5 16 ms 9 ms 9 ms 79.140.208.1
6 10 ms 10 ms 12 ms te2-3.250.ccr01.dub01.atlas.cogentco.com [149.6.4.241]
7 13 ms 13 ms 16 ms te1-4.ccr01.man01.atlas.cogentco.com [130.117.3.214]
8 15 ms 17 ms 17 ms te0-1-0-4.ccr21.lpl01.atlas.cogentco.com [130.117.51.254]
9 84 ms 90 ms 89 ms te0-3-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.6.141]
10 110 ms 114 ms 112 ms te0-2-0-6.mpd22.ord01.atlas.cogentco.com [66.28.4.57]
11 122 ms 128 ms 116 ms te0-2-0-3.mpd22.mci01.atlas.cogentco.com [154.54.6.253]
12 126 ms 127 ms 126 ms te4-7.mpd01.dfw01.atlas.cogentco.com [154.54.25.205]
13 129 ms 130 ms 132 ms te2-1.mpd01.dfw03.atlas.cogentco.com [154.54.7.46]
14 131 ms 128 ms 128 ms te-3-2.car3.dallas1.level3.net [4.68.110.109]
15 133 ms 140 ms 127 ms ae-92-90.ebr2.dallas1.level3.net [4.69.145.243]
16 130 ms 134 ms 130 ms ae-3-3.ebr2.newyork1.level3.net [4.69.137.122]
17 133 ms 125 ms 124 ms ae-72-72.csw2.newyork1.level3.net [4.69.148.38]
18 128 ms 129 ms 127 ms ae-2-79.edge1.newyork1.level3.net [4.68.16.78]
19 207 ms 219 ms 210 ms upc-broadba.edge1.newyork1.level3.net [4.78.164.222]
20 311 ms 309 ms 307 ms us-nyc01c-rd1-gi-13-0-0.aorta.net [213.46.190.181]
21 293 ms 303 ms 302 ms uk-lon02a-rd1-pos-12-0.aorta.net [213.46.160.125]
22 278 ms 282 ms 288 ms 84.116.132.241
23 301 ms 303 ms 303 ms 84-116-130-242.aorta.net [84.116.130.242]
24 293 ms 318 ms 293 ms 089-101-175109.ntlworld.ie [89.101.175.109]
25 309 ms 305 ms 309 ms 188.141.126.85
26 324 ms 324 ms 322 ms DemoniK

Trace complete.

I've opened a support request with UPC.
Clearly some Database somewhere is missing something....

Enigma IE

Must be a dodgy router (bad route) in Limerick vicinty. Packets going to the US then back to Limerick.

Pataman

Limerick:


Dublin:

Shammy

thelastangryman wrote: »

The limerick servers are messed up on speedtest.net

Heres mine (not with upc btw)

teddy b123

some of you bight find this a bit interesting https://www.inex.ie/technical/peeringmatrix

bryaner

Holy fcuk..

The ping is the big one..

bryaner

game4it70

bkehoe

Noticed the issue between UPC and Cogentco ourselves too. I think they should normally peer with each other at LINX in London but for the last week or so this has been happening in New York. Result is 250ms pings to Cogentco customers in Ireland and poor unreliable bandwidth. Anyone know how to report this to someone to get it fixed - I can't imagine trying to explain this to the average telephone support chap at UPC :rolleyes:

DemoniK

email them - or do something at least.
The more of us that do, the better the chance of getting it resolved. If we all sit back and do nothing it will stay like this

Kells...

vibe666

DemoniK wrote: »

email them - or do something at least.
The more of us that do, the better the chance of getting it resolved. If we all sit back and do nothing it will stay like this

ditto. you need to keep emailing support@upc.ie (or calling them if you can cope with that).

report the problem and then keep emailing every couple of days for status updates.

a lot of the problem solving is a reactive process, so they need people to log calls to know who is affected and how badly.

Simply Red

Enigma IE

I've logged a call with UPC also, lets see if they come back with anything.

Enigma IE wrote: »

Must be a dodgy router (bad route) in Limerick vicinty. Packets going to the US then back to Limerick.

Enigma IE

Enigma IE wrote: »

I've logged a call with UPC also, lets see if they come back with anything.

I got a response from customer support saying the issue is with Xbox,PS they dont support 3rd party equipment!! Clowns. I expected as much to be honest.

I sent them result of the speedtest, just to highlight the unacceptable latency and round drop times. I doubt they will be doing anything about it.

Enigma IE

Enigma IE wrote: »

I got a response from customer support saying the issue is with Xbox,PS they dont support 3rd party equipment!! Clowns. I expected as much to be honest.

I sent them result of the speedtest, just to highlight the unacceptable latency and round drop times. I doubt they will be doing anything about it.

I just got a call from UPC regarding the issue. The guy was decent enough actually, he sounded like a gamer. He said UPC packets have always gone to NYC and back (its their least cost route), but said the latency should only be about 60 ms, not 300+ms which is what most of us are getting. They are aware of the issue alright, but he didn't give the impression of any quick fix.

DemoniK

Enigma IE wrote: »

I just got a call from UPC regarding the issue. The guy was decent enough actually, he sounded like a gamer. He said UPC packets have always gone to NYC and back (its their least cost route), but said the latency should only be about 60 ms, not 300+ms which is what most of us are getting. They are aware of the issue alright, but he didn't give the impression of any quick fix.

got the same call...
I think 200ms to NY is pretty reasonable from previous providers - the problem is more the why meet there when cogent has servers in EU!
He's passed it on inwards - will see

We just have to keep raising tickets

Shammy

DemoniK wrote: »

got the same call...
I think 200ms to NY is pretty reasonable from previous providers - the problem is more the why meet there when cogent has servers in EU!
He's passed it on inwards - will see

We just have to keep raising tickets

I have my provider sending an e-mail to cogent , i'll let ye know there response when i do.

Enigma IE

DemoniK wrote: »

got the same call...
I think 200ms to NY is pretty reasonable from previous providers - the problem is more the why meet there when cogent has servers in EU!
He's passed it on inwards - will see

We just have to keep raising tickets

He mentioned they have an alternate route to Switzerland, but typically the NYC route was faster. He did say the round trip time is usually 60ms, so not reason why they can't sort it out. It's probably an overworked edge router somewhere that needs upgrading or replacing.

DemoniK

just got another phone call
Apparently quite a few people have reported the same problem
well done lads...

They asked me for a few IP Addresses to test with - and I provided.

He said they're not too far from resolving it...
Fingers crossed.

Enigma IE

DemoniK wrote: »

just got another phone call
Apparently quite a few people have reported the same problem
well done lads...

They asked me for a few IP Addresses to test with - and I provided.

He said they're not too far from resolving it...
Fingers crossed.

I just got same call, 2nd call... looking for my tracert results to Shammy.

Enigma IE

Enigma IE wrote: »

I just got same call, 2nd call... looking for my tracert results to Shammy.

Just spoke to one of their techies on second level. He recognised it is most likely a routing issue on their side. Packets sent from Dublin to Limerick should NOT be going transatlantic, it should be traversing national network only.

I told him I was testing with Munster broadband user and he is doing to do some testing himself, I have him sample IP address. He also mentioned he's a COD player so he understands the craic. He is going to give me a call back tomorrow.

Shammy

DemoniK wrote: »

just got another phone call
Apparently quite a few people have reported the same problem
well done lads...


.

I've a lot of friends on the 360/ps3 with upc that want to kick my ass again .

Just like to say thanks to everyone who complained and hopefully it will be resolved shortly.

MiniNukinfuts

Hey, I just stumbled upon this topic while searching a solution to my tracert problem with UPC. Have UPC got back to anyone about the problem yet?

I've tried a tracert to my friend in Kerry, I'm in cork. And the route that my connection goes is: cork (me) -> Dublin -> Netherlands -> Austria -> new york - > Washington DC -> Kansas -> Kerry(my friend)

the full results are here: [PHP]traceroute to 88.151.27.238 (88.151.27.238), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 10.316 ms 0.710 ms 0.616 ms
2 * * *
3 188.141.126.145 (188.141.126.145) 21.511 ms 22.011 ms 26.197 ms
4 089-101-174126.ntlworld.ie (89.101.174.126) 15.135 ms 15.998 ms 47.756 ms
5 84.116.134.134 (84.116.134.134) 104.656 ms 97.669 ms 96.120 ms
6 84.116.132.230 (84.116.132.230) 128.315 ms
84.116.132.226 (84.116.132.226) 126.433 ms
84.116.132.230 (84.116.132.230) 135.357 ms
7 us-nyc01b-rd1-pos-12-0.aorta.net (213.46.160.242) 98.201 ms 95.168 ms 96.199 ms
8 us-nyc01b-ri1-ge-0-1-0.aorta.net (213.46.190.178) 95.340 ms 94.807 ms 98.022 ms
9 xe-4-1-0.edge1.newyork1.level3.net (4.78.132.93) 95.746 ms 97.169 ms
xe-8-3-0.edge1.newyork1.level3.net (4.78.164.221) 98.344 ms
10 * * *
11 te0-1-0-4.mpd22.jfk02.atlas.cogentco.com (154.54.31.5) 134.266 ms
te0-0-0-4.mpd21.jfk02.atlas.cogentco.com (154.54.7.13) 134.482 ms
te0-3-0-5.mpd21.jfk02.atlas.cogentco.com (154.54.26.61) 135.968 ms
12 te0-1-0-1.ccr22.lpl01.atlas.cogentco.com (154.54.42.106) 209.348 ms 210.428 ms
te0-0-0-1.ccr22.lpl01.atlas.cogentco.com (154.54.42.102) 207.433 ms
13 te3-2.ccr01.man01.atlas.cogentco.com (130.117.51.253) 231.401 ms
te4-2.ccr01.man01.atlas.cogentco.com (154.54.36.58) 264.000 ms
te3-2.ccr01.man01.atlas.cogentco.com (130.117.51.253) 211.233 ms
14 te1-1.ccr01.dub01.atlas.cogentco.com (130.117.3.213) 217.561 ms 229.655 ms 214.528 ms
15 88.151.27.238 (88.151.27.238) 214.678 ms 217.479 ms 216.154 ms [/PHP]

Thanks, Mark

Smyth

Hi guys. Could this be the reason I'm experiencing problems with my connection too? (Dublin 8)

I've logged the issue multiple times and got it escalated so that they'll send out a technician.

Quick tracert to boards:

1 27 ms 14 ms 10 ms 89.101.208.1
2 9 ms * 15 ms 188.141.126.1
3 * * 13 ms 89.101.174.62
4 11 ms 11 ms 12 ms 84.116.238.34
5 * 28 ms 12 ms 193.242.111.2
6 56 ms 32 ms 14 ms 89.234.66.107

And a ping test to boards again

Request timed out.
Reply from 89.234.66.107: bytes=32 time=13ms TTL=60
Reply from 89.234.66.107: bytes=32 time=11ms TTL=60
Reply from 89.234.66.107: bytes=32 time=10ms TTL=60
Reply from 89.234.66.107: bytes=32 time=18ms TTL=60
Request timed out.
Request timed out.
Request timed out.
Reply from 89.234.66.107: bytes=32 time=30ms TTL=60
Request timed out.

Enigma IE

Smyth wrote: »

Hi guys. Could this be the reason I'm experiencing problems with my connection too? (Dublin 8)

I've logged the issue multiple times and got it escalated so that they'll send out a technician.

Quick tracert to boards:




And a ping test to boards again

Most definitely. The tracert results are normal, not all routers will respond (by design), that would be represented by the asterisks. The fact you are dropping packets trying to ping boards.ie, certainly suggests an issue with your kit or provider.

TheMastero

1st i gotta say speedtest is never accurate, well its never been for me anyway
but here are my results.

This is from Limerick to the Dublin server:


Limerick to Limerick server: lol


Heh i never take any notice of these test sites there a loda crap but thats my opinion....

My 30mb UPC bb i working fine

Shammy

TheMastero wrote: »

1st i gotta say speedtest is never accurate, well its never been for me anyway
but here are my results.

This is from Limerick to the Dublin server:


Limerick to Limerick server: lol


Heh i never take any notice of these test sites there a loda crap but thats my opinion....

My 30mb UPC bb i working fine

Depends on who you are connected to , if to me , then it is 731 ms(maybe not that high) as its taking you to the states before it reaches me.

Limerick to limerick 100 miles....limerick to dublin 50 miles ???

edit : Brian, have you gotten word on when its going to be fixed , i'm getting nothing back off my crowd.

Enigma IE

Shammy wrote: »

Depends on who you are connected to , if to me , then it is 731 ms(maybe not that high) as its taking you to the states before it reaches me.

Limerick to limerick 100 miles....limerick to dublin 50 miles ???

edit : Brian, have you gotten word on when its going to be fixed , i'm getting nothing back off my crowd.

Local peering needs to be configured in Limerick by both providers. Basically, Munster BB need a UPC circuit themselves and then route local traffic over that circuit. UPC contacted Munster BB as far as I know, they (Munster BB) said it would be sorted in 7-10 days. That was late last week.

sierra117x

Enigma IE wrote: »

Local peering needs to be configured in Limerick by both providers. Basically, Munster BB need a UPC circuit themselves and then route local traffic over that circuit. UPC contacted Munster BB as far as I know, they (Munster BB) said it would be sorted in 7-10 days. That was late last week.

you got so much further with them then i did oh well least its getting sorted i hate the days when shammy hosts cant wait to kick some limerick tail again

interpoint

Enigma IE wrote: »

Local peering needs to be configured in Limerick by both providers. Basically, Munster BB need a UPC circuit themselves and then route local traffic over that circuit. UPC contacted Munster BB as far as I know, they (Munster BB) said it would be sorted in 7-10 days. That was late last week.

This is correct. We are looking into the BGP peering arrangements that we have with UPC via INEX. We are also upgrading our backhaul out of Limerick to a 1Gb-1 circuit.

UPC are slow to complete the peering with us in INEX but we are trying. These things take time. I will post when we have this completed.

The end result will be Munster Broadband customers and UPC customers will be routed within Ireland and not via the USA.

Thanks

Munster Broadband
Support

Enigma IE

interpoint wrote: »

This is correct. We are looking into the BGP peering arrangements that we have with UPC via INEX. We are also upgrading our backhaul out of Limerick to a 1Gb-1 circuit.

UPC are slow to complete the peering with us in INEX but we are trying. These things take time. I will post when we have this completed.

The end result will be Munster Broadband customers and UPC customers will be routed within Ireland and not via the USA.

Thanks

Munster Broadband
Support

Hi, so can you tell us is the current issue a link saturation issue rather than a routing issue?

interpoint

Enigma IE wrote: »

Hi, so can you tell us is the current issue a link saturation issue rather than a routing issue?

The issue is certainly routing between Munster Broadband and UPC.

Tracing route to 188.141.126.85 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Private
2 2 ms 2 ms 1 ms Private
3 9 ms 15 ms 8 ms Private
4 55 ms 19 ms 13 ms 79.140.208.1
5 43 ms * 28 ms te2-3.250.ccr01.dub01.atlas.cogentco.com [149.6.4.241]
6 39 ms 23 ms 33 ms te1-4.ccr01.man01.atlas.cogentco.com [130.117.3.214]
7 18 ms 20 ms 23 ms te0-1-0-4.ccr21.lpl01.atlas.cogentco.com [130.117.51.254]
8 92 ms 110 ms 99 ms te0-2-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.0.70]
9 135 ms 159 ms 129 ms te0-0-0-6.mpd22.ord01.atlas.cogentco.com [154.54.28.9]
10 151 ms 150 ms 133 ms te0-2-0-3.mpd22.mci01.atlas.cogentco.com [154.54.6.253]
11 140 ms 130 ms 132 ms te3-3.mpd01.dfw01.atlas.cogentco.com [154.54.5.157]
12 144 ms 136 ms 136 ms te3-3.mpd01.dfw03.atlas.cogentco.com [154.54.6.94]
13 279 ms 237 ms 213 ms te-3-2.car3.dallas1.level3.net [4.68.110.109]
14 180 ms 140 ms 153 ms ae-92-90.ebr2.dallas1.level3.net [4.69.145.243]
15 146 ms 127 ms 132 ms ae-3-3.ebr2.newyork1.level3.net [4.69.137.122]
16 140 ms 128 ms 132 ms ae-82-82.csw3.newyork1.level3.net [4.69.148.42]
17 138 ms 146 ms 131 ms ae-3-89.edge1.newyork1.level3.net [4.68.16.142]
18 145 ms 133 ms 133 ms upc-broadba.edge1.newyork1.level3.net [4.78.164.222]
19 226 ms 233 ms 220 ms us-nyc01c-rd1-gi-0-0-0.aorta.net [213.46.190.97]
20 220 ms 226 ms 228 ms uk-lon02a-rd1-pos-12-0.aorta.net [213.46.160.125]
21 224 ms 229 ms 208 ms 84.116.132.245
22 256 ms 231 ms 233 ms 84.116.134.129
23 238 ms 230 ms 226 ms 089-101-175109.ntlworld.ie [89.101.175.109]
24 239 ms 259 ms 221 ms 188.141.126.85
Trace complete.

The issue will be resolved once the INEX peering has been completed.
Hops will be shortened dramatically and latency will be dramtically different.

Enigma IE

Cheers for the update. I fully understand that local peering will result in less hops and lower latency, hopefully solving the issue. The reason why I ask about saturation is because we were able to play online (UPC & MunsterBB) customers with no issues prior to about 5 or 6 weeks ago.

interpoint wrote: »

The issue is certainly routing between Munster Broadband and UPC.

Tracing route to 188.141.126.85 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms Private
2 2 ms 2 ms 1 ms Private
3 9 ms 15 ms 8 ms Private
4 55 ms 19 ms 13 ms 79.140.208.1
5 43 ms * 28 ms te2-3.250.ccr01.dub01.atlas.cogentco.com [149.6.4.241]
6 39 ms 23 ms 33 ms te1-4.ccr01.man01.atlas.cogentco.com [130.117.3.214]
7 18 ms 20 ms 23 ms te0-1-0-4.ccr21.lpl01.atlas.cogentco.com [130.117.51.254]
8 92 ms 110 ms 99 ms te0-2-0-4.ccr21.ymq02.atlas.cogentco.com [154.54.0.70]
9 135 ms 159 ms 129 ms te0-0-0-6.mpd22.ord01.atlas.cogentco.com [154.54.28.9]
10 151 ms 150 ms 133 ms te0-2-0-3.mpd22.mci01.atlas.cogentco.com [154.54.6.253]
11 140 ms 130 ms 132 ms te3-3.mpd01.dfw01.atlas.cogentco.com [154.54.5.157]
12 144 ms 136 ms 136 ms te3-3.mpd01.dfw03.atlas.cogentco.com [154.54.6.94]
13 279 ms 237 ms 213 ms te-3-2.car3.dallas1.level3.net [4.68.110.109]
14 180 ms 140 ms 153 ms ae-92-90.ebr2.dallas1.level3.net [4.69.145.243]
15 146 ms 127 ms 132 ms ae-3-3.ebr2.newyork1.level3.net [4.69.137.122]
16 140 ms 128 ms 132 ms ae-82-82.csw3.newyork1.level3.net [4.69.148.42]
17 138 ms 146 ms 131 ms ae-3-89.edge1.newyork1.level3.net [4.68.16.142]
18 145 ms 133 ms 133 ms upc-broadba.edge1.newyork1.level3.net [4.78.164.222]
19 226 ms 233 ms 220 ms us-nyc01c-rd1-gi-0-0-0.aorta.net [213.46.190.97]
20 220 ms 226 ms 228 ms uk-lon02a-rd1-pos-12-0.aorta.net [213.46.160.125]
21 224 ms 229 ms 208 ms 84.116.132.245
22 256 ms 231 ms 233 ms 84.116.134.129
23 238 ms 230 ms 226 ms 089-101-175109.ntlworld.ie [89.101.175.109]
24 239 ms 259 ms 221 ms 188.141.126.85
Trace complete.

The issue will be resolved once the INEX peering has been completed.
Hops will be shortened dramatically and latency will be dramtically different.

interpoint

Enigma IE wrote: »

Cheers for the update. I fully understand that local peering will result in less hops and less latency, hopefully solving the issue. The reason why I ask about saturation is because we were able to play online (UPC & MunsterBB) customers with no issues prior to about 5 or 6 weeks ago.

If you are a MBB client then PM me your Client ID. If you are a UPC client then PM me your Public IP and I will investigate further.

Once INEX is complete we can complete the tracert again and compare the hops.

The best way to communicate with Munster broadband is via support [at] munsterbroadband [dot] ie

We will always try and make things better for MBB customers as you can understand I cannot do anything to sort out issues UPC clients maybe experiancing once the data leaves the MBB network.

All we can do is reduce the hops.

Enigma IE

PM'd, thanks.

interpoint wrote: »

If you are a MBB client then PM me your Client ID. If you are a UPC client then PM me your Public IP and I will investigate further.

Once INEX is complete we can complete the tracert again and compare the hops.

The best way to communicate with Munster broadband is via support [at] munsterbroadband [dot] ie

We will always try and make things better for MBB customers as you can understand I cannot do anything to sort out issues UPC clients maybe experiancing once the data leaves the MBB network.

All we can do is reduce the hops.

interpoint

Enigma IE wrote: »

PM'd, thanks.

Got it.. Thanks

If you are speaking to your friend that is with MBB. Please ask him to PM me his IP or MBB Client ID and I will check to see what MBB access point he is connected to and check the internal latency for this user on the MBB network.

I would expect the UPC peering to be sorted in the next few days. However, sometimes around this time of year there can be config freezes where system managers do not want to make any new changes as they have reduced support capability and don't want to break anything.

I will raise the issue again in the morning and lets see how things progress..

ro2

UPC have a restrictive peering policy that is controlled by their NOC in Holland. Anyone having issues like the one with Munster Broadband should email UPC and ask them why they don't peer with the route servers on INEX.

If they peered with the route servers, most of their red boxes here would change to green. This would speed up access to the websites hosted by the providers they don't peer with for all UPC customers.

https://www.inex.ie/technical/peeringmatrix

Shammy

Pm sent

Shammy

interpoint wrote: »

The best way to communicate with Munster broadband is via support [at] munsterbroadband [dot] ie

We will always try and make things better for MBB customers as you can understand I cannot do anything to sort out issues UPC clients maybe experiancing once the data leaves the MBB network.

All we can do is reduce the hops.

Its been over a week since i pmed you and still no response , not to mention the phonecalls to mbb with no answers to my questions , i have left messages for a certain person to give me a call back on numourous occasions (the person supposeably dealing with this) and yet i have had no feedback.

interpoint

Shammy wrote: »

Its been over a week since i pmed you and still no response , not to mention the phonecalls to mbb with no answers to my questions , i have left messages for a certain person to give me a call back on numourous occasions (the person supposeably dealing with this) and yet i have had no feedback.

Shammy, I got your PM. I have not had any response from UPC. Peering arrangements are on hold over Christmas as network freezes are in place at the moment. Our office is also closed at the moment too.

This process can take several weeks to complete at worse case. We are willing to implement our end within 24 hours of a contact in UPC organising their end of the peering.