User Discontent with Airbyte ETL Connector

Slack Knowledge Base Q&A Connector Development
, , , ,
1

Summary

User reports a broken connector after 1 month and dissatisfaction with support response time, leading to migration to another ETL solution.


Question

For those of you considering airbyte for ETL, I would look somewhere else. Our connector broke after about 1 month of usage and never heard back from support. We waited 6 days and then moved everything over to stitch.


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['etl', 'connector', 'support', 'migration', 'stitch']
2

I’m surprised to hear that, from what I’ve seen their support team is pretty on top of things (this was Airbyte Cloud, right?)

I’m also curious what the source/destination systems were. It’s pretty odd to get random breakage like that from a pipeline that’s running with all other things being equal.

3

What connector were you using <@U083A3QQV7S>?