thinkshiv

Hi all - Shiv from Auth0. I am the CPO and wanted to share some additional context here. On July 31st 2019, at 5:11 am, we received an email from Insomnia reporting a service vulnerability. By 11:00 pm the same day, we had fixed the issue in production. We analyzed the logs and validated that no one exploited the vulnerability. More details from our CSO here: https://auth0.com/blog/insomnia-security-disclosure/?utm_sou.... Thanks to Insomnia for reporting the vulnerability and their partnership in coordinated disclosure. We appreciate the continued feedback from the security community-at-large to ensure we are providing the most secure platform for our global customers.

Now resolved

And in full transparency in case it comes up here we are also investigating some intermittent access issues to our dashboard (only affects some users not all). Status here: https://status.auth0.com/incidents/1j399kcrzgzr

Are you still seeing failures?

Update: Our response team have found the root cause and have applied a fix. Response times are now back to normal. We will publish a post-mortem within the next 7 days; further updates will also be published http://status.auth0.com/incidents/rpctnc6jd1kl. Thank you for your understanding and we applogize for the degraded service and outage. Should you have any queries please don’t hesitate to reach out to your Auth0 team. Discloure: I am the CPO at Auth0.

Sorry for the status title. The service was initially degraded and then 500ing so acknowledge your feedback and we will add this to our post-mortem. FYI - I am the CPO at Auth0 and apologize for the outage. All services are now back up and we are monitoring them actively. You can follow along here: http://status.auth0.com/incidents/rpctnc6jd1kl

check this out: https://github.com/kubernetes/kompose

Check this out: https://github.com/kubernetes/kompose and this article may help: https://www.digitalocean.com/community/tutorials/modernizing...

Appreciate the feedback, love and loyalty :)

Redis and Kafka are both on the roadmap for the second half. We are starting with PostgreSQL in Q1 and then MySQL.

that is correct

Echoing @gtf21 and @chrisweekly: in short, us taking out the complexity in using and scaling with cloud capabilities and making learning easy for all developers has been our innovation. We don't always have to be the first to launch to add value to millions of developers around the world :)

We have a big roadmap for 2019. Queues are interesting and so are functions in general. Nothing to share today but those are items we are assessing for future roadmaps :)

We are working on this but don't have a date to share today. I know many of our customers want it and we may be able to offer it in later 2019.

hi, yes no charges for the managed / master nodes. This is Shiv from DO (I head Products there).

yes it is

hey there, shiv here from DO. I will get you in both programs asap.

yes, it's next on our roadmap of engines. I work at DO FYI.

We've been working on this for some time. We announced earlier in the year that we want to offer this type of a managed service and we will start with one engine for now. Disclosure: I lead Products at DigitalOcean.

Hi there! I lead products at DO and we've had DBaaS on our roadmap for some time now.

Hi there, this is Shiv - I am the VP of Product at DigitalOcean. Thanks for asking about pricing. We are still working out the pricing details. I can tell you it won't be just the cost of the Droplet because this is a managed service with lots of additional features that you would not get with the current Droplet product.