Ongoing Service Disruption Due to Billing Migration

Update: We have identified a period of time during which notifications were not being appropriately sent due to the billing migration.

We have identified the root cause and are notifying impacted customers as soon as possible.

This incident is now resolved

Update: The API access issue has been resolved. All services are now operating normally.

We will continue to monitor to ensure stability.
A full root cause analysis and post-incident report will follow.

Update: We have identified the root cause and a fix is currently being deployed.

We expect the issue to be fully resolved within the next 15 minutes and will continue to monitor closely.

We will confirm once service is restored.

Update: The billing access issue on the main application has been resolved.

However, we are aware of reports from customers encountering "Forbidden" errors when using the Plain API.

We are actively investigating and will provide further updates as they become available.

Update: The billing access issue on the main application has been resolved.

However, we are aware of reports from customers encountering "Forbidden" errors when using the Plain API.

We are actively investigating and will provide further updates as they become available.

At 10:00 AM GMT, we completed a planned migration of our billing provider.

During the transition, some workspaces may have briefly encountered a billing paywall prompt.
Service was fully restored within minutes.

We apologize for any disruption this may have caused.

We migrated billing provider at 10am GMT. Workspaces may have noticed a billing paywall blip for a few minutes during the cutover. We apologise for any inconvenience