Lexer Outage History
Lexer is up right nowPingoru has recorded 50 incidents for Lexer: 7 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 0 of 744 (0%) |
| September 2026 | 1 | 6 of 720 (1%) |
| October 2026 | 0 | 0 of 520 (0%) |
Incidents, newest first
Major September 27, 2026 Lexer Facebook integrations unavailable 6h 25m Hub, Conversations, Integrations
Started Sep 27, 2026, 09:30 PM UTC· resolved Sep 28, 2026, 03:55 AM UTC
- 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.
Notice August 22, 2026 Respond Inbox outage –
Started Aug 22, 2026, 12:00 AM UTC· resolved Aug 22, 2026, 12:00 AM UTC
- 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.
Critical February 13, 2026 Track metric and Activation processing delay 3h 42m Hub
Started Feb 13, 2026, 12:46 AM UTC· resolved Feb 13, 2026, 04:28 AM UTC
- investigating Feb 13, 2026, 12:46 AM UTC
We are currently investigating this issue.
- identified Feb 13, 2026, 01:16 AM UTC
The issue has been identified and a fix is being implemented.
- identified Feb 13, 2026, 01:27 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 13, 2026, 02:31 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 13, 2026, 04:28 AM UTC
This incident has been resolved.
Minor January 9, 2026 Activation performance degraded 3h 31m Hub
Started Jan 09, 2026, 06:11 AM UTC· resolved Jan 09, 2026, 09:42 AM UTC
- investigating Jan 09, 2026, 06:11 AM UTC
We're investigating an issue causing activation's to be pending for longer than usual.
- identified Jan 09, 2026, 06:23 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jan 09, 2026, 06:34 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jan 09, 2026, 09:42 AM UTC
This incident has been resolved.
Critical November 22, 2025 Hub not accessible 20h 32m Hub
Started Nov 22, 2025, 02:44 AM UTC· resolved Nov 22, 2025, 11:17 PM UTC
- investigating Nov 22, 2025, 02:44 AM UTC
We are experiencing an issue where users are unable to login into their Hub. We are working to address the underlying cause and minimizing impact.
- identified Nov 22, 2025, 02:55 AM UTC
We have identified the issue and are currently implementing a fix.
- monitoring Nov 22, 2025, 04:04 AM UTC
A fix has been implemented and we are monitoring. User should now be able to login into their hub.
- resolved Nov 22, 2025, 11:17 PM UTC
This issue is resolved.
Major November 21, 2025 Facebook mentions not discoverable 10d 11h Hub
Started Nov 21, 2025, 12:45 PM UTC· resolved Dec 02, 2025, 12:03 AM UTC
- identified Nov 22, 2025, 08:58 AM UTC
Meta, our Facebook mention provider in Respond is currently experiencing issues with their APIs which means that we are unable to match facebook mentions to dives. We have contacted Meta and are currently working on a solution to restore service for all Respond clients that currently have an integrated facebook account.
- identified Nov 22, 2025, 11:21 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 22, 2025, 11:22 PM UTC
The team has updated Respond clients saved dives to be able to more precisely target facebook mentions. We are still working with Meta for a resolution on this issue.
- identified Nov 24, 2025, 02:19 AM UTC
We are still working with Meta for a resolution on this issue. We will update this thread once we receive an update.
- identified Nov 25, 2025, 02:35 AM UTC
We are continuing to work with Meta for a fix on this issue.
- monitoring Dec 01, 2025, 01:11 AM UTC
Meta acknowledged the issue and pushed a fix this morning. The team is currently monitoring.
- resolved Dec 02, 2025, 12:03 AM UTC
This incident has been resolved.
Minor October 29, 2025 Meta API Issues Affecting Facebook Connections 1h 46m Conversations, Integrations
Started Oct 29, 2025, 03:24 AM UTC· resolved Oct 29, 2025, 05:10 AM UTC
- investigating Oct 29, 2025, 03:24 AM UTC
Lexer has detected an elevated number of errors from Meta’s API impacting Facebook Pages and Business Accounts. This issue is currently affecting Lexer’s Respond and Activate products. As a result, you may experience: • Account disconnections (including email alerts) • Errors when syncing audiences • Errors when publishing replies to messages This issue originates within Meta’s systems and cannot be resolved by Lexer. We are actively monitoring the situation and will provide updates as more information becomes available from Meta.
- resolved Oct 29, 2025, 05:10 AM UTC
Meta’s API errors impacting Facebook Pages and Business Accounts have now been resolved. Affected accounts have reconnected successfully, and normal functionality has resumed across Lexer’s Respond and Activate products. We’ll continue to monitor performance, but no further impact is expected.
Minor August 19, 2025 Hub.lexer.io - service disruption 6h 45m Hub
Started Aug 19, 2025, 11:30 PM UTC· resolved Aug 20, 2025, 06:16 AM UTC
- investigating Aug 20, 2025, 12:09 AM UTC
We’re investigating an issue causing degraded performance on hub.lexer.io. The service has automatically recovered, and we’re continuing to monitor stability.
- investigating Aug 20, 2025, 12:09 AM UTC
We are continuing to investigate this issue.
- monitoring Aug 20, 2025, 12:19 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 20, 2025, 02:50 AM UTC
We are continuing to monitor for any further issues.
- resolved Aug 20, 2025, 06:16 AM UTC
This incident has been resolved.
Notice May 27, 2025 File Upload API and Secure File Upload Outage 3h
Started May 27, 2025, 10:00 PM UTC· resolved May 28, 2025, 01:00 AM UTC
- resolved Jun 03, 2025, 01:30 AM UTC
Partial service outage affecting file uploads 28 May 2025 08:00 AEST – 3 June 2025 11:00 AEST Between 08:00 AEST on 28 May 2025 and 11:00 AEST on 3 June 2025, Lexer experienced an outage affecting two upload methods: the File Upload API and the Secure File Upload (drag and drop) feature. During this period, all file upload attempts via these channels failed. If you attempted to upload files between 28 May and 3 June via the affected methods, please reupload them to ensure they are processed. The issue was resolved as of 11:00 AEST on 3 June 2025. File uploads are now functioning as expected. We apologise for the disruption and appreciate your understanding.
Major February 17, 2025 Hub.lexer.io performance degraded 1d 5h Hub
Started Feb 17, 2025, 11:43 PM UTC· resolved Feb 19, 2025, 05:24 AM UTC
- investigating Feb 17, 2025, 11:43 PM UTC
We're investigating reports of degraded performance for hub.lexer.io.
- investigating Feb 17, 2025, 11:43 PM UTC
We are continuing to investigate this issue.
- identified Feb 17, 2025, 11:55 PM UTC
We are experiencing a high rate of search timeout errors when loading conversations in Listen and Respond. Our team is continuing to investigate the root cause.
- identified Feb 18, 2025, 02:28 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Feb 18, 2025, 04:57 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 19, 2025, 05:24 AM UTC
This incident has been resolved.