This message was deleted.

https://status.pulumi.com/ claims no. But who knows how reliable that is. I've seem Travis claim no outages while one was in progress.

i just got a 10 minute timeout on a Fargate service, so yeah I think something might be down

There aren't any known outages or performance issues at the moment, but we are checking things on our side.

@rhythmic-finland-36256 what timeout errors are you seeing exactly? @big-nail-28315 the 10 minute timeout on Fargate tasks is likely the default creation timeout for the resource.

updating urnpulumidev:apiawsxxecsFargateService$awsecs/serviceService:customer dev timeout while waiting for state to become ‘true’ (last state: ‘false’, timeout: 10m0s)

Yes - that just means your service wasn’t healthy yet after 10 minutes.

Ah. I hadn’t seen it before with the same setup. I’m still learning all this stuff...my bad

There are further reports on slow answers, timeouts and app.pulumi.com not being reachable at all. https://pulumi-community.slack.com/archives/C84L4E3N1/p1567611744249300

@rhythmic-finland-36256 not sure if Igor is experiencing the same issue as you did. We are trying to confirm with him. We are keeping a close eye on this, but so far we aren’t seeing anything that would cause a timeout on our end. Are you sure it is not your internet connection? Are you still having trouble connecting to https://app.pulumi.com?

@rhythmic-finland-36256 Could you share details of any errors you are seeing? Are you seeing errors visiting

<http://app.pulumi.com|app.pulumi.com>

, or using the

pulumi

CLI?

For me it was both, using the website and from CLI. My internet connection is not the best at the moment as I’m traveling by train today and run into some timeouts every now and then. But I observed some isses for more than an hour and other sites worked pretty reliably. From CLI perspective I would think about low connection timeout settings but I experienced the same in the browser. For now it seems to work again (with the same quality as other services).

What errors exactly did you see? 404? Something else?

Just connection timeouts