https://linen.dev logo
Powered by
Composio still fully down, your response is lackin...
# 🖥│support-forum
r
Platform is totally broken, you have not even followed the steps you laid out in your blog post. Don't drop the blog post as a response here, your CEO should step up and actually tell us what is going on.
r
hey rj deeply apologize
our consumer product is currently entirely down correct including our dashboard
r
we are on the business product
*enterprise
r
can you give me more context on what you are using and seeing as down
r
all connections are failing for all users
r
yeah so we did revoke connections for the users like we mentioned
r
appreciate your response Rahul, but its time for Karan to step up and start responding to this and being clearer about the scope of the breach
they cannot reauthenticate back in
r
those revoked connections will not work
r
ok
so when will the product be back online, no estimates or anything are available
k
Hey @rj, really sorry for the issue. On the scope of breach till now from what we know is limited, but we revoked the accounts as we rotated our own secrets out of precaution. What is the issue you are facing related to reauth? What error are you getting. We expect the APIs to be normal, and are working to get the whole surface area back.
r
users and dev are getting 401s whenever they try to reconnect and in the logs we see instantly that the token was revoked again
@Karan thanks for responding, since you revoked a lot more than github is there an indication that user data was breached in other apps?
k
> An auxiliary cache service the attacker likely had access to had 5,241 API keys during the breach window. These api keys have a higher potential of being compromised. As a preventative measure, we have revovked these api keys which might have caused downtime to production customers. in this disclosure we know it is possible for an attacker to gain access to other apps, we do not see any direct evidence of breach but being caution we started revoking access
r
users and dev are getting 401s whenever they try to reconnect and in the logs we see instantly that the token was revoked again ?
t
A small number of accounts have temporary access issues during the security work described in the bulletin: https://composio.dev/blog/composio-may-2026-security-incident. We expect services to be fully operational shortly.
r
@Thomas @Karan @Rahul we are going on 48 hours of unstable to fully broken functionality for our users. Is there an ETA on when this will be fixed and when an external auditor will provide a full report on the entire scope of this incident?
k
We are trying our best to get it up asap. Expect improvements over the day.
b
When will access to the dashboard be restored?
s
any update on the dashboard being up again?
@Karan @Rahul
is there an eta
s
Over the day??!!
r
@Bill Ann // @siddharth we are working on getting it back up, don't have a confirmed eta.
r
@Karan what is the update on the incident, we still have customers reporting issues and the blog post hasn't been updated in close to 24hrs
k
Is there an update here? We can't create any new API keys despite the dashboard saying it should be one of the few things allowed. Your status page saying the platform is up is a joke, right?
k
@Karan @Rahul Any update on the incident please. all of our users are impacted and apparantly all tool calls are failing. dashboard is completely unusable. cant even create an incident.
r
@Karan @Thomas @Rahul where is the update>
s
@Karan @Rahul We would also like an update. Customers cannot reconnect accounts.
m
hello?? Feels like we're speaking to a wall.
j
Hi there! Any news on this problem?
w
Did I pick a bad time to switch from Pipedream?
s
its perfect time to swith to pipedream, I just moved today
t
hey @shea7544 thank you for point this out, I will raise this to the team immediately. For now you should be able to login at dashboard.composio.dev. We are working diligently in the background to get to full functionality
m
is piepdream the best alternative?
r
@Karan where is the update...
m
was about to ask the same...
w
Yes, it has a bit more of a learning curve because it has wider uses, but it's comparably priced and dependable.
t
My connect links are redirecting users to the Composio dashboard/login instead of the third-party OAuth consent screen, so new users can’t connect accounts or reauthorize existing ones. Also cannot submit a support ticket on Composio dashboard.
Is there an ETA for restoring connect flows? We’re trying to decide whether to wait or start migrating auth/connect flows to Pipedream.
t
Hey Everyone, we're very sorry about the disruption and the speed of communication here. We're working hard to get the platform back to fully functioning as fast as we can. We have temporarily disabled the following features: - Proxy Execute - Magic link sign-in - Org and project API key creation We have added the following Added: - IP allowlisting - Platform-wide rate limiting If you're blocked by rate limits or need whitelisting/allowlisting set up, you can email me personally (thomas@composio.dev) and I'll handle it. We'll send a follow-up the moment everything is back online. Thanks for your patience
d
whats ETA for this?
r
API keys are still blocked and I can't have any integration working because you deleted all API keys
t
The dashboard is up. We just enabled the ability to creating a new access token and APIs. You should be able to do everything programatically, just not in the platform. Will keep updates flowing
k
@Thomas Thank you for the update. Unfortunately, the connections are still not working via API routes.
t
let me check for you, one sec
k
it did work a few hours before for once or twice though and I sent users notifications that its working. unfortunately, its again broken. and for early stage startups like us, this is causing a huge user trust damage. would be great to have some formal comms
t
@Kno2GetherAdmin you can send support@composio.dev an email and include me (thomas@composio.dev) on the email. We're going to get this sorted out for you
k
sure thanks
k
@Kno2GetherAdmin Quick call?
k
This is what I m seeing now "This v1 endpoint has been retired. Please migrate to the equivalent /api/v3 endpoint." has there been an retirement of api which I have missed. it actually worked couple of hours before !!
Earlier the failure was "💥 Oops! Internal server error on https://backend.composio.dev/api/v2/connectedAccounts/initiateConnection","level":"error","message":"Failed to generate Composio OAuth URL","stack":"ComposioError: 💥 Oops! Internal server error on https://backend.composio.dev/api/v2/connectedAccounts/initiateConnection\n at CEG.throwAPIError (/app/node_modules/composio-core/index.js:757:15)\n at CEG.handleAllError (/app/node_modules/composio-core/index.js:725:35)\n at ConnectedAccounts.initiate (/app/node_modules/composio-core/index.js:2383:23)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async ComposioOAuthProvider.generateAuthUrl (/app/dist/providers/composio/oauth.js:73:37)\n at async /app/dist/routes/oauth.js:156:27","timestamp":"2026-05-25T14:18:26.973Z","userId":"c6e553c7-2f70-4f49-ac63-a3231ed8bafd"}
sure can have a quick call, if its easy
k
Hey yes, we had to take down v1 APIs. Do you mind moving to v3 or new SDK. Sorry we have been communicating for the same for a while.
And had to take it down due to a potential vulnerability
k
okay ! was there a deadline today ?
right okay !! would you mind send me the note please. I can do that
then upgrade the sdk and release it tonight ! thanks for notifying !
k
Our new SDKs have been on v3 for more than 12 months now.
k
beause I m quite sure, it was working earlier today
k
Yeah, we had to take it down today. Really sorry
Has the SDK for new APIs
r
@Karan can you help our team out right now?
k
right okay ! no worries. I understand security vulnerabilities can be really pain as I come from cybersec background, its just I was not aware of any deadline of that being taken down. as a early stage startup, we had a lot of other open source library vulnerability to take care off and really didn't pay attention to yours one !
Thanks bdw for prompt response ! best of luck
k
Thanks for the understanding
Let me know if you face any issue while you are migrating
k
sure. thanks
@Karan the migration seems worked atleast in my local however it seems one of the custom apps are not working. I m going to send it to test to the team for all of our apps (37+) and come back on this tomorrow. if there is any issue , will reach out via support email or use this thread
@Karan Regression pipelines looks good ! thanks for the help !
d
Hello @Thomas @Karan Can you please share if I can somehow create new projects within organisation?
t
let me check for you
found it, you can do this via the api but not in the dashboard. Opened a ticket, will be live tomorrow
d
okay, thank you
r
I still cant create new API keys for my Org?
j
Hey @Thomas, I’m Jayanth from Kore.ai. We’re currently blocked in production after the API key revocation changes. Abhishek helped regenerate the org key, but in our setup each user maps to a project, and we currently have no working way to regenerate project API keys. The endpoint we tried returns 404. Would really appreciate urgent help from the team on this since it’s actively impacting production workflows. Thanks, Jayanth
I've tried the below but it returns curl -X POST "https://backend.composio.dev/api/v3.1/org/owner/project/pr_BuXm1wLnnTrO/regenerate_api_key" \ -H "x-org-api-key: oak_**********EW" { "error": { "message": "Not found", "status": 404 } }
k
We are working on getting this back up. What's your org id?
b
We have regenerated the API key, but we are still receiving an "Invalid API key" error. Do we need to update the SDK version?
c
Triggers are failing to load for me in the dashboard as well when I view a toolkit
2 Views
PreviousNext
Powered by