Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

NGB adsl2+ peak and non peak comparison, am I missing something?

  • 02-02-2015 9:10pm
    #1
    Closed Accounts Posts: 11,631 ✭✭✭✭


    Hey all, figured this was a good place to post this.

    Recently I changed from Eircom NGB to Vodafone. I had the exact same problems on Eircom as I do now on Vodafone. The exchange is right outside my house so I'm synced at the full 24MB profile, with fastpath enabled

    Could anyone offer any insight as to whats going on? This happens every night and is worse on weekends. Below is a list of screen grabs showing the problems

    To Irish servers it's perfectly stable 24/7

    vo0vud.png

    Below are examples of how unstable the connection is to multiple servers

    UK non peak time

    160vqki.png

    UK peak time

    iwrpfp.png

    GER non peak

    2uhbnnq.png

    GER peak

    4hr4h5.png

    FRA non peak

    21njw5e.png

    FRA peak

    wklsfp.png

    NL non peak

    ax1udz.png

    NL peak

    2ia6esh.png

    I could list off another 20 servers. All this results in is a very unstable connection. In game lag is horrendous and unplayable for the most part. Its completely unpredictable aswell, one second it might be 40ms, and the next its over 100ms.

    What bothers me the most is this doesn't seem to be happening to users on Fiber, just NGB and non NGB users. I'm open to correction on this.

    As you can imagine it's highly frustrating as a gamer, I switched in the hop a new ISP would solve the problems, but it's just as bad as Eircom.

    Anyone have any idea?


Comments

  • Registered Users, Registered Users 2 Posts: 36,170 ✭✭✭✭ED E


    Its congested T1 links.

    Only residential ISP in Ireland with sufficient peak transit at the moment seems to be UPC. And even they still have some additional delay at peak (packet loss seems to be around 5%).

    Location:
    EU1 - Bavaria, Germany (login.p1.worldoftanks.eu) (92.223.1.92, 92.223.1.102, 92.223.1.112, 92.223.1.122)
    EU2 - Amsterdam, Netherlands (login.p2.worldoftanks.eu) (185.12.240.100, 185.12.240.110, 185.12.240.140, 185.12.240.150)

    Thats what Im usually hitting off.

    "Arctic Fibre" when its finished in a few years will add a heap of transit to the national pool, in the meantime L3, Cogent, C&W etc will need to do some upgrades. Im sceptical its not just the ISPs not paying up like could cause it as Vodafone own a chunk of the available bandwidth.


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    This never happens to any other ISP's in other countries, its very frustrating. In a community of thousands such as quake its always only me with such these routing problems at peak hours. From 2005 up to early 2012 or so there was never any of these problems, since eFiber starting roll out the problems began.

    The weird thing is any server in Frankfurt my latency is perfectly stable, everywhere else it's borked.


  • Registered Users, Registered Users 2 Posts: 36,170 ✭✭✭✭ED E


    The weird thing is any server in Frankfurt my latency is perfectly stable, everywhere else it's borked.

    Thats the nature or large scale WAN routing. If the destination IP is in X range it goes left and hits a congested link, Y it goes right and flies off to its destination.


    UK Peak above:
    http://ns.myip.ms/view/ip_addresses/3271693824/195.2.22.0_195.2.22.255
    Vodafones link

    Ger Peak Above:
    http://myip.ms/view/ip_addresses/3271694592/195.2.25.0_195.2.25.255
    Main bump is Vodafone again
    http://myip.ms/info/whois/77.109.140.30
    With additional slowdown as it traverses the continent.

    Rest are the same, CW's onward connections to europe hammering you. Which may indicate its UK-Mainland Europe thats problematic too.


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Thanks for the info, it just seems completely unfair. My only option is to move to a town and get UPC


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    Would appreciate if people would paste similar traces the above servers during peak hours just to see if its happening on vdsl and other ngb connections aswell, thanks all


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 7,903 ✭✭✭frozenfrozen


    Target Name: www.akamai.com
    IP: 23.200.101.190
    Date/Time: 2/3/2015 8:29:47 PM

    1 0 ms VODAFONE [10.13.37.254]
    2 27 ms [89.19.65.3]
    3 28 ms [89.19.65.65]
    4 28 ms [89.19.69.65]
    5 29 ms [89.19.69.150]
    6 29 ms a23-200-101-190.deploy.static.akamaitechnologies.com [23.200.101.190]

    Ping statistics for www.akamai.com
    Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
    Round Trip Times: Minimum = 29ms, Maximum = 29ms, Average = 29ms


    Target Name: www.twitter.com
    IP: 199.59.148.82
    Date/Time: 2/3/2015 8:30:02 PM

    1 0 ms VODAFONE [10.13.37.254]
    2 28 ms [89.19.65.3]
    3 28 ms [89.19.65.65]
    4 29 ms [89.19.69.65]
    5 28 ms [195.2.7.125]
    6 85 ms [195.2.21.1]
    7 43 ms ae24-xcr1.lns.cw.net [195.2.25.145]
    8 76 ms ae6-xcr1.lnt.cw.net [195.2.30.62]
    9 79 ms xe-1-1-0.cr1-lon1.twttr.com [195.66.225.142]
    10 55 ms ae61.lon2-cr2.twttr.com [199.16.159.143]
    11 127 ms [192.133.76.42]
    12 291 ms ae63.chi1-cr1.twttr.com [192.133.76.6]
    13 282 ms [199.16.159.31]
    14 182 ms ae52.smf1-er1.twttr.com [199.16.159.49]
    15 289 ms r-199-59-148-82.twttr.com [199.59.148.82]

    Ping statistics for www.twitter.com
    Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
    Round Trip Times: Minimum = 289ms, Maximum = 289ms, Average = 289ms

    Not really sure what ips I should be pinging to show it but I've been getting the exact same problems as you, perfect pings to Irish servers, OK to outside during the day and then in the evenings it's just awful to anything outside of Ireland.

    No packet loss either or jitter, just solid 150+ ping to UK or 200 to Germany in some cases.

    If you tell me what to ping I'll post more results here. From reading the above it looks like it's not likely to be fixed soon?


  • Closed Accounts Posts: 11,631 ✭✭✭✭Hank Scorpio


    No idea, I only changed to vodafone a few weeks ago

    Multiplay.co.uk had 240ms latency this time yesterday

    Tonight it seems fine

    Pinging multiplay.co.uk [85.236.96.26] with 32 bytes of data:
    Reply from 85.236.96.26: bytes=32 time=26ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=26ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=27ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=24ms TTL=48

    Here's another UK server

    185.16.85.10


    ping 185.16.85.10

    Pinging 185.16.85.10 with 32 bytes of data:
    Reply from 185.16.85.10: bytes=32 time=183ms TTL=118
    Reply from 185.16.85.10: bytes=32 time=193ms TTL=118
    Reply from 185.16.85.10: bytes=32 time=182ms TTL=118
    Reply from 185.16.85.10: bytes=32 time=187ms TTL=118

    Ping statistics for 185.16.85.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 182ms, Maximum = 193ms, Average = 186ms



    Its totally unpredictable, tomorrow night it could be fine or 240 again

    Mine are fine during the day too

    Just as I say that multiplay is bouncing from 25-60 again. It's completely unstable, being a gamer you can understand how frustrating this is


  • Registered Users, Registered Users 2 Posts: 7,903 ✭✭✭frozenfrozen


    Pinging multiplay.co.uk [85.236.96.26] with 32 bytes of data:
    Reply from 85.236.96.26: bytes=32 time=106ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=100ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=104ms TTL=48
    Reply from 85.236.96.26: bytes=32 time=96ms TTL=48

    Ping statistics for 85.236.96.26:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 96ms, Maximum = 106ms, Average = 101ms


    Yeah had to give up playing for the rest of the night as it's not worth the frustration of spiking to 200ms ping in the middle of an esea pug.


Advertisement