Is Lexer down?
Last checked 4m agoNo incidents right now.
Lexer is operational right now. Last checked 4m ago; the most recent incident resolved 34d ago.
Real-time Lexer status, recent outages, and incident history: pulled directly from Lexer's official status page at status.lexer.io every 5 minutes. Pingoru tracks 4 Lexer services and has captured 2 incidents in the last 90 days (97.78% uptime). Get email, Slack, Discord, or webhook alerts the moment Lexer reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- HubConversationsIntegrations
Timeline · 2 updates
- identified · Sep 27, 2026, 09:30 PM UTC
We're investigating an issue affecting Facebook connections for all customers. Since early on 28 September (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.
- resolved · Sep 28, 2026, 03:55 AM UTC
Facebook integrations have been restored and are syncing again. Between AEST 5:23pm on 27 Sep and 9:49am on 28 Sep, Lexer couldn't sync data with Facebook and Instagram because of a platform requirement on Lexer's connection to Meta. The issue has been resolved with Meta, and your accounts, credentials and data were not affected. Any audience activations that were paused during the incident have been re-enabled, and missed syncs will catch up over the next few hours. You don't need to do anything. If a Facebook or Instagram connection still shows an error, please contact our support team. We apologise for the disruption.
Latest: Facebook integrations have been restored and are syncing again. Between AEST 5:23pm on 27 Sep and 9:49am on 28 Sep, Lexer couldn't sync data with Facebook and Instagram because of …
-
-
Timeline · 1 update
- resolved · Sep 08, 2026, 11:53 PM UTC
The Respond Inbox was unavailable from around 10am on Saturday 22 August to approximately 10:45am on Monday 24 August 2026. During this period, messages across all sources did not load or appear in Inbox search, so agents were unable to view or reply to customer conversations. The issue was triggered by scheduled maintenance on our cloud infrastructure, after which part of the system that connects stored messages to the Inbox did not come back online. Incoming messages continued to be received and stored safely throughout the outage, and no message data was lost. All messages were available in the Inbox once service was restored. We recognise the disruption was extended by the time it took us to detect the issue over the weekend. Restoring service took under an hour once our engineering team was engaged; the gap was in identifying the problem sooner. We are strengthening our proactive monitoring and out-of-hours escalation so an issue of this kind is caught and resolved quickly in future.
Latest: The Respond Inbox was unavailable from around 10am on Saturday 22 August to approximately 10:45am on Monday 24 August 2026. During this period, messages across all sources did not …
-
Incident record
Since April 2026 · Statuspage by Atlassian · 4 components checked every 5 minutesThe longest incident in the last year, Facebook mentions not discoverable on November 21, 2025, ran for 10 days.
Most affected components, last 12 months
- Hub5
- Conversations1
- Integrations1
Latest incidents
- Lexer Facebook integrations unavailable
We're investigating an issue affecting Facebook connections for all customers. Since early on 28 September (AEST), Lexer hasn't been able to sync data with…
- Respond Inbox outage
The Respond Inbox was unavailable from around 10am on Saturday 22 August to approximately 10:45am on Monday 24 August 2026. During this period, messages across…
- Track metric and Activation processing delay
We are currently investigating this issue.
- Started Sep 27, 2026, 09:30 PM UTC · Resolved Sep 28, 2026, 03:55 AM UTC · 6h 25m
- Respond Inbox outage ResolvedStarted Aug 22, 2026, 12:00 AM UTC · Resolved Aug 22, 2026, 12:00 AM UTC · –