High Ping but Line is Fine

damojag

About two months ago I noticed my online gaming begin to lag, prior to this I had a perfect gaming set-up with no lag and no dropped connections. I was using the silver Netopia router and found that the ping was hitting 1100ms and up. I figured it must be a router problem and replaced it with the black Zyxel but found ping to be going above 800ms.

After several calls to Eircom and replacing the router with a new one I have discovered the following:

My line is perfect
Nobody at Eircom has a clue why the ping is high
Nobody will offer any solutions that work
Eircom are perfectly fine with a 300ms ping even though it drastically affects online gaming, browsing and streaming
I've tried everything, all of Eircom's ping/latency tests, moving my connection from 5 to 6 to 7 to 8meg and all the way down again. Interleaving has been turned on and off. When the router is rebooted, the ping is fine for ten minutes and then it goes above 300ms.

I am completely out of ideas.

number66

Have you used traceroute to see how/where your packets are being routed?

http://www.mediacollege.com/internet/troubleshooter/traceroute.html

High ping times are very unlikely to be caused by your router.

damojag

Not entirely sure if this right, I went through Terminal on the Mac:

traceroute to eircom.net (86.43.38.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3309.112 ms 1.147 ms 0.745 ms
2 b-ras1.rtd.sligo.eircom.net (159.134.155.25) 293.559 ms 116.709 ms 104.185 ms
3 ge-3-1-5.pe1.rtd.rsl-rtd.eircom.net (86.43.247.5) 130.522 ms 192.488 ms 150.409 ms
4 tenge-7-1-1.core2.dbn.core.eircom.net (86.43.253.65) 158.173 ms 222.055 ms 202.577 ms
5 tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138) 237.360 ms 214.479 ms 332.674 ms
6 * ge1-5.service4.cra.dublin.eircom.net (159.134.125.46) 338.352 ms 449.469 ms

damojag

A few months ago I had a ping of 37ms almost constantly. With the silver Netopia I had a lovely stable ping of 1100ms and with the black Zyxel it was 850ms. My most recent Speedtests (a ping of 300ms is fine according to an Eircom engineer):




And this is a pingtest I conducted myself:

PING home.eircom.net (86.43.38.8): 56 data bytes
64 bytes from 86.43.38.8: icmp_seq=0 ttl=58 time=102.945 ms
64 bytes from 86.43.38.8: icmp_seq=1 ttl=58 time=123.362 ms
64 bytes from 86.43.38.8: icmp_seq=2 ttl=58 time=259.411 ms
64 bytes from 86.43.38.8: icmp_seq=3 ttl=58 time=307.239 ms
64 bytes from 86.43.38.8: icmp_seq=4 ttl=58 time=351.082 ms
64 bytes from 86.43.38.8: icmp_seq=5 ttl=58 time=144.140 ms
64 bytes from 86.43.38.8: icmp_seq=6 ttl=58 time=202.943 ms
64 bytes from 86.43.38.8: icmp_seq=7 ttl=58 time=130.186 ms
64 bytes from 86.43.38.8: icmp_seq=8 ttl=58 time=190.902 ms
64 bytes from 86.43.38.8: icmp_seq=9 ttl=58 time=229.168 ms
64 bytes from 86.43.38.8: icmp_seq=10 ttl=58 time=287.255 ms
64 bytes from 86.43.38.8: icmp_seq=11 ttl=58 time=356.597 ms
64 bytes from 86.43.38.8: icmp_seq=12 ttl=58 time=362.242 ms
64 bytes from 86.43.38.8: icmp_seq=13 ttl=58 time=152.969 ms
64 bytes from 86.43.38.8: icmp_seq=14 ttl=58 time=247.313 ms
64 bytes from 86.43.38.8: icmp_seq=15 ttl=58 time=316.329 ms
64 bytes from 86.43.38.8: icmp_seq=16 ttl=58 time=386.786 ms
Request timeout for icmp_seq 17
64 bytes from 86.43.38.8: icmp_seq=18 ttl=58 time=32.112 ms
64 bytes from 86.43.38.8: icmp_seq=19 ttl=58 time=191.757 ms
64 bytes from 86.43.38.8: icmp_seq=20 ttl=58 time=287.003 ms
64 bytes from 86.43.38.8: icmp_seq=21 ttl=58 time=393.985 ms
64 bytes from 86.43.38.8: icmp_seq=22 ttl=58 time=133.059 ms
64 bytes from 86.43.38.8: icmp_seq=23 ttl=58 time=235.337 ms
64 bytes from 86.43.38.8: icmp_seq=24 ttl=58 time=316.243 ms
64 bytes from 86.43.38.8: icmp_seq=25 ttl=58 time=370.366 ms
64 bytes from 86.43.38.8: icmp_seq=26 ttl=58 time=111.088 ms
64 bytes from 86.43.38.8: icmp_seq=27 ttl=58 time=58.785 ms
64 bytes from 86.43.38.8: icmp_seq=28 ttl=58 time=204.026 ms
Request timeout for icmp_seq 29
64 bytes from 86.43.38.8: icmp_seq=30 ttl=58 time=115.262 ms
Request timeout for icmp_seq 31
64 bytes from 86.43.38.8: icmp_seq=32 ttl=58 time=165.054 ms

number66

Realistically there is nothing you can do to improve your network latency. It's up to the network provider and you said it in your original post "Eircom are perfectly fine with a 300ms ping". Which I find ridiculously high and not worth considering for FPS online gaming. I won't log into a server with a ping higher that 75ms.

Since Eircom seem to have adopted a service level at 300ms I can only suggest you switch to a different provider, the only option being UPC if they are available in your area. I pinged that server you lists as being good a few months ago from my UPC connection in Waterford. you seem to be running 10 to 20 times slower than me, go Eircom, I'd give that obnoxious child in their TV ad a good smack, Un-Congested network my foot.

PING home.eircom.net (86.43.38.8) 56(84) bytes of data.
64 bytes from isp1.eircom.net (86.43.38.8): icmp_req=1 ttl=56 time=24.4 ms
64 bytes from isp1.eircom.net (86.43.38.8): icmp_req=2 ttl=56 time=11.6 ms
64 bytes from isp1.eircom.net (86.43.38.8): icmp_req=3 ttl=56 time=18.3 ms
64 bytes from isp1.eircom.net (86.43.38.8): icmp_req=4 ttl=56 time=14.2 ms
64 bytes from isp1.eircom.net (86.43.38.8): icmp_req=5 ttl=56 time=12.5 ms

damojag

Honestly, I know 300ms is criminal but they're rolling out fibre optic here before Christmas so I don't know if I should jump ship to UPC

number66

Well, the way you describe it as being ok for 10min and then going bad sounds like the network is badly configured. But fault finding a network is a dark art and doing it from the outside is next to impossible. I'd suggest look to see if anyone you know near you has UPC and try out their connection to see how well setup they are. My results really are meaningless as UPC could be terrible in your location.

In the end all that most companies really care about is money, But Eircom is probably more interested in government money than customers money so they care even less about their customers than most. You'll just have to decide what works best for you.

Solair

Ping times on some of the fixed-wireless networks can be excellent too.
It's all about good network design.

Eircom could be routing that traffic all over the place, especially if you're not on an NGN exchange that has relatively poor backhaul.

Baneblade

damojag wrote: »

When the router is rebooted, the ping is fine for ten minutes and then it goes above 300ms.

have you made sure you have nothing running on your network? the above sounds like having torrents running. connections are broken when you reboot it and slowly reconnect over the space of a few mins.

and you first mentioned pings off 800-1100ms. 9/10 times when pings are that high the cause is on the users network.

gerryk

When networks run close to capacity, the poorly designed buffering mechanism in routers creates bursty traffic, thus further aggravating the problem. The net result is what you are seeing... the network latency fluctuates wildly over certain periods.

There are two possible solutions... 1. increase the capacity of the network, and 2. remedy the broken buffering

Neither is a small undertaking, but the former, at least, could be undertaken by a network operator, the latter requires an industry-wide effort.

For more -> http://esr.ibiblio.org/?p=4171 & http://www.bufferbloat.net/

Not the definite cause of what you are seeing, but likely.

damojag

When I was getting 1100ms I was connected directly to the router via ethernet, wireless was turned off and only my computer was connected. There were no torrents or other downloading clients running.

Eircom have had me up on 8meg, 7, 6, and now they're trying 5 again - they don't have a clue what's going on and they've told me they have no idea why ping is that high.

Hank Scorpio

check how the pings are @ 3am or so, or at off peak times.

if your friendly with any people in your area check how the ping times are there too, might give you an indication of whether its a exchange problem or a problem with your personal network

damojag

Have you ever heard of Java causing problems? I use a Mac app called CrashPlan that backs up my computer to a remote server and I know that the app that runs in the menubar uses Java. I quit the app but I still noticed that Java was running in the background and using up about 200MB's of RAM. When it used under 100MB, my ping was fine but as soon as it went over 100MB my ping spiked.

There is no real way of uninstalling Java as many apps depends on it so I removed the CrashPlan app and now Java doesn't run in the background but more importantly my ping is stabilising at around 32ms.. I'll monitor it some more but could a program cause such problems?

number66

But you just have to look at the ping trace to see that the network is SLOW. every hop on that trace takes over 200ms, the hop to your router takes 0.75 ms. It's pretty obvious the network is shagged/overloaded. Is Netflix popular in your area?

anyway, I'm no network geek and gerryk seem to be more on the ball.

looking at it a bit more
1 192.168.1.1 (192.168.1.1) 3309.112 ms 1.147 ms 0.745 ms

would seem to point to a DNS issue to !!

itsnoton

number66 wrote: »

It's pretty obvious the network is shagged/overloaded.

On that basis - if eircom won't fix the problem, has the OP the right to walk away from any minimum contract period that eircom are enforcing? If not, can they escalate with a complaint to comreg?


(As an aside, it's interesting to consider that this is the eircom customer interaction forum - yet I see no input whatsoever from any eircom rep. in assisting their customer?)

Hank Scorpio

itsnoton wrote: »

On that basis - if eircom won't fix the problem, has the OP the right to walk away from any minimum contract period that eircom are enforcing? If not, can they escalate with a complaint to comreg?


(As an aside, it's interesting to consider that this is the eircom customer interaction forum - yet I see no input whatsoever from any eircom rep. in assisting their customer?)

Comreg can only get Eircom to check the problem, been down there route with my connection and didn't fix anything unfortunately

itsnoton

nuxxx wrote: »

Comreg can only get Eircom to check the problem, been down there route with my connection and didn't fix anything unfortunately

How about exiting the contract? Is the problem as described by the OP sufficient grounds for him to extract himself from a minimum contract period?

number66

damojag wrote: »

Have you ever heard of Java causing problems? I use a Mac app called CrashPlan that backs up my computer to a remote server and I know that the app that runs in the menubar uses Java. I quit the app but I still noticed that Java was running in the background and using up about 200MB's of RAM. When it used under 100MB, my ping was fine but as soon as it went over 100MB my ping spiked.

There is no real way of uninstalling Java as many apps depends on it so I removed the CrashPlan app and now Java doesn't run in the background but more importantly my ping is stabilising at around 32ms.. I'll monitor it some more but could a program cause such problems?

Wondering if you still having issues? a Java app running in the background could have been causing your problems. But I still cant see how it would slow down a traceroute , but it's very hard to be sure of anything with computers unless you really know the system your running.

So are you still having ping issues, or has the problems gone away. and if they have, was it the backup software or did someone at eircom fix the network?

damojag

Traceroute when everything is perfect:

traceroute to eircom.net (86.43.38.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.922 ms 3.720 ms 1.434 ms
2 b-ras1.rtd.sligo.eircom.net (159.134.155.25) 30.860 ms 27.741 ms 25.595 ms
3 ge-3-1-6.pe1.rtd.rsl-rtd.eircom.net (86.43.247.13) 29.625 ms 27.224 ms 23.902 ms
4 tenge-7-1-1.core2.dbn.core.eircom.net (86.43.253.65) 37.929 ms 30.446 ms 29.109 ms
5 tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138) 39.952 ms 30.794 ms 30.467 ms
6 ge1-5.service4.cra.dublin.eircom.net (159.134.125.46) 36.194 ms 29.320 ms 29.794 ms

This is with Java disabled but the simple fact is that I will need to use Java in the future - my ping will become terrible once I do

number66

I'd suggest you verify that it is actually Java that is the issue by enabling it again and seeing if the problem comes back, It's possible that removing Java had nothing to do with fixing you connection. It could be that an error had been fixed on the network around the same time you stopped java. I just can not see how a program on your computer would slow down packets traveling between two routers on Eircoms network.

Java as such should not interfere with you net connection. But Java 7 (think that some 6 versions have been affected too) is a big security risk and has recently been shown to have a large security hole that went unnoticed for quite a long time and is still not fixed.

http://www.h-online.com/security/features/The-new-Java-0day-examined-1677789.html

So if your computer is having network issues while Java is enabled I'd think your OS has been compromised. I'd also suggest http://www.wireshark.org/ as a good tool to see what data is moving from your computer.

Hope this helps, and glad to see you connection is working properly again.

damojag

Tested the exact same set-up at work - same app using Java and have noticed no ping issues, ironically I'm using Eircom at work - must be a problem with my line?

number66

I would think that some Eircom router had become mis-configured or some nefarious network traffic was bouncing around on that part of the network. Looks like it's been fixed whatever it was. It's not a problem with you line, the traffic was slow between Eircoms routers, they have nothing to do with your line.

from the traceroute you line is

1 192.168.1.1 (192.168.1.1) 3309.112 ms 1.147 ms 0.745 ms <-- the router in you sitting room

2 b-ras1.rtd.sligo.eircom.net (159.134.155.25) 293.559 ms 116.709 ms 104.185 ms <- eircoms router at your local exchange

from there on it is on Eircom lines.

3 ge-3-1-5.pe1.rtd.rsl-rtd.eircom.net (86.43.247.5) 130.522 ms 192.488 ms 150.409 ms
4 tenge-7-1-1.core2.dbn.core.eircom.net (86.43.253.65) 158.173 ms 222.055 ms 202.577 ms
5 tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138) 237.360 ms 214.479 ms 332.674 ms
6 * ge1-5.service4.cra.dublin.eircom.net (159.134.125.46) 338.352 ms 449.469 ms

you can see that it's slow on the eircom routers as well, nothing on you computer should be able to cause this. ( unless your computer has been hacked and is actively attacking the network ).

But good to see that Eircom don't actually think that 300ms is an ok ping time and got around to fixing it. Not so good that they did not flag a issue on the network and let the support staff know so they could just tell you that it's being worked on and will be fixed as soon as possible, rather that wasting time messing around with your local settings.

You should know a bit more if it happens again and save yourself a bit of time.

FruitLover

number66 wrote: »

1 192.168.1.1 (192.168.1.1) 3309.112 ms 1.147 ms 0.745 ms

would seem to point to a DNS issue to !!

This points to the answer alright, but it's not DNS. OP, if you're really getting 3309ms to your own router, then the problem is in your own home, nothing to do with Eircom.

I'm betting you're on Wi-Fi - next time you have latency issues, try connecting using a cable to see if the problem goes away. If so, the problem is probably local RF interference (maybe even neighbours' wireless networks). Try changing the Wi-Fi channel to see if this helps (if you have a smartphone, there are many free Wi-Fi analysis apps available, which can show you how many other Wi-Fi APs are on each channel).

itsnoton wrote: »

(As an aside, it's interesting to consider that this is the eircom customer interaction forum - yet I see no input whatsoever from any eircom rep. in assisting their customer?

Yeah, I wanted to comment on that too. Two business days pass by after a customer posts on the most popular online forum in the country, and not even a peep out of the official representatives on the topic? Shameful.

number66

FruitLover, true, If you are getting slow times pinging your router, but the OP was doing a traceroute which is a different animal. that traceroute showed that the problem was not local. the first packet was slow because a DNS lookup had to be preformed over a SLOW network before the packet could be sent. The subsequent packets could use the cashed IP address and did not preform a DNS lookup. was a red herring.

damojag

FruitLover wrote: »

This points to the answer alright, but it's not DNS. OP, if you're really getting 3309ms to your own router, then the problem is in your own home, nothing to do with Eircom.

I'm betting you're on Wi-Fi - next time you have latency issues, try connecting using a cable to see if the problem goes away. If so, the problem is probably local RF interference (maybe even neighbours' wireless networks). Try changing the Wi-Fi channel to see if this helps (if you have a smartphone, there are many free Wi-Fi analysis apps available, which can show you how many other Wi-Fi APs are on each channel).

Had the exact same ping times using ethernet only with wifi disabled. In fact I had pings of 300ms+ using FIVE different routers ethernet wired and wireless.

Silver Eircom Netopia: 1100ms+
Black Eircom Zyxel: 800ms+
Linksys Cisco WAG160N: 500ms+
D-Link 2740R: 300ms+
TP Link W8961ND: 300ms+

Where I am I do not pick up any of the neighbours networks and I use either channel 1 or 11.

FruitLover

number66 wrote: »

the first packet was slow because a DNS lookup had to be preformed over a SLOW network before the packet could be sent. The subsequent packets could use the cashed IP address and did not preform a DNS lookup. was a red herring.

The traceroute program runs the hostname lookup before any probes are sent, so the DNS resolution time is not included in the first packet's RTT.

OP, try leaving a continuous ping to your local gateway (192.168.1.1) running for a while to see if you get any latency spikes. This should confirm whether or not there's a local issue. The fact that you're getting such wildly varying ping times through different routers is another factor that's making me suspect a local problem (e.g. dodgy NIC or driver). Do you have any other devices you can test from other than your Mac?

damojag

Had it running for a good 30 mins last night whilst gaming online with the PS3. Pings were stabilising around 30ms with the odd spike of 50 or 70 and one occasion of 140ms due to loading a website.

Strangely I reinstalled the troublesome app and noticed no spike in ping times. Obviously I'm left scratching my head. Eircom have upped me to 7meg again to test out my ping so I'll have a go at that later on.

damojag

Line was upgraded to 7meg again today, here is a ping test:

PING home.eircom.net (86.43.38.8): 56 data bytes
64 bytes from 86.43.38.8: icmp_seq=0 ttl=58 time=30.233 ms
64 bytes from 86.43.38.8: icmp_seq=1 ttl=58 time=30.488 ms
64 bytes from 86.43.38.8: icmp_seq=2 ttl=58 time=33.068 ms
64 bytes from 86.43.38.8: icmp_seq=3 ttl=58 time=29.540 ms
64 bytes from 86.43.38.8: icmp_seq=4 ttl=58 time=40.246 ms
64 bytes from 86.43.38.8: icmp_seq=5 ttl=58 time=66.093 ms
64 bytes from 86.43.38.8: icmp_seq=6 ttl=58 time=44.319 ms
64 bytes from 86.43.38.8: icmp_seq=7 ttl=58 time=122.094 ms
64 bytes from 86.43.38.8: icmp_seq=8 ttl=58 time=103.672 ms
64 bytes from 86.43.38.8: icmp_seq=9 ttl=58 time=29.837 ms
64 bytes from 86.43.38.8: icmp_seq=10 ttl=58 time=29.713 ms
64 bytes from 86.43.38.8: icmp_seq=11 ttl=58 time=145.190 ms
64 bytes from 86.43.38.8: icmp_seq=12 ttl=58 time=132.880 ms
64 bytes from 86.43.38.8: icmp_seq=13 ttl=58 time=43.138 ms
64 bytes from 86.43.38.8: icmp_seq=14 ttl=58 time=32.091 ms
64 bytes from 86.43.38.8: icmp_seq=15 ttl=58 time=31.129 ms
64 bytes from 86.43.38.8: icmp_seq=16 ttl=58 time=32.405 ms
64 bytes from 86.43.38.8: icmp_seq=17 ttl=58 time=33.613 ms
64 bytes from 86.43.38.8: icmp_seq=18 ttl=58 time=32.463 ms
64 bytes from 86.43.38.8: icmp_seq=19 ttl=58 time=29.831 ms
64 bytes from 86.43.38.8: icmp_seq=20 ttl=58 time=32.470 ms
64 bytes from 86.43.38.8: icmp_seq=21 ttl=58 time=32.522 ms
64 bytes from 86.43.38.8: icmp_seq=22 ttl=58 time=29.876 ms
64 bytes from 86.43.38.8: icmp_seq=23 ttl=58 time=32.472 ms
64 bytes from 86.43.38.8: icmp_seq=24 ttl=58 time=29.744 ms
64 bytes from 86.43.38.8: icmp_seq=25 ttl=58 time=32.941 ms
64 bytes from 86.43.38.8: icmp_seq=26 ttl=58 time=32.953 ms
64 bytes from 86.43.38.8: icmp_seq=27 ttl=58 time=31.839 ms
64 bytes from 86.43.38.8: icmp_seq=28 ttl=58 time=29.566 ms
64 bytes from 86.43.38.8: icmp_seq=29 ttl=58 time=31.459 ms
64 bytes from 86.43.38.8: icmp_seq=30 ttl=58 time=29.997 ms
64 bytes from 86.43.38.8: icmp_seq=31 ttl=58 time=29.609 ms
64 bytes from 86.43.38.8: icmp_seq=32 ttl=58 time=29.907 ms
64 bytes from 86.43.38.8: icmp_seq=33 ttl=58 time=30.981 ms
64 bytes from 86.43.38.8: icmp_seq=34 ttl=58 time=34.842 ms
64 bytes from 86.43.38.8: icmp_seq=35 ttl=58 time=33.737 ms
64 bytes from 86.43.38.8: icmp_seq=36 ttl=58 time=32.725 ms
64 bytes from 86.43.38.8: icmp_seq=37 ttl=58 time=32.776 ms
64 bytes from 86.43.38.8: icmp_seq=38 ttl=58 time=35.169 ms
64 bytes from 86.43.38.8: icmp_seq=39 ttl=58 time=32.026 ms
64 bytes from 86.43.38.8: icmp_seq=40 ttl=58 time=33.268 ms
64 bytes from 86.43.38.8: icmp_seq=41 ttl=58 time=32.302 ms
64 bytes from 86.43.38.8: icmp_seq=42 ttl=58 time=29.423 ms
64 bytes from 86.43.38.8: icmp_seq=43 ttl=58 time=33.074 ms
64 bytes from 86.43.38.8: icmp_seq=44 ttl=58 time=29.939 ms
64 bytes from 86.43.38.8: icmp_seq=45 ttl=58 time=29.304 ms
64 bytes from 86.43.38.8: icmp_seq=46 ttl=58 time=30.173 ms
64 bytes from 86.43.38.8: icmp_seq=47 ttl=58 time=30.398 ms
64 bytes from 86.43.38.8: icmp_seq=48 ttl=58 time=29.364 ms
64 bytes from 86.43.38.8: icmp_seq=49 ttl=58 time=302.888 ms
64 bytes from 86.43.38.8: icmp_seq=50 ttl=58 time=253.223 ms
64 bytes from 86.43.38.8: icmp_seq=51 ttl=58 time=303.472 ms
64 bytes from 86.43.38.8: icmp_seq=52 ttl=58 time=348.412 ms
64 bytes from 86.43.38.8: icmp_seq=53 ttl=58 time=363.532 ms
64 bytes from 86.43.38.8: icmp_seq=54 ttl=58 time=233.808 ms
64 bytes from 86.43.38.8: icmp_seq=55 ttl=58 time=422.526 ms
64 bytes from 86.43.38.8: icmp_seq=56 ttl=58 time=335.582 ms
64 bytes from 86.43.38.8: icmp_seq=57 ttl=58 time=288.321 ms
64 bytes from 86.43.38.8: icmp_seq=58 ttl=58 time=387.546 ms
64 bytes from 86.43.38.8: icmp_seq=59 ttl=58 time=228.399 ms
64 bytes from 86.43.38.8: icmp_seq=60 ttl=58 time=72.247 ms
64 bytes from 86.43.38.8: icmp_seq=61 ttl=58 time=36.190 ms
64 bytes from 86.43.38.8: icmp_seq=62 ttl=58 time=36.197 ms
64 bytes from 86.43.38.8: icmp_seq=63 ttl=58 time=29.181 ms
64 bytes from 86.43.38.8: icmp_seq=64 ttl=58 time=29.669 ms
64 bytes from 86.43.38.8: icmp_seq=65 ttl=58 time=30.259 ms

Traceroute:

traceroute to eircom.net (86.43.38.8), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 4.582 ms 4.398 ms 1.399 ms
2 b-ras1.rtd.sligo.eircom.net (159.134.155.25) 23.523 ms 24.615 ms 24.840 ms
3 ge-1-1-7.pe1.rtd.rsl-rtd.eircom.net (86.43.247.1) 35.254 ms 26.544 ms 24.454 ms
4 tenge-7-1-1.core2.dbn.core.eircom.net (86.43.253.65) 32.717 ms 35.623 ms 29.761 ms
5 tenge-1-2-1.pe2.crz.crz-crz.eircom.net (86.43.252.138) 39.468 ms 29.833 ms 29.991 ms
6 ge1-5.service4.cra.dublin.eircom.net (159.134.125.46) 38.347 ms 32.018 ms 28.599 ms

And a Speedtest: