Sentry Status

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.

Resolved: We had a database corruption where new org creation, user sign-ups, new API Token generation, and new integrations made between 3:45PM and 5:00PM PST were affected and will need to be re-created. No other data were affected.

We are very sorry for this inconvenience.

Monitoring: We restored the impacted services to operational state, while investigating the full impact of the incident

Monitoring: We are continuing to monitor for any further issues.

Monitoring: We implemented a fix for the issue and monitoring

Identified: We're implementing a fix for the issue

Investigating: We detected a data corruption in one of our databases and investigating the issue

Investigating: We are currently investigating this issue.