For the last couple of hours I have noted extremely poor (slow, patchy) network performance to my Amazon EC2 instances, US-West N.California. Instances themselves are running totally fine by the look of it.
Anybody else noticing this?
For the last couple of hours I have noted extremely poor (slow, patchy) network performance to my Amazon EC2 instances, US-West N.California. Instances themselves are running totally fine by the look of it.
Anybody else noticing this?
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
![]() ![]() ![]() |
|
Just found that site myself.
(NB: Cable, Christchurch)
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
Are you using Vodafone's DNS servers?
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
michaelmurfy:
Are you using Vodafone's DNS servers?
Yes
$ cat /etc/resolv.conf
nameserver 203.97.78.43
nameserver 203.97.78.44
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
Cool test, but not sure I trust it. It's reporting 460ms latency to EC2 in US-West. I have an EC2 server in US-West and windows ping tells me I'm getting 160ms latency.
timmmay:
Cool test, but not sure I trust it. It's reporting 460ms latency to EC2 in US-West. I have an EC2 server in US-West and windows ping tells me I'm getting 160ms latency.
I agree on this too.
their CDN tests seem about right however..
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
It seems to have started going full tilt again now.
I noticed the routes changed slightly too forat least the instance I was looking at mainly.
Was
...
be10-2.bgnzftc02.akl.vf.net.nz (203.109.130.41)
*
v422.core1.sjc1.he.net (216.218.254.57)
10ge7-2.core1.sjc2.he.net (72.52.92.118)
equinix02-sfo5.amazon.com (206.223.116.236)
...
Now
...
be10-2.bgnzftc02.akl.vf.net.nz (203.109.130.41)
*
v422.core1.sjc1.he.net (216.218.254.57)
100ge1-1.core1.sjc2.he.net (184.105.213.94)
amazon-02-as16509.10gigabitethernet18.switch3.sjc2.he.net (216.218.193.42)
...
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
Spoke too soon, we are back to 10ge7 route and go slow mode.
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
Have opened ticket with VF about it and posted to AWS Support Forum also.
The route for us-west-1 as it leaves VF in San Jose seems to be unstable, as above, on one request it will work fine and on the next it will drag along at less than 10KB/s.
I spun up a test instance on us-west-2 and it seems fine (different route), it's just us-west-1.
Current results from that site...
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
michaelmurfy:
Are you using Vodafone's DNS servers?
VF are advising their cable customers to use Google DNS...
Seems... seems... to be working better today, at least a few hundred KB/s up to a couple MB/s instead of a few KB/s. Given I'm only running against instances up to m3, that's probably within the realms of reason.
Hopefully this post hasn't jinxed it.
---
James Sleeman
I sell lots of stuff for electronic enthusiasts...
|
![]() ![]() ![]() |