Is AirwaySim up or down - Check the status page

[Sami]

If you ever wonder if AirwaySim's server is unreachable or slow from your location, you should check our uptime status page. It tells you if we are actually live or down for some reason.

System is provided by a third-party monitoring service, and they check the status of our server every minute from various locations around the world. Besides of the simple "up or down" status also the average page response times are shown.

http://uptime.airwaysim.com

[Mort]

Page can't be reached it seems 

[Verto]

Same - ironically the uptime page is the only down page.

[DanDan]

for me it works... 

[JumboShrimp]

does not work for me.

[Sami]

Might take a while for your DNS record to update (browser restart might also help in that)

[Cardinal]

The connection has timed out

The server at uptime.airwaysim.com is taking too long to respond.

    The site could be temporarily unavailable or too busy. Try again in a few moments.

[Sami]

 If anyone is still having issues with the uptime server then please post both ping and traceroute results from your location to the uptime server here in this thread. (works for me, but the service provider is asking for more details if there is some issue somewhere)

[JumboShrimp]

It still does not open for me, but I do get a ping and tracert:

Pinging prod-public-reports-691547200.eu-west-1.elb.amazonaws.com [54.77.148.87] with 32 bytes of data:
Reply from 54.77.148.87: bytes=32 time=98ms TTL=229
Reply from 54.77.148.87: bytes=32 time=99ms TTL=229
Reply from 54.77.148.87: bytes=32 time=96ms TTL=229
Reply from 54.77.148.87: bytes=32 time=92ms TTL=229

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


Tracing route to prod-public-reports-691547200.eu-west-1.elb.amazonaws.com [54.77.148.87]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  routerlogin.net [192.168.0.1]
  2    21 ms    17 ms    16 ms  cpe-184-153-0-1.nyc.res.rr.com [184.153.0.1]
  3    11 ms     9 ms     9 ms  be40.nyclnyrg02h.nyc.rr.com [68.173.200.94]
  4    14 ms    22 ms    18 ms  agg101.nyquny9101r.nyc.rr.com [68.173.198.34]
  5    14 ms    14 ms    23 ms  bu-ether25.nycmny837aw-bcr00.tbone.rr.com [107.14.19.22]
  6    14 ms     9 ms    14 ms  0.ae1.pr0.nyc20.tbone.rr.com [66.109.6.163]
  7    16 ms    13 ms    19 ms  ix-ae-10-0.tcore1.n75-new-york.as6453.net [66.110.96.13]
  8    77 ms    78 ms    80 ms  if-ae-12-2.tcore2.nto-new-york.as6453.net [66.110.96.6]
  9    88 ms    87 ms    88 ms  if-ae-32-2.tcore2.ldn-london.as6453.net [63.243.216.23]
 10    80 ms    87 ms    80 ms  80.231.20.82
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13    99 ms   105 ms    96 ms  176.32.106.176
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28    95 ms   100 ms    99 ms  ec2-54-77-148-87.eu-west-1.compute.amazonaws.com [54.77.148.87]

Trace complete.

[Sami]

Try with another browser if its cache related issue?

[schro]

There's no SSL on it, only HTTP, so if you go to https://uptime.airwaysim.com it just spins in circles, but if you go to http:// it loads just fine. May need to redirect to the insecure page or get SSL up on it? It's on an Amazon ELB, so it shouldn't be too hard...

[JumboShrimp]

It seems to be a DNS issue, I would just give it another day.

I tried 3 browsers, my cable and phone ISPs, and I am not getting it on either of these yet.

[schro]

It seems to be a DNS issue, I would just give it another day.

I tried 3 browsers, my cable and phone ISPs, and I am not getting it on either of these yet.

Are you visiting http:// or https://  ??

[JumboShrimp]

Are you visiting http:// or https://  ??

I did it both ways

[schro]

I did it both ways

Ok, so... it looks like the page is a mess of http and https resources, and I see at least 2 of them throwing 307 errors, at least one of which for HSTS (ga.js/google analytics).

Based upon this article - that header can be responsible for stuff jumping the curb. However, why it does it for you and not everyone else is a bit odd....

[JumboShrimp]

Looks like the problem is that I am being re-directed in the browser from http to https and there is nothing on https.

This redirect takes place (for me) under IE, Chrome, Edge (on PC) and also under Safari on T-Mobile (WIFI off)

[Cardinal]

Pinging prod-public-reports-691547200.eu-west-1.elb.amazonaws.com [54.77.148.87] with 32 bytes of data:
Reply from 54.77.148.87: bytes=32 time=109ms TTL=232
Reply from 54.77.148.87: bytes=32 time=109ms TTL=232
Reply from 54.77.148.87: bytes=32 time=109ms TTL=232
Reply from 54.77.148.87: bytes=32 time=109ms TTL=232

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

Tracing route to prod-public-reports-691547200.eu-west-1.elb.amazonaws.com [54.77.148.87]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.2.0.1
  2     2 ms     2 ms     2 ms  wsip-24-248-22-161.hr.hr.cox.net [24.248.22.161]
  3     2 ms     2 ms     2 ms  172.22.51.120
  4     2 ms     1 ms     1 ms  172.22.51.120
  5     7 ms     7 ms    13 ms  ashbbprj01-ae2.rd.as.cox.net [68.1.0.242]
  6     *        *        *     Request timed out.
  7     *       85 ms    85 ms  ae-2-3202.ear2.paris1.level3.net [4.69.140.34]
  8    92 ms    92 ms    92 ms  212.73.243.158
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26   109 ms   109 ms   109 ms  ec2-54-77-148-87.eu-west-1.compute.amazonaws.com [54.77.148.87]

[Sami]

I think I need to consult the Pingdom guys a bit on how to build a web page, eh .. 

(their uptime monitoring system itself works well though - I'm getting automated email/SMS alerts if the AWS server doesn't respond to ping or http page doesn't load. Been using that for years already. Not that we've had that may outages (once every 5 years?), but still good to have.)

[JumboShrimp]

Just checked again, and it is now working for me.