Lexer Status
Real-time updates of Lexer issues and outages
Lexer status is Operational
Lexer Hub
Lexer Conversations
Lexer Integrations
You're checking on Lexer - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We're investigating an issue affecting Facebook connections for all customers. Since 27 Sep 17:23 AEST, Lexer hasn't been able to sync data with Facebook, and connected accounts may show a "token invalid" error.
We've identified the cause. It's a platform-level requirement on Lexer's connection to Meta, not a problem with your account, credentials or permissions, and your data is safe. We're working with Meta to restore access now.
Lexer Outage Survival Guide
Lexer Components
Lexer Hub
We're investigating an issue affecting Facebook connections for all customers. Since 27 Sep 17:23 AEST, Lexer hasn't been able to sync data with Facebook, and connected accounts may show a "token invalid" error.
We've identified the cause. It's a platform-level requirement on Lexer's connection to Meta, not a problem with your account, credentials or permissions, and your data is safe. We're working with Meta to restore access now.
Lexer Profiles
Lexer Conversations
We're investigating an issue affecting Facebook connections for all customers. Since 27 Sep 17:23 AEST, Lexer hasn't been able to sync data with Facebook, and connected accounts may show a "token invalid" error.
We've identified the cause. It's a platform-level requirement on Lexer's connection to Meta, not a problem with your account, credentials or permissions, and your data is safe. We're working with Meta to restore access now.
Lexer Integrations
We're investigating an issue affecting Facebook connections for all customers. Since 27 Sep 17:23 AEST, Lexer hasn't been able to sync data with Facebook, and connected accounts may show a "token invalid" error.
We've identified the cause. It's a platform-level requirement on Lexer's connection to Meta, not a problem with your account, credentials or permissions, and your data is safe. We're working with Meta to restore access now.