Engine Yard403 Forbidden callback errors
The incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The incident has been resolved.
Resolved
SMS functionality has been restored to normal operations for all affected short codes on US carrier networks. The service disruption, caused by a Twilio incident, has been fully resolved. We continue monitoring to ensure optimal performance.
Resolved
This incident has been resolved. A fix has been deployed to address the issue affecting Classic interactions when used alongside GSAP interactions on recently published sites. Only sites that were published with both Classic and GSAP interactions between 3:55 PM PST and 9:11 PM PST will need to be republished for the fix to take effect.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
A PagerDuty outage prevented some Trigger and SLO notifications from reaching your workspaces. The issue has since been resolved, and notification systems are now operating normally. Impact Window: 21:54 PT – 23:27 PT
Resolved
We've continued to monitor this incident and can confirm it has now been resolved. We apologise for any inconvenience caused. If you are still facing issues with the service, please reach out to our support team here https://support.speechmatics.com/hc/en-gb.
Resolved
The network errors have stopped and request levels are back to normal. Query engines are being successfully provisioned in us-east-1 again and console.prisma.io and api.prisma.io are fully operational again.
Resolved
PagerDuty notifications deliveries are back to normal.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We have identified the cause of the issue and resolved it. Thanks so much for bearing with us while we investigated and resolved this! We’re sorry for the trouble as well. If you experience any further issues, please raise a ticket through our Help Center. Thanks!
Resolved
We identified that a subset of jobs submitted to our Batch SaaS EU1/US1 endpoints between 15:22 and 15:54 BST were not accepted and resulted in 5XX errors. The issue was traced to a misconfiguration in one of our services, which has since been corrected, and normal performance has been restored. We apologise for the inconvenience caused.
Resolved
This incident has been resolved.
Resolved
We have determined the cause and implemented a fix. Customers should be seeing normal operations again.
Resolved
Between 10:50am - 11:03am US/Eastern on 8/27/25, we experienced an issue that resulted in errors accessing the Klaviyo app, disruption in event ingestion, and issues submitting signup forms. We have resolved the issue.
Resolved
issue resloved pipeline is completed.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Access to the Dashboard and Webflow.com has been fully restored, and this incident is now resolved. The disruption occurred between approximately 16:04 UTC and 17:32 UTC. If you continue to encounter issues, please clear your browser cache (Ctrl/Cmd + Shift + R) and try again. The issue was caused by a third-party tracker on webflow.com. We have implemented a change to prevent this from happening again. Customers who were already logged into the Webflow Designer or Dashboard may not have been affected, and no Webflow hosted sites were impacted. We sincerely appreciate your patience while our team worked to restore full access.
Resolved
This incident has been resolved.
Resolved
API calls to api.cloudinary.com for clouds in EU/AP geo-regions may have experienced failures with 404 status code responses at approximately 7:20-11:20 UTC.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
A database issue caused profile-related disruptions for approximately 50% of users. The incident lasted around 2 hours and was resolved by restarting the affected systems. To help prevent future occurrences, we’re updating system settings, improving monitoring, and optimizing backend processes.
Resolved
Llama-3.3-70B endpoint experienced reduced availability starting at approximately 7:45am PT. Endpoint went back to full availability starting 8:55am PT.
Resolved
This incident has been resolved.
Resolved
The plugin portal suffered connection issues possibly related to incidents with the different providers used: * Heroku: https://status.heroku.com/incidents/2867 * AWS: https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/INTERNETCONNECTIVITY/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE/AWS_INTERNETCONNECTIVITY_OPERATIONAL_ISSUE_49824_16DD211EFC1 When restarted, the application started behaving properly.
Resolved
The site loading issue affecting users in Brazil is now resolved. Sites are now loading normally. The issue was related to external network conditions with third-party Latin American ISP providers. We have done an extensive investigation and found the issue to be caused by the routing before it reaches Wix. No further action is required. We will continue monitoring to ensure stability.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Braze Engineers have confirmed US clusters are operating within normal operational bounds. Engineers will continue to monitor service health across all US clusters. This incident has been resolved.
Resolved
The upstream provider has identified and fixed the issue. We have seen normal operations for the past 30 min. We'll continue monitoring.
Resolved
This incident has been resolved.
Resolved
Our third-party provider has implemented a fix, and impacted services should now be working as expected. If your site was published during the incident, we recommend republishing it at this time to ensure everything updates correctly.
Resolved