Respond.io Outage History

Started Oct 29, 2026, 02:30 PM UTC· resolved Oct 29, 2026, 04:29 PM UTC

1. identified Oct 29, 2026, 02:30 PM UTC

   We are currently investigating an issue affecting the WhatsApp channel. Messages sent from respond.io are not displaying a delivery status and are disappearing from the Inbox. We have not yet confirmed whether the affected messages are reaching recipients. Our engineering team is actively...

2. investigating Oct 29, 2026, 02:51 PM UTC

   Between 22:13 and 22:51 (GMT+8), messages sent through WhatsApp Business API channels were delayed by up to approximately 35 minutes, and in the Inbox they appeared to have disappeared. The delayed messages were delivered once the backlog cleared, and messages are now sending normally. The...

3. resolved Oct 29, 2026, 04:29 PM UTC

   The issue affecting WhatsApp channels has been fully resolved, and all messaging services are operating normally. Between 22:13 and 22:51 (GMT+8) on October 29, some outbound WhatsApp messages were delayed and may have briefly appeared as missing in the inbox. These messages were delivered...

Read the full incident report →

Started Oct 16, 2026, 01:12 PM UTC· resolved Oct 16, 2026, 01:12 PM UTC

1. resolved Oct 16, 2026, 01:12 PM UTC

   The issue affecting Conversations, Users, Responses and Resolutions reports has been resolved. Beginning October 16 at 13:12 UTC, a reporting issue caused these reports to show zero or missing results for recent activity. Conversation activity continued to be...

Read the full incident report →

Started Oct 09, 2026, 03:15 AM UTC· resolved Oct 09, 2026, 05:00 AM UTC

1. identified Oct 09, 2026, 03:15 AM UTC

   We are currently experiencing an issue affecting Broadcast scheduling. When attempting to schedule a Broadcast, the application may freeze and become unresponsive. Our team is actively investigating the situation. Some customers may experience disruptions when scheduling Broadcasts. ...

2. investigating Oct 09, 2026, 03:50 AM UTC

   Our Engineering team has deployed a hotfix to address the issue affecting Broadcast scheduling. We are currently monitoring the application to verify the effectiveness of the fix while continuing to investigate the underlying root cause. We will provide further updates as soon as...

3. investigating Oct 09, 2026, 04:15 AM UTC

   Our Engineering team has identified the root cause of the issue affecting Broadcast scheduling and successfully deployed a hotfix to the LIVE environment. The issue was caused by a recent update to the Broadcast scheduling date picker, which resulted in the application freezing when...

4. resolved Oct 09, 2026, 05:00 AM UTC

   The issue affecting Broadcast scheduling has been resolved, and the application is now functioning normally. Customers can proceed with scheduling their Broadcasts. If you continue to experience any issues, please perform a hard refresh of your browser. Thank you for your patience...

Read the full incident report →

Started Sep 29, 2026, 12:30 PM UTC· resolved Sep 29, 2026, 02:07 PM UTC

1. identified Sep 29, 2026, 12:30 PM UTC

   We are currently experiencing an issue affecting voice calls on Telnyx channels and WhatsApp calling. Some customers may be unable to place or receive calls, or may experience dropped calls or audio issues. This coincides with scheduled maintenance by Telnyx on their voice services across...

2. investigating Sep 29, 2026, 01:00 PM UTC

   We have identified that this issue is now affecting all voice calls on Telnyx channels and WhatsApp calls. You may currently be unable to place or receive calls. We have escalated this to Telnyx as a priority and are working with them to restore calling as quickly as possible. We sincerely...

3. resolved Sep 29, 2026, 02:07 PM UTC

   This issue has been resolved. Voice calls on Telnyx channels and WhatsApp calling have been working normally since 23:07 JST. Between 20:38 and 23:07 JST, calls routed through our Telnyx SIP connection were being rejected at the carrier level (SIP 403), which prevented calls from being...

Read the full incident report →

Started Sep 17, 2026, 05:39 PM UTC· resolved Sep 17, 2026, 09:11 PM UTC

1. identified Sep 17, 2026, 05:39 PM UTC

   We are currently investigating multiple reports of issues affecting AI Agents on the platform, including agents becoming unavailable or unresponsive, and published agents not appearing in the assignment list. Our team is actively investigating the situation. Some customers may experience...

2. investigating Sep 17, 2026, 07:10 PM UTC

   Our investigation has expanded in scope. In addition to the AI Agent issues reported earlier (agents becoming unavailable or unresponsive, published agents not appearing in the assignment list), we've identified that new user invitations to the platform are also affected, with invited users...

3. resolved Sep 17, 2026, 09:11 PM UTC

   This issue has been fully resolved. For approximately 2 hours 20 minutes, new sign-ups, team invitations, and AI Agent creation were failing across the platform. A fix was deployed and confirmed working as of 02:54 (MYT) on 18 September. Existing accounts, conversations, and messaging were...

Read the full incident report →

Started Sep 03, 2026, 01:30 AM UTC· resolved Sep 18, 2026, 05:00 AM UTC

1. identified Sep 03, 2026, 01:30 AM UTC

   We're aware that some customers received a notification indicating their WhatsApp Business Account (WABA) has been disabled. We're sorry for the confusion this may have caused. In many cases, this notification does not reflect the actual current status of your account and your channel...

2. investigating Sep 03, 2026, 04:00 AM UTC

   What we know: We've confirmed this is affecting a number of accounts, and we're working directly with Meta to determine the cause. If your WhatsApp channel is still sending and receiving messages normally, no action is needed. ...

3. resolved Sep 18, 2026, 05:00 AM UTC

   Meta has confirmed that the WhatsApp Business Account (WABA) disablement notifications observed between 01:30–06:00 MYT Sept 3rd were triggered by an internal platform change on Meta's side and were not the result of enforcement actions against the affected accounts</...

Read the full incident report →

Started Sep 02, 2026, 10:54 AM UTC· resolved Sep 03, 2026, 04:00 AM UTC

1. identified Sep 02, 2026, 10:54 AM UTC

   We're aware of an issue where some users are experiencing delays when navigating within the platform. This includes opening and switching between conversations, and sending messages taking longer than usual. The platform remains accessible and messages are still being sent and...

2. investigating Sep 02, 2026, 02:05 PM UTC

   Our team is actively investigating to identify the root cause of these delays. Not all users are affected, and the platform remains usable while we work on this. We will provide another update as soon as we have more information.

3. investigating Sep 02, 2026, 06:13 PM UTC

   We've identified the issue affecting some of our services and our team is actively working on a solution. We've rolled out fixes that have reduced the impact, and we're continuing to work toward a full resolution. We'll share another update as soon as we have more information.

4. resolved Sep 03, 2026, 04:00 AM UTC

   We are happy to report that the platform slowness issue has been resolved. Our engineering team deployed a hotfix to address the issue, and platform performance has returned to normal. We have been monitoring the platform following the deployment and have confirmed that it remains stable.</...

Read the full incident report →

Started Aug 29, 2026, 04:50 AM UTC· resolved Sep 16, 2026, 07:00 AM UTC

1. identified Aug 29, 2026, 04:50 AM UTC

   We're aware that users are experiencing errors when sending messages through the WhatsApp Cloud API, as well as when reconnecting a Cloud API channel. Affected messages return a Meta API error (#100). We apologize for the disruption this is causing. Our team is actively...

2. investigating Aug 29, 2026, 09:30 AM UTC

   We’re continuing to investigate intermittent issues affecting WhatsApp Cloud API channels. Error rates have decreased and remain low and scattered, with no further major spikes. However, some users may still encounter Meta API error (#100) when sending messages or reconnecting their...

3. investigating Aug 31, 2026, 08:40 AM UTC

   Following further investigation, we can confirm this is not an intermittent issue. Outbound messages on WhatsApp Cloud API channels are failing consistently rather than occasionally. Channels connected through respond.io's own BSP are not affected. The cause appears to be a loss of phone-...

4. investigating Sep 02, 2026, 07:05 AM UTC

   Update: We have identified an additional impact affecting incoming media attachments on WhatsApp Cloud API channels. Text messages continue to be received, but some incoming attachments, such as images or files, may fail to load in the respond.io Inbox and display the error <...

5. investigating Sep 09, 2026, 07:00 AM UTC

   Investigating Update: We’ve identified additional steps that may help restore affected WhatsApp Cloud API channels. If your channel is affected, please first grant respond.io access to your WhatsApp Business Account in Meta Business Manager...

6. resolved Sep 16, 2026, 07:00 AM UTC

   Incident Summary Beginning 29 August 2026, a number of WhatsApp Cloud API channels were unable to send outbound messages, returning a Meta API error (#100). The same issue also prevented incoming attachments, such as images and files, from loading in the respond.io Inbox,...

Read the full incident report →

Started Aug 19, 2026, 06:30 AM UTC· resolved Aug 19, 2026, 08:00 AM UTC

1. identified Aug 19, 2026, 06:30 AM UTC

   We are currently experiencing an issue where the “Close Conversation” step in Workflows is not closing conversations as expected. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the inconvenience and will provide an...

2. investigating Aug 19, 2026, 07:20 AM UTC

   Our engineering team has identified the root cause of the issue affecting the “Close Conversation” step in Workflows and AI Agent conversations. A mitigation has been applied, and conversations can now be closed as expected. Our engineering team is currently working on...

3. resolved Aug 19, 2026, 08:00 AM UTC

   We are happy to report that the issue affecting the “Close Conversation” step in Workflows has been resolved. Our engineering team has fully deployed the fix and verified that conversations are now closing as expected. We will continue to monitor the platform to ensure...

Read the full incident report →

Started Aug 13, 2026, 06:05 AM UTC· resolved Aug 13, 2026, 07:20 AM UTC

1. identified Aug 13, 2026, 06:05 AM UTC

   We’ve detected an issue causing the platform to be intermittently inaccessible, with some users seeing a “This site can’t be reached” error. Our team is investigating and working to restore stable access. We’ll share further updates as they become available.

2. investigating Aug 13, 2026, 07:00 AM UTC

   We have identified the issue as being related to the attachment spotlight feature. A fix has been validated and is currently being deployed. We are monitoring the deployment and will provide another update once the issue is fully resolved.

3. resolved Aug 13, 2026, 07:20 AM UTC

   This issue is now resolved. Between approximately 2:00 PM and 3:06 PM (+08:00), the platform was intermittently inaccessible, with some users being unexpectedly redirected to a "This site can't be reached" error page. The cause was traced to the attachment spotlight feature, and a fix...

Read the full incident report →

Started Aug 11, 2026, 05:40 AM UTC· resolved Aug 11, 2026, 07:20 AM UTC

1. identified Aug 11, 2026, 05:40 AM UTC

   We are currently experiencing an issue where outgoing messages from the respond.io Inbox are failing to send and displaying the error “Message not sent. Click to try again.” Our engineering team has been alerted and is actively investigating the root cause. We apologize...

2. investigating Aug 11, 2026, 05:50 AM UTC

   Our engineering team is actively investigating the issue affecting outgoing messages from the respond.io Inbox. We are working to identify the root cause of the message sending failures and restore normal functionality as soon as possible. We will continue to provide updates as more...

3. resolved Aug 11, 2026, 07:20 AM UTC

   We are happy to report that the issue affecting outgoing messages from the respond.io Inbox has been resolved. Our engineering team identified an infrastructure related issue that resulted in intermittent messaging service errors. The necessary adjustments have been made, and the platform...

Read the full incident report →

Started Aug 05, 2026, 05:30 AM UTC· resolved Aug 11, 2026, 08:10 AM UTC

1. identified Aug 05, 2026, 05:30 AM UTC

   We are currently experiencing an issue where browser notifications are not being delivered, despite browser notification settings being configured correctly. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the inconvenience and will...

2. investigating Aug 05, 2026, 05:35 AM UTC

   Our engineering team has identified the issue affecting browser notifications and is actively investigating the root cause. We are working to identify the cause of the disruption and restore normal browser notification delivery as quickly as possible. We will continue to provide...

3. investigating Aug 05, 2026, 07:00 AM UTC

   Our engineering team has identified the cause of the browser notification issue and is actively working on a fix. The issue is related to how the browser notification service initializes and resets under certain conditions, which can prevent notifications from being delivered as expected. ...

4. investigating Aug 05, 2026, 08:00 AM UTC

   Our engineering team has identified the cause of the browser notification issue and is actively working on a fix. We will provide another update as soon as more information becomes available.

5. resolved Aug 11, 2026, 08:10 AM UTC

   We are happy to report that the issue affecting browser push notifications has been resolved. Our engineering team deployed a hotfix to address the issue, and browser notifications are now being delivered as expected. The fix is continuing to propagate across all users, with related errors...

Read the full incident report →

Started Jul 29, 2026, 08:30 AM UTC· resolved Jul 29, 2026, 06:20 PM UTC

1. identified Jul 29, 2026, 08:30 AM UTC

   Workflow events and steps began to be delayed, with actions not appearing in real time. Actions were still being carried out, but with a delay of around 20 minutes.

2. investigating Jul 29, 2026, 04:35 PM UTC

   We have confirmed that this is affecting multiple workflows and multiple users, not an isolated case. Delays of up to 40 minutes have been observed between a workflow being triggered and its steps completing. Our team is continuing to investigate the cause.

3. investigating Jul 29, 2026, 04:42 PM UTC

   We have identified the cause. Workflows containing an "Add Google Sheet Row" step are being held at that step, which blocks every step that follows in the same workflow. This has created a backlog that is also delaying other workflows sharing the same processing capacity. Our...

4. resolved Jul 29, 2026, 06:20 PM UTC

   Incident Summary Between 5:30pm on 29 July and 1:20am on 30 July 2026 (+08:00), workflows containing an "Add Google Sheet Row" step were delayed. Because a workflow pauses at that step until it completes, all following steps were also held up, and the...

Read the full incident report →

Started Jul 27, 2026, 03:35 PM UTC· resolved Jul 27, 2026, 05:21 PM UTC

1. identified Jul 27, 2026, 03:35 PM UTC

   We are aware of an issue where delivery status indicators are not appearing on outbound WhatsApp messages. Incoming messages are being received as normal, and outbound messages appear to be sending, but no check marks are displayed in the Inbox. Our team is currently investigating and is awaiting...

2. investigating Jul 27, 2026, 04:05 PM UTC

   Following further checks, messages appear to be sent and delivered successfully. The issue seems to be limited to a delay in receiving delivery status updates from Meta, which is why check marks may appear late or not at all in the Inbox. Message delivery itself does not appear to be affected. <...

3. resolved Jul 27, 2026, 05:21 PM UTC

   The issue has been fully resolved. All messaging services are operating normally. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Started Jul 22, 2026, 01:55 PM UTC· resolved Jul 22, 2026, 04:40 PM UTC

1. identified Jul 22, 2026, 01:55 PM UTC

   We are currently experiencing intermittent delays and errors when sending messages through Meta channel (Facebook, Instagram, WhatsApp Business, and WhatsApp Cloud). This appears to be related to a broader issue on Meta's platform,...

2. investigating Jul 22, 2026, 02:35 PM UTC

   Update: We can now confirm that message delays are averaging 6–7 seconds, primarily affecting Instagram. All other details from our previous update remain unchanged we continue to monitor closely and are still awaiting confirmation from Meta.

3. investigating Jul 22, 2026, 03:55 PM UTC

   Update: We're seeing signs of recovery — Instagram response times have returned to normal, and intermittent errors on Facebook have significantly reduced. WhatsApp Business and WhatsApp Cloud have not been affected further. We're continuing to monitor closely to confirm full stability before...

4. resolved Jul 22, 2026, 04:40 PM UTC

   We are happy to report that the issue affecting message delivery across Meta channels has been resolved and services have returned to normal. The disruption was caused by instability on Meta's side, which resulted in slower responses and intermittent message delivery errors, particularly...

Read the full incident report →

Started Jul 20, 2026, 07:35 AM UTC· resolved Jul 20, 2026, 08:10 AM UTC

1. identified Jul 20, 2026, 07:35 AM UTC

   We are currently experiencing an issue where incoming messages from TikTok contacts are not appearing in the respond.io Inbox module, despite the TikTok channel being successfully connected. The same messages are still being successfully received in the TikTok app's direct inbox. Our...

2. investigating Jul 20, 2026, 07:42 AM UTC

   We have received confirmation from the TikTok partner team that they are currently investigating an issue involving missing webhooks, which is preventing incoming messages from being delivered to respond.io. We are closely monitoring the investigation and working with the TikTok partner...

3. resolved Jul 20, 2026, 08:10 AM UTC

   Incident Summary Starting around July 10, a temporary delay in TikTok’s backend authorization data synchronization caused webhook events to be blocked before delivery. The issue affected all TikTok webhook event types. Unfortunately, TikTok confirmed that the...

Read the full incident report →

Started Jul 19, 2026, 08:15 AM UTC· resolved Jul 19, 2026, 01:12 PM UTC

1. identified Jul 19, 2026, 08:15 AM UTC

   We are currently experiencing an issue affecting WhatsApp messages. Outbound messages may fail to be delivered due to the following Meta error: WhatsApp Business: Meta Error (#200): You do not have the necessary permission to send messages on behalf of this WhatsApp Business...

2. investigating Jul 19, 2026, 09:10 AM UTC

   Based on our preliminary analysis, the issue originates from Meta. Access to Meta Business is currently unavailable; we are awaiting confirmation from Meta Support.

3. investigating Jul 19, 2026, 09:30 AM UTC

   Access to Meta Business has been restored and outbound messages started working again; we are pending for confirmation from Meta Support.

4. investigating Jul 19, 2026, 10:00 AM UTC

   Outbound WhatsApp delivery has largely resumed. No change to your channel configuration is required. Please resend any affected messages.

5. resolved Jul 19, 2026, 01:12 PM UTC

   This incident has been resolved. Outbound WhatsApp messages were failing to deliver due to an upstream outage on Meta's Ads Delivery infrastructure. Meta has confirmed the issue is fixed and services have been restored on their end. We've verified that message delivery through our platform has...

Read the full incident report →

Started Jul 17, 2026, 07:15 AM UTC· resolved Jul 17, 2026, 08:15 AM UTC

1. identified Jul 17, 2026, 07:15 AM UTC

   We are currently experiencing an issue where our AI Agent is not replying to user messages in live conversations. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the inconvenience and will provide an update as soon as more information becomes...

2. investigating Jul 17, 2026, 07:20 AM UTC

   We are currently investigating an issue where our AI Agent is not replying to user messages in live conversations. Please note that messages are still being successfully received in the platform, and human agents are able to manually reply to contacts. We will provide another update...

3. investigating Jul 17, 2026, 07:40 AM UTC

   We have identified that requests to OpenAI are timing out, which is impacting AI Agent responses. Our engineering team is actively monitoring the situation and has prioritized a planned hotfix to improve the service while OpenAI resolves the issue. We will continue to provide...

4. resolved Jul 17, 2026, 08:15 AM UTC

   We are happy to report that AI Agent responses have been fully restored and are now operating normally. The issue was caused by requests to OpenAI timing out, which impacted AI Agent responses. The issue has since been resolved, and our engineering team has verified that AI Agents are...

Read the full incident report →

Started Jul 17, 2026, 07:00 AM UTC· resolved Aug 05, 2026, 09:00 AM UTC

1. identified Jul 17, 2026, 07:00 AM UTC

   We found an issue affecting our Voice Calls feature, with some inbound and outbound calls not connecting properly since July 17. Our team is looking into the cause.

2. investigating Jul 17, 2026, 10:00 AM UTC

   We have traced these call failures to an authentication issue with our upstream voice provider, Telnyx, rather than an issue within respond.io itself. We are in contact with their team to confirm the cause. Telnyx also has an ongoing issue on their side related to processing delays, which may be...

3. investigating Jul 26, 2026, 04:21 PM UTC

   The issue became more significant on July 26 between 4:21 PM and 6:55 PM UTC, when a higher volume of inbound and outbound calls failed to connect. We are working with Telnyx to identify the cause.

4. investigating Jul 27, 2026, 09:36 AM UTC

   Telnyx has confirmed that our account is active and in good standing, and was never suspended. They believe the failures may be linked to a processing delay on their platform that began July 16, which could have caused our account to be temporarily and incorrectly flagged. We are continuing to...

5. investigating Jul 27, 2026, 11:10 AM UTC

   Telnyx has escalated this internally to their engineering team for further investigation. We are waiting on their findings and will share another update as soon as we have more information.

6. resolved Aug 05, 2026, 09:00 AM UTC

   This issue is now resolved. Between 17 July and 5 August, intermittent authentication failures with our upstream voice provider caused some inbound and outbound calls not to connect, with the highest volumes on 26 July and 4 August. The failures were not caused by any suspension or...

Read the full incident report →

Started Jul 13, 2026, 07:10 AM UTC· resolved Jul 13, 2026, 10:12 AM UTC

1. identified Jul 13, 2026, 07:10 AM UTC

   We are currently experiencing an issue affecting N8N where there is delay performance in trigger and action. Our team is actively investigating the situation. Some customers may experience delayed performance with N8N. We will provide further updates as soon as more information...

2. investigating Jul 13, 2026, 08:00 AM UTC

   Our Engineering team has identified the root cause of the n8n delay affecting trigger and action performance. They are currently preparing a hotfix and working to expedite its release as quickly as possible. We will share another update as soon as more information becomes...

3. resolved Jul 13, 2026, 10:12 AM UTC

   This incident has been resolved. The issue was caused by communication failures with affected webhook endpoints, which resulted in some webhook requests being rejected. Webhook deliveries are now processing normally, and we will continue to monitor the service to ensure...

Read the full incident report →

Started Jul 09, 2026, 08:50 AM UTC· resolved Jul 09, 2026, 11:10 AM UTC

1. identified Jul 09, 2026, 08:50 AM UTC

   We are currently experiencing an issue affecting WhatsApp template messages. Outbound template messages with URL buttons may fail to be delivered due to the following Meta error: Meta Error #100: "Button at index 0 of type Url does not require parameters." <...

2. investigating Jul 09, 2026, 09:05 AM UTC

   Our Engineering team has identified the root cause of the issue affecting WhatsApp template messages with static URL buttons. A recent system change introduced for an incompatibility with Meta's template requirements, causing affected template messages to fail delivery....

3. resolved Jul 09, 2026, 11:10 AM UTC

   The incident has been resolved

Read the full incident report →

Started Jun 27, 2026, 01:07 PM UTC· resolved Jun 29, 2026, 12:00 PM UTC

1. identified Jun 27, 2026, 01:07 PM UTC

   We are currently experiencing an issue with the Instagram channel where sending file and image attachments is failing with an "Upload failed" error. This is a Meta-side issue affecting the Instagram Messaging API. We are actively monitoring Meta's status and will provide updates as the...

2. investigating Jun 27, 2026, 03:00 PM UTC

   We continue monitoring the situation and are awaiting official confirmation from the Meta engineering team. Please check Meta's status pages for real-time updates: Instagram: https://metastatus.com/ig-messenger We...

3. investigating Jun 29, 2026, 08:00 AM UTC

   Our engineering team has been actively investigating this issue and has identified a change in the Instagram Messaging API on Meta's side is causing file attachment uploads to fail. Our team ran a proof-of-concept and confirmed a working solution. We are now deploying a hotfix.</...

4. resolved Jun 29, 2026, 12:00 PM UTC

   The hotfix has been successfully deployed. File attachment sending via Instagram is now fully operational. If you still experience issues, please refresh your Instagram channel permissions by following these steps (this requires a respond.io Manager or Owner role and Meta...

Read the full incident report →

Started Jun 16, 2026, 08:30 AM UTC· resolved Jun 16, 2026, 11:00 AM UTC

1. identified Jun 16, 2026, 08:30 AM UTC

   We are currently investigating an issue affecting all Telegram Bots. Telegram Bots are unable to send or receive messages, returning the error: "An error occurred while sending the message." All other messaging channels are unaffected. Our...

2. investigating Jun 16, 2026, 10:00 AM UTC

   Telegram bots are now able to send and receive messages. We are continuing to monitor the situation and will confirm full resolution shortly.

3. resolved Jun 16, 2026, 11:00 AM UTC

   Telegram bot messaging has been fully resolved.

Read the full incident report →

Started Jun 12, 2026, 02:40 PM UTC· resolved Jun 12, 2026, 05:15 PM UTC

1. identified Jun 12, 2026, 02:40 PM UTC

   We are aware of an ongoing issue affecting Meta channels, including WhatsApp Business API (WABA), Instagram, Facebook, Marketing API and other services. This disruption is originating from Meta's platform and is impacting message delivery across these channels. This appears to be a...

2. investigating Jun 12, 2026, 04:00 PM UTC

   Some users are still experiencing intermittent issues with messaging services in WhatsApp, Instagram, and Messenger. We are actively monitoring the situation and are awaiting official confirmation from the Meta engineering team on full resolution. Please check Meta's status pages...

3. resolved Jun 12, 2026, 05:15 PM UTC

   We have confirmed that Meta has resolved the outage affecting WhatsApp, Instagram, and Messenger services. All messaging services are now fully operational. We appreciate our customers' patience and understanding during this time.

Read the full incident report →

Started Jun 05, 2026, 05:37 AM UTC· resolved Jun 05, 2026, 07:30 AM UTC

1. identified Jun 05, 2026, 05:37 AM UTC

   You may experiece issues when importing contacts via a CSV file start 1st June , where Contact creation may fail during the import process. If contacts may fail to be created, and please downloaded error file and it may display a due to "Server Error" . ...

2. investigating Jun 05, 2026, 05:38 AM UTC

   Our Engineering team is actively working on a fix. We will provide further updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

3. resolved Jun 05, 2026, 07:30 AM UTC

   Our engineers have implemented a fix to resolve the disruption affecting contact imports via CSV files. The issue has been successfully mitigated, and we are actively monitoring the system to ensure continued stability and uninterrupted service.

Read the full incident report →