Prisma

<@U45JCS258> there's a intercom chat window on your console.graph.cool project

they haven't responded to me, but they may take action more urgently if others report as well

We are investigating intermittent issues. Please track <https://status.graph.cool/> to stay informed of our progress. We are resolving this as fast as possible.

We have resolved the connectivity issues and have identified issues with our alerting infrastructure that we will resolve. You can find a detailed description of what happened here <https://status.graph.cool/>. I'm sorry for the caused inconvenience.

<@UB4QV2QAW> my last question asked 4 weeks ago shows as never seen

When I started like a year ago, they were really responsive.  One reason why I continued down the graph.cool path.  Getting close to a beta now and am starting to question whether I can release on this platform

well i emant im having similar problems in the sense that the api is down but yeah unresponsive so far

Will upgrading to prisma make any difference?

in terms of avoiding major outages like this

I get the sense that they are pushing everyone to prisma but now I need a prisma server and a database server so now you have 2 points of failure

<@UBN5LLP28> You could self-host the graphcool-framework if you'd like

<@U0RQY0KK5> getting 504 on sll my apps 
```
receiveTimestamp:  "2018-07-11T02:51:24.644270753Z"  
 resource: {…}  
 textPayload:  "  message: 'Network error: Network request failed with status 504 - "Gateway Time-out"',
"  
 timestamp:  "2018-07-11T02:51:20Z"
```

<@UBN5LLP28> are you on a pay tier or free tier?  Just curious because I understand the free tier taking a back seat but I would expect the pay tier to get better service?

yes <@U9J3Z0GDA> Several people including myself have been experiencing the same thing

4 days after launch for one…. ugh.. have ads running atm

we’re in the middle of prisma migrate.. its a BIG undertaking

everyone send email to support@graph.cool thats where ive always had fastest response