Störungsverlauf von Instapage

We have identified an authorization issue with the Salesforce API that is preventing leads from being transmitted successfully through the integration. Our team is working together with the Salesforce team to resolve this as soon as possible. First report date: February 20 Impact: - Leads are currently not being pushed to Salesforce - Integration settings errors: cannot connect/reconnect accounts to the workspace or configure page-level integrations Please rest assured that no data has been lost. All incoming leads are stored in our back-end queue and will be sent once the integration is operational again.

We have released a fix for the Salesforce integration issue. For previously connected Salesforce accounts, re-authentication is required for each workspace: - Navigate to Workspace Settings > Integrations > Salesforce - Click "Re-authenticate" - Log in to your Salesforce account (only users with access and valid credentials for the already connected Salesforce account can complete this step) Re-authenticating will fully restore the connection - new leads will resume syncing normally, and access to page-level integration settings will be restored. Leads collected during the incident have been securely stored and will be processed progressively after re-authentication. New Salesforce accounts can be connected going forward without any issues. We appreciate your patience and understanding.

We have monitored the lead queue and can confirm that the previously missing leads have now been successfully sent to Salesforce for users who completed the re-authentication process. For accounts with a properly re-authenticated Salesforce integration, lead syncing is now functioning as expected.

We are currently investigating an issue causing delays in the publishing flow for pages. Previously published pages remain live, but updating actions may take longer than expected to apply.

The issue has partially stabilized, and the page publishing/updating flow is performing better. Minor delays may still occur while we continue to make improvements.

A fix has been implemented and page publishing/updating processes are stable again. Any pending page updates will be processed shortly. Thank you for your patience!

Cloudflare is down so the Instapage application and landing pages are down as well. You can also monitor their status here: https://www.cloudflarestatus.com/ Unfortunately, our ticketing system is also down because of this, so we are unable to respond at this time.

The Cloudflare team identified the issue and provided a fix. The landing page and the Instapage app are currently working. We are monitoring the situation.

This incident has been resolved, and all services are working as expected.

Multiple Google Cloud Services are down, and this also caused an outage on our application and other services that we are using (CloudFlare). The landing pages that were cached in CloudFlare are still working, but the rest are throwing a 404 error. We are monitoring the situation, and as soon as the GCP products restore, we should be back online.

The Instapage application and the landing pages started to work. The Google infrastructure has recovered in all regions except us-central1, so in this region, there might still be issues. We are monitoring the situation and will update you when we have an official confirmation from Google that their systems are 100% operational. You can also check Google's status page here: https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW.

Google confirmed that they are also seeing recovery in us-central1 and mutli-region/us and that they expect the recovery to be completed in less than an hour. The Instapage application and landing pages still work as expected so we will close this incident. Thank you for your patience and understanding.

We are currently experiencing 403 errors from our email system provider, causing emails to be stuck in a queue. Our team has identified the issue and is working on a solution. Please note that the emails are not lost; they will be sent, but there may be a delay. Thank you for your patience and understanding!

We switched to a backup email provider and transactional emails like password recovery and team invites are going out. Lead notifications are still in the queue, as our email provider needs to complete some steps. We will update you as soon as we have some news. We appreciate your understanding!

We are still waiting for an update from our email provider. The incident status remains unchanged, but we will update it accordingly once we have more information. We apologize for the inconvenience this ongoing issue may cause and appreciate your patience and understanding.

The problem with our email provider has been fixed, and we have begun sending lead notifications successfully again. Today, we are monitoring the situation, and tomorrow morning we will begin processing the queue of emails. Thank you for your patience while we worked to resolve this issue!

We have processed all the queue of emails, and now everything is working and up to date. We also started warming up a new email provider as a backup, but it will take a few weeks to handle the amount of emails we have. After that, we will be having multiple providers warmed up at all times in the future.

We are currently investigating an issue with the email delivery system, impacting lead notifications and potentially other platform emails such as team member invitations, password reset requests, verification emails for new accounts, etc. We apologize for the inconvenience. Our team is working on fixing this as soon as possible.

The issue has been resolved, and the emails that were previously undelivered should go out. Due to the high volume of emails, there will be some delay as they are currently in the queue. Thank you for your patience on this.

We experienced an issue with our Google certificate from the Cloudflare CDN, which caused some inconsistencies in the loading of images in certain geographical regions, such as Texas, California, Florida (US) and Melbourne, AU. However, we are happy to inform you that the issue has been fully resolved, and we have put additional notifications in place to prevent similar situations from happening in the future. We apologize for any inconvenience caused by this incident and appreciate your understanding.

Clients may experience issues with publishing pages on new subdomains. Subdomains recently set up via CNAME return an "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" error on the live URL, due to inability to complete the connection and apply the SSL certificate. More information on the Cloudflare status page: https://www.cloudflarestatus.com/. Once we have more information about the progress, we will update this incident accordingly. Thank you for your patience!

Cloudflare API services are operational: https://www.cloudflarestatus.com/ Enabling SSL certificates is possible again and connecting new subdomains should not pose issues going forward. If there is any delay with the SSL application, please reach out to our team.

Since the Cloudflare transition today (around 7 AM UTC), we have reports of 1014 errors for landing pages published via CNAME on domains hosted with Cloudflar, with proxy mode enabled. Our team has identified the solution and is working to implement it as soon as possible. In the meantime, as a temporary solution for those impacted, we recommend disabling the proxy mode on their hosting if possible.

A fix has been applied which should fully propagate within the next hour. During this time, impacted landing pages should gradually start working.

The fix has been applied and most landing pages using standard implementation/publishing methods have been working for some time now. Please make sure to review our Cloudflare migration guide, if necessary, at this link: https://d.pr/jgq2dv We are working on a resolution for the remaining few pages that still experience issues.

We can confirm that this has been resolved. In case of any lingering page issues related to the Cloudflare migration, please make sure your publishing setup is up to date, as indicated in our migration guide here: https://d.pr/jgq2dv For any questions or further assistance on this matter, please contact our Support team.

Some landing pages returned 500 or 403 errors and experienced slowdown due to an on-going DDOS attack. The issue lasted approximately 5 hours, between 4 AM - 9 AM UTC. We apologize again for any inconvenience this has caused. Our team will continue to monitor the situation and work to prevent this from happening again.

We have reports of some landing pages returning 502 server errors. Our team is currently investigating this, but if you have been impacted, we recommend pausing any paid traffic to your landing pages until this is permanently resolved.

The issue has been traced to a DDOS attack which as been blocked. The affected pages should start working soon but we will monitor the situation and update accordingly

The landing pages are back up and working now, but we will continue to monitor the situation. Please clear your browser cache if needed. If you experience any further issues, please reach out to our Support team. Thank you for your patience and understanding on this matter.

We are experiencing increased number of errors both on the Instapage Application and landing pages. Our team is currently investigating the issue.

Our team has found the root cause and the fix has been applied. We are currently monitoring the situation.

The app is stable now and the landing pages are up and running. If there are any pages still returning 404, please make sure to clear your browser cache. In case of any lingering issues that may be related to this incident, please reach out to our team. We appreciate your patience and understanding while our team worked on resolving this.

We are experiencing an outage at the application level. The landing pages are not affected. We identified the problem and we are working on a fix, the app is expected to be up again in 30 minutes.

The app is working now, but some disruptions may still occur until the system is fully stable. Most of the pages were not affected by this incident, as they were cached on our servers, but some of them might have returned a temporary 404 status code.

The app has now recovered. Some live pages are experiencing 404 status errors. If you are impacted, we recommend pausing any paid traffic to your landing pages until this is resolved. Our team is working on it and it should be fixed shortly. We appreciate your patience and understanding while we are working on this.

The app is stable now and the landing pages are up and running. If there are any pages still returning 404, please make sure to clear your browser cache. In case of any lingering issues that may be related to this incident, please reach out to our team. We appreciate your patience and understanding while our team worked on resolving this.

We are currently experiencing a partial outage at the application level and some live pages return 404 errors. Our team is working on resolving this incident as soon as possible, but we recommend pausing any paid traffic to your landing pages until this is permanently resolved. We appreciate your patience and understanding while we are working on this.

The issue has been traced to a DDOS attack, which has been handled by the team and all is working as expected now. The app is stable and the affected pages should now be back up.

We are aware of an intermittent and sporadic issue affecting requests. How to identify the issue: a browser notification will include the message "Our systems have detected unusual traffic from your computer network." What is being done: - the team is working to identify a possible workaround - the team has escalated to the highest level of support with the Cloud Service Provider We apologize if you were among the users who experience this issue, and we thank you for your patience and understanding!

A promising workaround has been implemented on the backend. We are continuing to work with our service provider and monitor the situation.

The workaround currently in place has proved to be effective. We have not received any further reports of this issue, but we will continue to monitor the situation. Should you encounter this problem again, please report it to our Support team. Thank you for your understanding.

We have identified a DDOS attack on some pages that caused a heavy load on our servers, hence making less than 10% of the overall traffic have a slow loading time or not load at all. Our team has stopped the attack, and we are closely monitoring the situation.

The attack was handled, and all is working as expected. We will still be monitoring closely in case we will get attacked again. We are sorry if your pages got affected by this! Our team will look for ways to prevent this from happening again.

Some users may experience partial responsiveness issues at the application level due to a service disruption reported for the Google Cloud servers. We are working on moving the workloads to a different zone to minimize impact.

The issue seems to have been resolved and the application is stable and functional now.

We are currently experiencing some DNS issues, and the live pages are down. We recommend pausing any paid traffic to your landing pages until this is resolved. Our team is working on it and it should be fixed shortly. We appreciate your patience and understanding while we are working on this.

A fix has been implemented, and we are monitoring the results. The pages started to recover, and they will soon work 100%. Please test them on your end, and start sending traffic again as soon as they work.

We monitored the fix, and all is working as intended. The issue is solved, networking works correctly, and all services are available. Our service responsible for page generation of Thor pages experienced connection issues. Because of that, Thor pages were unavailable, live pages without valid cache were affected and unreachable (404). We have updated our monitoring tool to avoid this kind of issue in the future. Thanks for your understanding!

We have identified a DDOS attack on our network which is causing a large portion of landing pages to be inaccessible or load slowly. Our team is working on deploying a solution. We recommend pausing or diverting ad traffic if your pages are affected, if possible. We believe a fix will be deployed shortly.

A fix has been implemented and the affected pages are now recovering. We are monitoring the situation and believe all pages will start loading as expected over the next 30 minutes.

The incident has been resolved.

We experienced responsiveness issues at the application level and some live pages returned intermittent 404 errors, beginning at 1 PM (UTC timezone). The app fully stabilized after 2:30 PM (UTC). The issues occurred due to a heavier system load and our team is currently working on improvements to avoid similar situations in the future. We apologize if you were among the users that experienced this issue, and we thank you for your understanding!