Instapage Outage History

Instapage is up right now

Pingoru has recorded 50 incidents for Instapage: 3 in the last 12 months and 0 in the last 90 days.

Source: status.instapage.com

50incidents recorded
3last 12 months
0last 90 days
35 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Instapage in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 524 (0%)

Incidents, newest first

Major February 23, 2026 Salesforce Integration issue 4d 2h Application (app.instapage.com)

Started Feb 23, 2026, 08:37 AM UTC· resolved Feb 27, 2026, 11:04 AM UTC

  1. identified Feb 23, 2026, 08:37 AM UTC

    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.

  2. monitoring Feb 24, 2026, 07:48 AM UTC

    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.

  3. resolved Feb 27, 2026, 11:04 AM UTC

    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.

Read the full incident report →

Minor January 19, 2026 Delay in Landing Page Publishing Flow 7h 20m pageserve.co, Application (app.instapage.com), pagedemo.co, Landing Page Servers

Started Jan 19, 2026, 02:56 PM UTC· resolved Jan 19, 2026, 10:17 PM UTC

  1. investigating Jan 19, 2026, 02:56 PM UTC

    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.

  2. investigating Jan 19, 2026, 08:20 PM UTC

    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.

  3. resolved Jan 19, 2026, 10:17 PM UTC

    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!

Read the full incident report →

Critical December 5, 2025 Instapage app and landing pages affected by Cloudflare API service issues 20m Website & Blog (instapage.com), pageserve.co, Cloudflare Authoritative DNS, Application (app.instapage.com) and 4 more

Started Dec 05, 2025, 09:06 AM UTC· resolved Dec 05, 2025, 09:26 AM UTC

  1. identified Dec 05, 2025, 09:06 AM UTC

    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.

  2. monitoring Dec 05, 2025, 09:17 AM UTC

    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.

  3. resolved Dec 05, 2025, 09:26 AM UTC

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

Read the full incident report →

Major June 12, 2025 Application and some pages are down because of Google's services global outage 1h 11m pageserve.co, Application (app.instapage.com), pagedemo.co, Cloudflare Network and 3 more

Started Jun 12, 2025, 08:00 PM UTC· resolved Jun 12, 2025, 09:11 PM UTC

  1. investigating Jun 12, 2025, 08:00 PM UTC

    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.

  2. monitoring Jun 12, 2025, 08:28 PM UTC

    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.

  3. resolved Jun 12, 2025, 09:11 PM UTC

    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.

Read the full incident report →