Anyone else have issue with logging into aws today and yesterday?

[Sami]

When we are tracing from here to some of your IP's, it seems that the routing at Bellsouth is breaking up instead ... But we're investigating.

But as mentioned already before; since this isn't anything to do with us or our ISP or servers we cannot do anything about it.. But our ISP may be able to reroute something.

[spiff23]

I think the issue is with teliaSonera.

I did the trace test (tried print sceen but too small) if someone know how to copy I can put whole thing.
   
Everything is fine till here:

Starting at line 7

7 37ms   36ms  37ms   nyk-bb2-link.telia.net [80.91.246.19]
8   128ms 125ms  *   kbn-bb2-link.telia.net [80.91.247.118]
9 138ms *  *  s-bb2-pos7-0-0.telia.net [213.248.65.30]
10  142ms  *  141ms  hls-b2-link.telia.net [80.91.245.37]
11  * 143 *  TeliaSonera-IC-124322-hls-b4.c.telia.net [80.239.132.61]

I can transcribe more if helpful...at line 14 it says "timed out"

[swiftus27]

Using ATT Bellsouth and having a really difficult time playing. All my other internet use is fine

please do a traceroute to see where the packet loss is.

[spiff23]

thanks for checking...need to head out now.  I did a couple more tracerts...this is what I'm getting now consistently...looks like the breakdown is somewhere between ATT (owns bellsouth and SBC/Ameritech) and Telia.

at line 5


5 19ms 16ms 15ms  ggr3.cgcil.in.attnet [12.122.133.113]
6 18ms 46ms 15ms 192.205.34.198
7 99ms *  * nyk-bb2-link.telia.net [80.91.248.197]
8 * * * Request timed out.

(thanks for the info to get to the DOS screen...[un]fortunately I'm old enough that I do know how to use DOS so I guess I have residual computer skills...it's like riding a bike...hopefully the ISPs can figure out where the breakdown is )

[slither360]

I recently switched from Verizon to Comcast, and now AWS has gotten noticeably slower, to the point of not loading sometimes..

[ACfly]

I'm based in Nashville, USA and yes having real issues.....

[schro]

I did the trace test (tried print sceen but too small) if someone know how to copy I can put whole thing.
   

As long as you're not executing the command in a protected system folder, you can pipe the results to a text file.

For example:

tracert airwaysim.com > tracert.txt

When it finishes running, you'll have a text file with the results.

I agree the issue seems to be with telia, but I'm guessing they are one step removed from the AWS ISP. My path is going from winstream to level 3 to telia to AWS...

[Sami]

FYI, I emailed to our ISP and the msg has been forwarded to their network team for investigation. But no idea if they work on weekends.

In any case these issues are always only temporary.

[swiftus27]

I ran a traceroute....

It takes 24 hops to get to you.  Wow.

I was experiencing some packed loss...  avg went to 178ms and lost 25%

[ACfly]

Ping results ..

Request timed out
25% loss
Round trip time:Average = 154ms

[JumboShrimp]

Ok, now it seems to me affecting me as well (last 2 days approx).  Ping result:

    Packets: Sent = 100, Received = 85, Lost = 15 (15% loss),
Approximate round trip times in milli-seconds:
    Minimum = 119ms, Maximum = 163ms, Average = 124ms

ISP is RoadRunner (Time Warner Cable).  New York City.

[JumboShrimp]

My TraceRt shows the same problem TeliaSonara.  I had to do TraceRt several times to get the entry #13, which is where the breakdown seems to be - consistently.

Tracing route to airwaysim.com [217.30.182.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    27 ms    12 ms     9 ms  cpe-74-73-168-1.nyc.res.rr.com [74.73.168.1]
  3     9 ms    28 ms     9 ms  gig-0-1-0-nycmnyc-rtr2.nyc.rr.com [24.29.157.138]
  4    14 ms     9 ms     9 ms  tengig-12-0-0-nycmnya-rtr1.nyc.rr.com [24.29.97.9]
  5    11 ms     9 ms     9 ms  tenge-0-1-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.150]
  6    10 ms     9 ms    12 ms  ae-4-0.cr0.nyc30.tbone.rr.com [66.109.6.78]
  7    11 ms    12 ms    32 ms  ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
  8    11 ms    12 ms    12 ms  nyk-b5-link.telia.net [213.248.77.177]
  9   188 ms    12 ms    12 ms  nyk-bb2-link.telia.net [80.91.248.161]
10   124 ms   102 ms   102 ms  kbn-bb2-link.telia.net [213.248.64.33]
11   112 ms   111 ms   111 ms  s-bb2-link.telia.net [80.91.246.108]
12   138 ms   135 ms   119 ms  hls-b2-link.telia.net [80.91.247.221]
13     *        *      120 ms  TeliaSonera-IC-124322-hls-b4.c.telia.net [80.239.132.6]
14   134 ms   118 ms   139 ms  crtr1-v1310.lau.hel.fi.nblnet.com [83.150.93.57
15   122 ms   121 ms   121 ms  www.airwaysim.com [217.30.182.14]

[JumboShrimp]

TeliaSonera
Telecommunications provider in the Nordic and Baltic countries, offering mobile and fixed network services. Also a major ISP.
http://www.teliasonera.com/

[ACfly]

Any IT guru know how to use a Proxy server to get around this issue?

For me, it looks like every 3 pages results in a loss connection.. so it is taking a incredibly long time just to do things in airways sim..

[Sami]

Indeed seems to be TeliaSonera who's lagging here. I've googled around and SEVERAL other sites have reported of the same too.

[ACfly]

Indeed seems to be TeliaSonera who's lagging here. I've googled around and SEVERAL other sites have reported of the same too.

so it's not ATT/Bell south.. would this mean that everyone is having this issue, and it's not limited to southern USA?

[Sami]

No, just the ISPs who route their traffic via Telia. And only from US apparently.

[Yullover]

What i got from Montreal, Canada with Videotron service. it's slow but not have difficulty to load pages.

1                   *   *   *
2    HOSGate.your-server.de    213.239.224.1    de    0.165 ms        
   hos-tr2.juniper1.rz10.hetzner.de    213.239.224.33    de    0.188 ms    
   HOSGate.your-server.de    213.239.224.1    de    0.165 ms
3    hos-bb1.juniper1.ffm.hetzner.de    213.239.240.224    de    5.101 ms    4.903 ms    4.900 ms
4    ffm-b2-link.telia.net    213.248.92.81         4.893 ms    4.921 ms    4.931 ms
5    ffm-bb2-link.telia.net    80.91.249.102         5.270 ms        
   ffm-bb1-link.telia.net    80.91.252.169         5.155 ms    
   ffm-bb1-link.telia.net    80.91.247.166         45.846 ms
6    s-bb2-link.telia.net    80.239.147.177         27.388 ms        
   s-bb1-link.telia.net    80.239.147.173         60.877 ms    60.843 ms
7    hls-b2-link.telia.net    80.91.251.32         36.596 ms        
   hls-b2-link.telia.net    80.91.249.3         34.039 ms    
   hls-b2-link.telia.net    80.91.246.85         56.601 ms
8                   *   *   *
9    crtr1-v1310.lau.hel.fi.nblnet.com    83.150.93.57    fi    37.201 ms    39.726 ms    37.175 ms
10                   *   *   *
11                   *   *   *
12                   *   *   *
No reply for 3 hops. Assuming we reached firewall.

[Bolier Dweller]

I believe this outage show that we need  US based server for this exact reason.

[kados]

It's fixed for me