BRU1 instances are timing outFebruary 14, 2019 at 11:06am
Ever since 6 hours ago, our website monitoring service tells us that NOW is being down.
Looking deeper, it seems that all this instances are down at the minute they get accessed anywhere in Europe and they seem fine anywhere in America.
Also, if I try to do another deployment and alias it the bru1 instance times out.
Any thoughts into why this is happening?
February 14, 2019 at 11:07am
Meta version 1 id IWov7vDHchgiLMQIKkRWJBID name @leaffm/campaign-manager readyState READY type NPM affinity random url leaffmcampaign-manager-qaexytwryz.now.sh createdAt Wed Feb 13 2019 16:44:14 GMT+0000 (Greenwich Mean Time) [19h ago]
Scale dc min max current bru1 1 1 1 gru1 0 0 0 iad1 0 0 0 sfo1 1 1 1
Events 2019-02-13T16:44:14.381Z state INITIALIZING 2019-02-13T16:44:17.564Z build-start 2019-02-13T16:47:28.934Z build-complete 2019-02-13T16:47:28.986Z state READY 2019-02-13T16:47:35.000Z instance-start (sfo1) 2019-02-13T16:49:39.000Z instance-start (bru1) 2019-02-13T16:49:40.193Z scale-set 2019-02-14T03:41:58.000Z instance-stop (bru1) 2019-02-14T03:53:31.000Z instance-start (bru1) 2019-02-14T03:58:37.000Z instance-stop (bru1) 2019-02-14T04:35:52.000Z instance-stop 2019-02-14T04:42:44.000Z instance-stop (bru1) 2019-02-14T04:43:26.000Z instance-start (bru1) 2019-02-14T05:59:32.000Z instance-stop (bru1) 2019-02-14T06:00:49.000Z instance-start (bru1) 2019-02-14T06:08:31.000Z instance-stop 2019-02-14T06:25:23.000Z instance-start (bru1) 2019-02-14T06:30:16.000Z instance-stop (bru1) 2019-02-14T06:33:43.000Z instance-stop 2019-02-14T09:00:13.000Z instance-stop 2019-02-14T09:59:59.000Z instance-start (bru1) 2019-02-14T10:03:44.972Z scale-set 2019-02-14T10:16:52.606Z scale-set 2019-02-14T10:25:24.000Z instance-start (bru1)
I sent an email to support initially 1 hour and a half ago.
my production instance is unstable
and no one has answered :( that's why I tried to reach here
Kevin give me a deployment URL. If this is afecting more people @helguita then it must be something...
this deployment URL was working fine 20 hours ago.
it was since 5 hours ago that this started happening.