Is Instapage Down Right Now? Check if there is a current outage ongoing.

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.

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.

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 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.

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 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!

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 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.

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.

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.

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!

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.

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.

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

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.

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.

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.

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

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 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.

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

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

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.

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 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.

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 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 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 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.

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

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!

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.

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 issue seems to have been resolved and the application is stable and functional now.

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.

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!

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 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.

The incident has been resolved.

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.

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.

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!

Our team managed to implement a fix and both the application and live pages are currently working as expected. We want to apologize again for any inconvenience caused and let you know that we will continue monitoring the situation, to ensure that we can avoid any other similar issues in the future.

We are currently experiencing an outage at the application level and also intermittently for some of the live pages. We noticed the inconsistencies began around 14:00 (UTC timezone). Our entire team is already 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.

We had some problems with page serving flow. The cause was communication issues with the database which resulted in some pages having intermittent 404s. The issue started around 1 PM UTC - full stabilization around 8 PM; the worst moment being between 2:30 PM and 4 PM UTC. We're still analyzing logs. We already found many clues which can give us concrete implementation ideas to improve our system so that this won't happen again in the future. We apologize if you were among the users that experienced this issue, and we thank you for your understanding!

Our team managed to implement a fix and both the application and live pages are currently working as expected. We want to apologise again for any inconvenience caused and let you know that we will continue monitoring the situation, to ensure that we can avoid any other similar misbehaviour in the future.

Earlier today we experienced an outage at the application level and also for some of the live pages. The outage began at 14:00 (UTC timezone), lasted for 30 minutes and around 40% of the live page visits failed during this time. The incident has been resolved at that time, but we are noticing further issues related to the same components right now. Our entire 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 apologise for the inconvenience and we want to thank you for your patience while we resolve this.

We have monitored the application database, and it has fully recovered. The app was down for approximately five hours, between 2 AM and 7 AM UTC. No live pages should have been affected during this time.

A fix was implemented two hours ago, and we are in the monitoring phase. The app is working, but there can still occur some disruptions until the database fully recovers.

We are experiencing an outage, and the Application hasn't been running for a few hours. We identified the problem and we are working on a fix.

A CDN SSL certificate renewal process malfunction has caused assets such as images, videos, or scripts hosted on the g.fastcdn.co CDN server to not load as intended on Instapage landing pages. The issue began 2:32 PM (UTC time) and lasted for approximately 18 minutes. We apologize for any type of disruption this temporary malfunction may have caused and want to assure you that our engineers have already updated the CDN SSL certificate renewal process so that this kind of situation does not reoccur in the future.

We experienced an outage, and the application could not be accessed for a total of four hours due to a database error. Most of the pages were not affected by this incident, as they were cached on our servers, but some of them might have returned 404 status code for the time the app was down. We apologize and want to assure you that we will work even harder to ensure that roadblocks like these stop occurring in the future. Also, we are working on a permanent fix that will prevent such errors from appearing in our application in the future.

A fix has been applied by our engineers and the application and landing pages should now work as expected. We are really sorry about this unfortunate situation that has happened and we want to ensure you that we're looking into continuously improving our processes so that scenarios like these don't happen again in the future.

We are experiencing an outage at both the application and landing page server levels due to a problem that showed up during our database update. The issue began at 9:25 AM UTC, has been identified, and we are currently working on resolving it as soon as possible. Not all of the live landing pages are affected, however, we advise pausing any ongoing live ad campaigns until this is being resolved. Our team apologizes for any inconvenience this outage might've caused.

app.instapage.com experienced a partial outage last night and the application could not be accessed for a total of three hours. The outage was caused by a DNS error which was quickly identified by our engineering team and a fix was deployed. The initial fix was not propagating fast enough so our team has deployed a secondary solution which helped bring everything back to normal after four hours from the initial report. We want to apologize and assure you that our team is looking into what caused this outage and take the necessary measures to prevent it from happening again.

We can confirm that both the application and landing page servers are fully operational now and the issue has been completely resolved. We want to apologize and assure you that we will take any necessary measures to prevent this from happening again in the future.

Our application and landing page servers are currently experiencing an outage, but our team managed to identify and resolve the issue and we are now monitoring it. However, we recommend pausing any paid traffic to your landing pages until this is permanently resolved. Thank you for your patience and we apologize for the inconvenience.

The incident has been resolved and all systems are fully operational now. We apologise for the inconvenience and we will make sure to improve our systems and avoid these situations in the future. Thank you for your patience.

We are experiencing an outage at both the application and landing page servers levels. The issue has been identified and we are working on resolving it as soon as possible. We advise pausing paid traffic to your landing pages until this is permanently resolved. Thank you for your understanding.

Our team managed to resolve the incident. The application is stable and fully functional now, however, there might still be inconsistencies regarding the page Preview mode. We will keep monitoring the application and ensure that we eliminate any inconsistencies.

We've noticed the application is currently experiencing a heavier load balance and parts of the application may take longer to load or won't load at all. We have identified the root cause and are working on deploying a permanent fix, which will take effect shortly. Please note that no live pages or leads have been affected by this. Thank you for your understanding.

Our engineers have identified an error with our Lead Capturing system. There was a 50-minute downtime (4:45 AM - 5:35 AM UTC) in which leads were not entering the Leads Dashboard, nor were they captured anywhere on our platform. All of our systems are now fully operational and new leads are being correctly captured. We apologize for the inconvenience caused and we're working on implementing additional preventive measures to avoid such errors in the future.

Some live pages experienced a partial outage for 15 minutes, from 08:45 to 09:00 UTC due to an unforeseen security trigger. We apologize for any inconvenience this may have caused.

Due to Google Cloud's Networking Incident, we experienced an outage of approximately 15 minutes on 2019-06-02 between 19:45 - 19:58 UTC. For the following 4 hours, some pages might have experienced longer loading times than usual. The incident has been resolved and all systems are fully operational now.

The situation has been resolved and all affected pages are in the process of becoming fully operational. This may take an additional 30 minutes.

We are experiencing a partial outage of the application and live pages as well. We are working on fixing this as soon as possible but in the meantime, we recommend pausing ad traffic until this is completely resolved.

Server load is now stable and all pages are operational.

We are investigating an issue that is causing some pages that use Global Blocks to return an Internal 500 error. We advise pausing paid traffic to pages that have Global Blocks until this is resolved.

The incident was resolved approximately an hour ago. Our team is monitoring this part of the application and all pages should now function as expected. There might be a short delay before updates to global blocks display on the live page.

We are investigating an issue regarding the correct rendering of global blocks. We recommend pausing ad traffic that directs to pages where global blocks were used and we advise against creating new global blocks until this is resolved.

The queue has been cleared and leads are now arriving as expected.

We have noticed that a queue has been created on our servers, which is causing the email Lead Notifications, as well as the Leads sent to 3rd party CRMs to be delivered with a certain delay. Please rest assured, no leads have been lost, everything is being captured instantly in the Leads Dashboard. Our engineers are monitoring the situation as server load has already been lightened.

A segment of our users has been affected by one of our recent updates which caused some leads to not be displayed in their leads dashboard. Lead notifications and lead push to CRMs have not been affected, with all leads getting pushed to their respective integrations successfully. Our team is working on recovering the leads not displayed in the leads dashboard for the accounts which were affected.

After monitoring the fix released on Friday, we can confirm that the situation has been completely resolved and all SSL certificates are up-and-running. We apologize for the inconvenience and thank you for your patience!

The fix has been released and most of the SSL certificates will be active in 6 hours, though it might take up to 24 hours in some cases.

We are currently experiencing some issues with our SSL certificate provider and we cannot generate SSL certificates for newly added subdomains or reactivate expired certificates for existing ones. Please note that any page that is already secured won't be affected. In case you have ads running on a page with an expired certificate we recommend pausing your ads until the issue is fixed. Our engineers are working together with our SSL certificate provider and the situation will be fixed as soon as possible.

All systems are now operational. The incident in question was reported by Google here: https://status.cloud.google.com/incident/cloud-networking/18012

We are currently experiencing issues with Google, our cloud provider. The application and some pages might be affected and return a 502 Server Error.

Today any collected leads between 2:00 AM - 2:20 AM (PST) have not been sent via Zapier or Webhooks. These leads are not lost, since they were successfully collected inside our Leads Dashboard, so any leads from this timeframe can be manually exported into the corresponding CRM. We apologize for the inconvenience.

One of our servers (US-Central) for pageserver-cache (non-secured pages) experienced an outage of 30 minutes, between 20:50 - 21:20 UTC. The incident has been resolved and all systems are operational. We appreciate your understanding.

Today our lead collection system experienced intermittent outages for around 45 minutes, between 12:20 PM (UTC) and 1:20 PM (UTC), incident which led to some leads not being successfully captured. This has already been fixed and all our systems are currently operational. We will keep closely monitoring the incident and update this status if anything changes. We apologize for the inconvenience and thank you for your understanding!

Our systems are stabilizing, leads and notifications are being sent again. We highly appreciate your patience.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Some users may experience delayed lead deliveries, for both email notifications and integrated third party software solutions, however, no data will be lost. A queue is being created and all the leads will be delivered, shortly after. We will make sure to update you as soon as all the systems are operating at full capacity. Thank you for your understanding.

We have identified intermittent outages affecting the Leads dashboard and redirect function for users that have been migrated to our new submission system. Our engineers have deployed several fixes and our systems should now be stable. Additional safety measures have been taken in order to prevent future incidents. We will keep monitoring the platform to make sure everything is running smoothly. We appreciate your patience on this matter.

On the 4th of May the leads dashboard, submissions, and page re-direct systems experienced intermittent outages. All 3rd party integrations and lead notifications functioned normally, with the exception of Webhooks and Zapier. A fix has been applied and all systems are currently operational. We will keep closely monitoring the incident and update this status if anything changes. We thank you for your patience and understanding.

The third party email notification system used by Instapage has had delays over a period of a few hours on the morning of April 26th. This issue has been resolved and all email notifications that were in queue were delivered successfully. We apologize for the inconvenience and we are taking actions to prevent this from happening in the future.

Today our encryption system was disconnected from the network, issue which caused the dashboard leads to not be accessible for some users that were already migrated to the new submission system. Unfortunately, the leads that were collected between 10:47AM and 13:00AM (CET) might be missing and can't be recovered. If the forms were connected to a 3rd party CRM, the leads still went through. A relatively low number of users were affected by this incident. The system is now working smoothly and we are going to keep monitoring all operations. We apologize for the inconvenience caused and highly appreciate your understanding!

On March 14th between 10 PM and 3 AM PST our analytics system failed to collect stats on visitors and conversions. Traffic between those hours won't be recorded in your analytics dashboard, but leads were captured and pages were not affected.

The Dashboard is now fully operational and everything is back up and running. We apologize for the inconvenience this has caused!

Our engineers have identified a temporary outage for the dashboard and are working to deploy a fix as we speak. Live pages have not been affected.

We have identified a display error with the Analytics Dashboard. Only viewing statistics were temporarily paused, no data was affected by this. Within 10 minutes the dashboard view was fixed, everything is now operational.

We had a temporary server outage at 08.00 AM PST, which caused some pages to display a 404 error. The interruption was identified and fixed within 3 minutes.

This issue was resolved.

Our SSL certificate provider is experiencing intermittent issues which may cause some pages to become inaccessible while they are working on fixing the problem.