←View full Cursor status
Cursor: Webhook Failed / Integration Error
Current Status: Major Outage
Last checked: 16m ago
What We're Seeing Right Now
No recent issues reported. If you're experiencing problems with Cursor, report below to help the community.
What is this error?
When Cursor's webhooks or integrations fail, automated workflows, notifications, and connected services stop receiving updates. This breaks CI/CD pipelines and team collaboration tools.
Error Signatures
Webhook delivery failedIntegration errorConnection refusedEndpoint not foundWebhook timed outDelivery failed after retriesIntegration disconnectedCommon Causes
- Webhook endpoint is unreachable or returning errors
- Cursor's webhook delivery service is down
- Authentication changed on the receiving end
- Payload format changed after an update
- Rate limit on webhook deliveries
✓ How to Fix It
- Check the webhook delivery logs in Cursor's settings
- Verify your endpoint URL is correct and reachable
- Check authentication credentials on both sides
- Test with a simple webhook receiver (e.g., webhook.site)
- Check this page for Cursor integration issues
- Re-register the webhook if needed
Cursor Resources:
Live Signals
Service Components
Cursor App
OperationalCursor AI Features
OperationalRecent Incidents
CRITICAL✓ Resolved
AI features unavailable
Cursor AI code completion and suggestions completely offline for 2 hours
5d ago → 5d ago
Frequently Asked Questions
Why are Cursor webhooks not working?
Check webhook logs, endpoint availability, and authentication. If Cursor-wide, check the status above.
Is Cursor webhook service down?
Check community reports below.
How do I debug Cursor webhook failures?
Check delivery logs, test with webhook.site, verify credentials, and check for payload format changes.