Identified - We are currently experiencing a delay in provisioning new LemonadeLXP instances due to an active bug in Cloudflare's UI affecting Enterprise accounts.
Impact -------
A bug in Cloudflare's management interface prevents Enterprise customers from converting zones from Free tier to the required security level through self-serve means. As a result, new instance provisioning — which depends on this zone conversion step — cannot be completed within our standard timeframes.
This issue does _not_ affect any existing LemonadeLXP instances or currently active customers.
Current Workaround --------------------
Cloudflare support is processing zone conversions manually on a per-ticket basis. Each zone must be submitted individually and actioned by Cloudflare's team. This introduces significant delays beyond our normal setup SLA.
Status -------
We are in active contact with Cloudflare and are monitoring for resolution. Updates will be provided as the situation develops.
Apr 09, 2026 - 10:11 EDT
LemonadeLXP Application Platform
Operational
90 days ago
100.0
% uptime
Today
AWS account
Operational
AWS acm-pca-us-east-1
Operational
AWS apigateway-us-east-1
Operational
AWS autoscaling-us-east-1
Operational
AWS backup-us-east-1
Operational
AWS detective-us-east-1
Operational
AWS dynamodb-us-east-1
Operational
AWS elasticache-us-east-1
Operational
AWS elb-us-east-1
Operational
AWS glacier-us-east-1
Operational
AWS guardduty-us-east-1
Operational
AWS imagebuilder-us-east-1
Operational
AWS inspector-us-east-1
Operational
AWS kms-us-east-1
Operational
AWS lambda-us-east-1
Operational
AWS polly-us-east-1
Operational
AWS rds-us-east-1
Operational
AWS sns-us-east-1
Operational
AWS sqs-us-east-1
Operational
AWS vpc-us-east-1
Operational
Cloudflare Access
Operational
Cloudflare Argo Smart Routing
Operational
Cloudflare Authoritative DNS
Operational
Cloudflare Bot Management
Operational
Cloudflare CDN/Cache
Operational
Cloudflare CDN Cache Purge
Operational
Cloudflare Challenge Platform
Operational
Cloudflare Dashboard
Partial Outage
Cloudflare DNS Root Servers
Operational
Cloudflare DNS Updates
Operational
Cloudflare Firewall
Operational
Cloudflare Image Resizing
Operational
Cloudflare Images
Operational
Cloudflare Infrastructure
Operational
Cloudflare Load Balancing and Monitoring
Operational
Resolved -
Cloudflare Error 1034 on corporate networks — static/outdated internal DNS configurations require update.
## How can you tell if you are affected?
Visiting your LemonadeLXP instance shows Cloudflare Error 1034 instead of the expected login, or play pages.
## Status: Identified
Users at a small number of customer organizations are receiving a Cloudflare "Error 1034 — Edge IP Restricted" page when accessing their LemonadeLXP environment from their corporate network on private DNS. Access from outside the corporate network is unaffected.
## Cause
Cloudflare validates that a requested hostname is authorized on the specific edge address the request arrives at. Configurations that previously resolved to Cloudflare addresses not allocated to the hostname are now rejected at Cloudflare's edge, before the request reaches our platform.
This change occurred on Cloudflare's network. No changes have been made to our platform, our Cloudflare configuration, or our origin infrastructure.
This only affects private DNS with static (now outdated) configurations. Public DNS resolution is 100% operational.
## Who is affected
Only organizations that have a manually configured internal DNS record — a split-brain or override entry — for their LemonadeLXP hostname pointing to a fixed Cloudflare address. These configurations functioned previously and stopped working without any change on the customer's part, which is why the failure appeared suddenly and only on the corporate network.
Organizations that implemented the NS delegation prescribed during onboarding are not affected and need take no action.
Public DNS resolution is correct and unaffected throughout. Access from outside the corporate network continues to work normally in all cases.
## Resolution
IMPORTANT: Please connect with your customer service representative to obtain your intended NS records ahead of implementing this correction.
The correction is to the internal DNS record within the affected organization's network. Remove any manual A or CNAME record and replace it with an NS delegation to the two Cloudflare nameservers assigned during onboarding, then clear the DNS cache on your domain controllers.
Our setup documentation specifies NS delegation — or CNAME, for organizations on our CNAME package — and does not support direct IP addressing for these hostnames.
Because this only affects misconfigured internal networks, we are unable to proactively reach out to at-risk configurations. If you get error 1034, the solution lies in correcting your internal DNS configuration only.
If on a nameserver setup (determined at onboarding), you should only have NS entries for your LemonadeLXP domain.
Aug 7, 13:03 EDT
Investigating -
We are currently investigating a Cloudflare routing issue that seems to be affecting some customers. When the issue occurs, Cloudflare presents random errors when trying to load a LemonadeLXP instance. Commonly, it will state "Edge IP Restricted". We are currently investigating the matter. This seems to be affecting corporate networks rather than personal ISPs.
Aug 7, 11:25 EDT