Convoso Outage History

Convoso is up right now

Convoso had 42 outages in the last 2 years totaling 240h 32m of downtime — averaging 1.7 incidents per month.

There were 42 Convoso outages since June 5, 2024 totaling 240h 32m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.convoso.com

Minor May 19, 2026

High Wait Times

Detected by Pingoru
May 19, 2026, 03:19 PM UTC
Resolved
May 19, 2026, 06:42 PM UTC
Duration
3h 23m
Affected: Dialer
Timeline · 4 updates
  1. investigating May 19, 2026, 04:33 PM UTC

    We are currently investigating reports of high agent wait times. Engineering teams are engaged as a priority event. More updates wil be provided as the investigation progresses.

  2. identified May 19, 2026, 04:48 PM UTC

    The issue has been identified, and remediation efforts are already underway.

  3. identified May 19, 2026, 06:47 PM UTC

    The backend work to resolve this issue is almost complete, and many clients will already have seen an improvement in agent wait times. We will confirm once it is fully resolved.

  4. resolved May 19, 2026, 08:51 PM UTC

    We're pleased to report that this issue is resolved. No further impact is expected. Convoso would like to take this opportunity to apologize for the degraded service and advise that we continue to closely monitor this for continued stability. Clients who submitted a Support ticket will be sent an RFO in due course.

Read the full incident report →

Notice May 1, 2026

Our support phone line is undergoing maintenance

Detected by Pingoru
May 01, 2026, 02:52 PM UTC
Resolved
May 01, 2026, 03:25 PM UTC
Duration
33m
Timeline · 2 updates
  1. identified May 01, 2026, 02:52 PM UTC

    Our support phone line is currently down due to emergency maintenance. Our team is ready to assist via email and chat. We apologize for the inconvenience and we will close this out once the maintenance is complete.

  2. resolved May 01, 2026, 03:25 PM UTC

    Our support phone line is once again available, we appreciate your patience as we worked to correct this.

Read the full incident report →

Minor May 1, 2026

Inbound calls to select DIDs may be experiencing routing issues

Detected by Pingoru
May 01, 2026, 01:39 PM UTC
Resolved
May 01, 2026, 05:15 PM UTC
Duration
3h 35m
Affected: Dialer
Timeline · 3 updates
  1. identified May 01, 2026, 03:29 PM UTC

    Our team has identified an issue where a small collection of DIDs may experience inbound calls not properly routing. This is being handled as a Priority 1 Issue and we are actively correcting this across all affected accounts. We apologize for any impact this may cause and will provide updates as work progresses.

  2. identified May 01, 2026, 04:27 PM UTC

    Our team continues work to urgently resolve routing issues with the subset of impacted DIDs, with many already corrected.

  3. resolved May 01, 2026, 05:20 PM UTC

    As of 10:15 AM PST, work has completed to resolve any remaining routing issues. We are monitoring to validate this resolution. We apologize for any impacts this may have had operations and appreciate your patience as we worked to correct this. Customers who reported impact to our Support team will receive an RFO once internal investigations have concluded.

Read the full incident report →

Minor April 29, 2026

Customers may experience audio degradation

Detected by Pingoru
Apr 29, 2026, 03:52 PM UTC
Resolved
Apr 30, 2026, 03:03 PM UTC
Duration
23h 11m
Affected: Dialer
Timeline · 4 updates
  1. investigating Apr 29, 2026, 04:36 PM UTC

    We are currently urgently investigating reports of intermittent audio degradation audio while on calls. This is being treated as a Priority 1 incident and work is ongoing to resolve.

  2. investigating Apr 29, 2026, 06:56 PM UTC

    Our investigation and examination remains ongoing, and we are still treating this as a priority event, and have engaged several external partners in addition to our own Engineering and Carrier teams.

  3. monitoring Apr 29, 2026, 11:45 PM UTC

    We continue to monitor this issue and are working closely with our providers and carriers. There have been no fresh reports submitted for multiple hours at this point. We are not yet ready to state this as resolved however, until a longer monitoring phase has been completed.

  4. resolved Apr 30, 2026, 03:03 PM UTC

    After appropriate monitoring and morning checks, we are satisfied that this issue has now been resolved. There will be an RFO issued to reporting clients in due course. Thank you for your patience as this issue was worked through.

Read the full incident report →

Minor April 15, 2026

Registration and transfer Call issue

Detected by Pingoru
Apr 15, 2026, 12:18 PM UTC
Resolved
Apr 15, 2026, 03:35 PM UTC
Duration
3h 17m
Affected: Dialer
Timeline · 4 updates
  1. investigating Apr 15, 2026, 01:55 PM UTC

    We are currently aware of an issue affecting a subset of clients related to Registration errors and transferring calls. Our Engineering team is engaged, and we are treating this issue as a Priority. Updates to follow.

  2. monitoring Apr 15, 2026, 02:13 PM UTC

    We have identified the root cause and have corrected the issue. We are currently monitoring to ensure the resolution is complete and stable.

  3. identified Apr 15, 2026, 03:06 PM UTC

    We have reverted the stage as we have identified an additional instance of the concern, which we are investigating as a priority.

  4. resolved Apr 15, 2026, 03:47 PM UTC

    The issue has been fully resolved and the fix is confirmed stable. RFO will be issued in due course to impacted clients.

Read the full incident report →

Minor March 2, 2026

Slow/Unresponsive Agent Monitor

Detected by Pingoru
Mar 02, 2026, 04:59 PM UTC
Resolved
Mar 02, 2026, 07:08 PM UTC
Duration
2h 9m
Affected: Campaigns and Hopper
Timeline · 3 updates
  1. investigating Mar 02, 2026, 05:23 PM UTC

    We have received reports of Agent Monitor being slow to load and/or not loading at all. This is under active investigation as a priority issue. Updates will be posted once available.

  2. monitoring Mar 02, 2026, 06:08 PM UTC

    We have isolated the issue and made adjustments to resolve this. We are currently monitoring closely to ensure platform stability and responsiveness.

  3. resolved Mar 02, 2026, 07:42 PM UTC

    After a period of intensive monitoring, we are satisfied that this incident is resolved and our platform is operating as expected. We appreciate your patience while we investigated and resolved this. Customers who reported an impact with our Support team will receive an RFO once the investigation is complete.

Read the full incident report →

Minor March 2, 2026

AWS Route 53 Degraded Performance

Detected by Pingoru
Mar 02, 2026, 04:50 PM UTC
Resolved
Mar 03, 2026, 12:12 AM UTC
Duration
7h 22m
Affected: AWS route53
Timeline · 2 updates
  1. monitoring Mar 02, 2026, 04:50 PM UTC

    We are closely monitoring reports of Degraded Performance with Amazon AWS Route 53 services. At this time we are not seeing any impacts to the Convoso platform.

  2. resolved Mar 03, 2026, 12:12 AM UTC

    At this time Amazon has indicated issues with AWS Route 53 are resolved. Convoso did not see impacts from this external issue.

Read the full incident report →

Minor February 27, 2026

Call Connection Delays

Detected by Pingoru
Feb 27, 2026, 02:09 PM UTC
Resolved
Feb 27, 2026, 03:07 PM UTC
Duration
58m
Affected: Dialer
Timeline · 3 updates
  1. investigating Feb 27, 2026, 02:38 PM UTC

    We are currently investigating reports of delays with call connections, treating this as a priority issue, and have engaged our engineering resources. We will provide updates as they become available.

  2. monitoring Feb 27, 2026, 03:07 PM UTC

    We have identified and corrected an issue and are actively monitoring for stability, and are seeing wait times for calls connecting return to normal levels.

  3. resolved Feb 27, 2026, 03:30 PM UTC

    At this time, we have confirmed resolution and restoration of normal call handling. We appreciate your patience as we worked urgently to resolve this issue. Customers who reported impact to our Support team will receive an RFO as soon as internal investigations conclude.

Read the full incident report →

Minor February 20, 2026

Intermitted Platform Disconnects

Detected by Pingoru
Feb 20, 2026, 06:07 PM UTC
Resolved
Feb 20, 2026, 06:40 PM UTC
Duration
32m
Affected: DialerCampaigns and HopperScriptsAPIWorkflow AutomationLeadsReports and Dashboards
Timeline · 3 updates
  1. identified Feb 20, 2026, 06:26 PM UTC

    We have identified intermittent platform disconnects impacting our customers. We have escalated this internally and are treating this as a Priority 1 issue.

  2. monitoring Feb 20, 2026, 06:30 PM UTC

    We have identified an external network issue and have deployed a fix to avoid this provider. We are monitoring closely to validate full resolution. This issue is impacting other providers and is not specific to Convoso.

  3. resolved Feb 20, 2026, 06:40 PM UTC

    At this time, we have confirmed that the adjustments made to bypass the affected external provider have restored stable connectivity for our customers. We appreciate your patience while we implemented this solution. Customers who reported impact to our Support team will receive a RFO once the investigation is complete.

Read the full incident report →

Minor February 19, 2026

Increased Congestion Dispositions

Detected by Pingoru
Feb 19, 2026, 03:26 PM UTC
Resolved
Feb 19, 2026, 05:59 PM UTC
Duration
2h 33m
Affected: Dialer
Timeline · 3 updates
  1. investigating Feb 19, 2026, 04:42 PM UTC

    We have identified a rise in congestion status calls. We are urgently investigating this as a Priority 1 issue at this time and will provide updates as work progresses.

  2. monitoring Feb 19, 2026, 05:13 PM UTC

    A fix has been deployed and we are closely monitoring to validate resolution.

  3. resolved Feb 19, 2026, 05:59 PM UTC

    At this time, we have confirmed resolution and restoration of normal call handling. We appreciate your patience as we worked urgently to resolve this issue. Customers who reported impact to our support team will receive an RFO as soon as internal investigations conclude.

Read the full incident report →

Notice January 31, 2026

Investigation into Isolated Increases in CG Responses

Detected by Pingoru
Jan 31, 2026, 12:11 AM UTC
Resolved
Feb 05, 2026, 01:38 AM UTC
Duration
5d 1h
Affected: Dialer
Timeline · 2 updates
  1. investigating Jan 31, 2026, 12:11 AM UTC

    We have completed our investigation into an increase in CG status calls observed by some customers. This behavior appears to be isolated in nature and is related to the deployment of spam blocking applications by endpoint carriers. Impact to customers is not widespread. We are running additional analytics and will reach out directly to affected customers to discuss next steps.

  2. resolved Feb 05, 2026, 01:38 AM UTC

    As our investigations have concluded, we will close this alert at this time.

Read the full incident report →

Minor November 24, 2025

Issue with Report Data Exports

Detected by Pingoru
Nov 24, 2025, 02:39 PM UTC
Resolved
Nov 24, 2025, 04:01 PM UTC
Duration
1h 22m
Affected: Reports and Dashboards
Timeline · 3 updates
  1. investigating Nov 24, 2025, 02:32 PM UTC

    We have received reports of data exports returning with zero bytes of data. We are investigating.

  2. monitoring Nov 24, 2025, 02:48 PM UTC

    A fix has been implemented and our team is closely monitoring to verify full resolution.

  3. resolved Nov 24, 2025, 04:01 PM UTC

    After an extensive review, we have confirmed no further impact as of 6:39 AM PST. Thank you for your understanding.

Read the full incident report →

Major October 23, 2025

Call handling delays

Detected by Pingoru
Oct 23, 2025, 08:41 PM UTC
Resolved
Oct 23, 2025, 09:48 PM UTC
Duration
1h 7m
Affected: Dialer
Timeline · 3 updates
  1. identified Oct 23, 2025, 09:19 PM UTC

    Our team is urgently working to resolve an issue that may cause delays to call handling. We have identified the source of the trouble and are working to restore service levels. This is a priority 1 issue.

  2. monitoring Oct 23, 2025, 09:36 PM UTC

    Our team has implemented a fix and are we are closely monitoring to validate full resolution.

  3. resolved Oct 23, 2025, 09:48 PM UTC

    At this time we have validated resolution internally and customers should no longer see delays with call handling. We apologize for the impact this may have had on your operations and we appreciate your patience as we worked urgently to resolve this. Customers who reported impact to our support team will receive an RFO once it is completed.

Read the full incident report →

Notice October 13, 2025

Support and Billing emails sent between 1:25 AM - 7:45 AM PST may have not reached our team.

Detected by Pingoru
Oct 13, 2025, 06:13 PM UTC
Resolved
Oct 13, 2025, 06:13 PM UTC
Duration
Affected: Billing
Timeline · 1 update
  1. resolved Oct 13, 2025, 06:13 PM UTC

    Due to an outage with our ticketing provider, emails to our Support and Billing teams may not have properly created a ticket for us to assist you. We apologize for any inconvenience this may have caused. If you reached out to our team and did not get a reply or a ticket number, please create a new ticket or forward your old one to our team and we'll assist you as soon as possible. Once again we apologize for any delays in assistance and we're here to help.

Read the full incident report →

Minor September 29, 2025

Mobile numbers may show as Landline

Detected by Pingoru
Sep 29, 2025, 06:32 PM UTC
Resolved
Oct 01, 2025, 05:53 PM UTC
Duration
1d 23h
Affected: Leads
Timeline · 4 updates
  1. identified Sep 29, 2025, 06:32 PM UTC

    We have identified an issue with phone type detection for Leads (Landline, Mobile, etc). A fix has been applied, so new Leads will have the correct data. We are working urgently to correct the data for existing Leads. Customers may not be able to send SMS to affected leads until the Lead is corrected.

  2. identified Sep 29, 2025, 11:10 PM UTC

    Our team continues work to adjust the phone type of existing Leads back to their correct value. We will continue working on this throughout the night and we aim to have this resolved as soon as possible. As a reminder, new Leads will be inserted with the correct phone type.

  3. identified Sep 30, 2025, 04:28 PM UTC

    We continue to correct existing lead data, primarily overnight, to reduce impact to operations.

  4. resolved Oct 01, 2025, 05:53 PM UTC

    At this time, the data correction should be complete. We will be sending an RFO to customers who reported impact to our support team as soon as possible. We appreciate your patience as we worked to fix and then correct the data related to this issue, and we apologize for any impact this may have had on your operations.

Read the full incident report →

Minor September 26, 2025

Users may experience trouble logging in

Detected by Pingoru
Sep 26, 2025, 02:06 PM UTC
Resolved
Sep 26, 2025, 04:50 PM UTC
Duration
2h 44m
Affected: DialerReports and Dashboards
Timeline · 6 updates
  1. investigating Sep 26, 2025, 03:02 PM UTC

    We are currently investigating reports of issues logging into the platform. We are treating this as a P1 event.

  2. investigating Sep 26, 2025, 03:27 PM UTC

    We have our engineering team actively engaged on resolving this issue.

  3. identified Sep 26, 2025, 03:57 PM UTC

    Our team is actively deploying a fix for users who may be unable to login at this time. We apologize for any impact this may have on your operations as we work urgently to resolve.

  4. identified Sep 26, 2025, 04:00 PM UTC

    We are continuing to work on a fix for this issue.

  5. monitoring Sep 26, 2025, 04:48 PM UTC

    A fix has been fully deployed and users should see little to no further impact as they log in. We are actively monitoring this issue closely to verify full resolution.

  6. resolved Sep 26, 2025, 05:24 PM UTC

    Our team has confirmed full resolution of login issues as of 9:50 AM PST. Customers who reported impact to our Support Team will receive an RFO as soon as internal work concludes. We apologize for any impact this may have had on your operations and appreciate your patience as we worked to resolve this issue.

Read the full incident report →

Minor September 12, 2025

Intermittent Dialing Pauses

Detected by Pingoru
Sep 12, 2025, 04:38 PM UTC
Resolved
Sep 12, 2025, 05:08 PM UTC
Duration
30m
Affected: Dialer
Timeline · 2 updates
  1. monitoring Sep 12, 2025, 05:13 PM UTC

    We have identified intermittent pausing and delays in dialing and immediately raised this as Priority 1 issue. The root cause has been identified and a fix has been applied. We are monitoring closely to confirm full resolution.

  2. resolved Sep 12, 2025, 05:27 PM UTC

    A fix was deployed at 10:08 AM PST, and we have confirmed no further impact at this time. Customers who reported impact to Support will receive an RFO as soon it is completed. We appreciate your patience as we worked to resolve this issue and we apologize for any impact this may have had on your operations.

Read the full incident report →

Notice July 25, 2025

Backbone Provider Network Issue

Detected by Pingoru
Jul 25, 2025, 08:00 PM UTC
Resolved
Jul 25, 2025, 09:26 PM UTC
Duration
1h 25m
Timeline · 3 updates
  1. monitoring Jul 25, 2025, 08:20 PM UTC

    Convoso has identified interconnects between major US network providers appear to have major packet loss. This will impact your ability to connect to Convoso, among other service providers. We are closely monitoring this situation.

  2. monitoring Jul 25, 2025, 08:20 PM UTC

    We are continuing to monitor for any further issues.

  3. resolved Jul 25, 2025, 09:26 PM UTC

    We’ve identified that intermittent connectivity issues reported by some customers are the result of packet loss occurring across certain internet service providers. Our systems remain fully operational. However, due to the streaming protocols used by our platform, degraded ISP routes may continue to impact performance, even when other internet-based services appear unaffected. If you are still experiencing connectivity issues, we recommend contacting your internet service provider. You can also use WinMTR (https://help.convoso.com/hc/en-us/articles/218732368-Checking-for-Quality-of-Service-issues-with-WinMTR-Windows-OS) to verify that your connection to Convoso is stable. As this issue is external to our platform and infrastructure, we are closing this notice at this time. We appreciate your patience as we investigated this concern.

Read the full incident report →

Minor May 14, 2025

Some customers may be experiencing trouble logging in to Convoso

Detected by Pingoru
May 14, 2025, 05:03 PM UTC
Resolved
May 14, 2025, 05:03 PM UTC
Duration
Affected: DialerScriptsReports and Dashboards
Timeline · 3 updates
  1. identified May 14, 2025, 04:52 PM UTC

    We have identified an issue where a small subset of customers may be experiencing trouble logging into Convoso at this time. While this issue is very isolated we are treating it as a Priority 1 incident and we are working urgently to resolve this. If you are experience impact, please reach out to our Support team.

  2. monitoring May 14, 2025, 04:57 PM UTC

    A fix has been applied and we are working to verify full resolution at this time. If you experienced trouble logging in earlier, please try once again at this time.

  3. resolved May 14, 2025, 05:06 PM UTC

    At this time customers should no longer be experiencing trouble logging in related to this issue. Customers who reported impact will receive an RFO as soon as it is available. We appreciate your patience as we worked to resolve this issue and apologize for any impact it may have had on your operations.

Read the full incident report →

Notice May 1, 2025

Customers may have trouble reaching our Support Team via Phone

Detected by Pingoru
May 01, 2025, 06:39 PM UTC
Resolved
May 01, 2025, 07:40 PM UTC
Duration
1h
Timeline · 2 updates
  1. identified May 01, 2025, 06:39 PM UTC

    We are aware of an issue reaching the Convoso Support team via phone at this time. We are still here to help! Please reach out to us via Email or Chat and we will assist you as soon as possible. We apologize, and thank you for being a Convoso Customer!

  2. resolved May 01, 2025, 07:40 PM UTC

    Our support phone line is back operational. We apologize for the brief interruption in phone support and thank you for your patience as we worked to resolve this.

Read the full incident report →

Minor April 24, 2025

Users may experience trouble accessing Convoso

Detected by Pingoru
Apr 24, 2025, 01:32 PM UTC
Resolved
Apr 24, 2025, 02:09 PM UTC
Duration
36m
Affected: DialerCampaigns and HopperScriptsAPIWorkflow AutomationLeadsReports and Dashboards
Timeline · 3 updates
  1. investigating Apr 24, 2025, 01:32 PM UTC

    Users may be experiencing trouble connecting to agent.convoso.com at this time. We are urgently working to resolve this issue.

  2. monitoring Apr 24, 2025, 01:50 PM UTC

    A fix has been implemented and we are closely monitoring for any persisting impact at this time.

  3. resolved Apr 24, 2025, 02:09 PM UTC

    As of 7:05 AM PST this issue has been resolved. We appreciate your patience as we worked to address this issue. We apologize for any impact this may have had on your operations, and customers who reported impact will receive an RFO once available.

Read the full incident report →

Major April 3, 2025

Customers may experience trouble with calls connecting

Detected by Pingoru
Apr 03, 2025, 02:02 PM UTC
Resolved
Apr 03, 2025, 06:00 PM UTC
Duration
3h 58m
Affected: Dialer
Timeline · 4 updates
  1. investigating Apr 03, 2025, 02:02 PM UTC

    We are investigating an issue where some calls may not properly connect. Our team is urgently investigating this as a priority 1 incident.

  2. identified Apr 03, 2025, 02:10 PM UTC

    Our team has identified the issue and work to resolve customer impacts have begun. We apologize for any impact this may have on your operations currently and appreciate your patience.

  3. monitoring Apr 03, 2025, 03:02 PM UTC

    A fix has been rolled out and our teams are closely monitoring for further impacts.

  4. resolved Apr 03, 2025, 06:00 PM UTC

    At this time, we can confirm the fix deployed at 7:56 AM PST has fully resolved this issue. We apologize for any impact it may have had on your operations. We will be sending an RFO to any customers who reported impacted as soon as it is completed. Thank you for your patience as we worked to urgently correct this issue.

Read the full incident report →

Minor March 13, 2025

Users may see delays logging into Convoso

Detected by Pingoru
Mar 13, 2025, 02:30 PM UTC
Resolved
Mar 13, 2025, 04:47 PM UTC
Duration
2h 16m
Affected: Dialer
Timeline · 4 updates
  1. identified Mar 13, 2025, 03:31 PM UTC

    We have identified an issue where users may see delays or trouble logging into Convoso. We are actively deploying a fix for this issue and we appreciate your patience as we work urgently to resolve this.

  2. identified Mar 13, 2025, 03:43 PM UTC

    Our team has identified users may also see delays then disconnects from the Agent UI. We are working to resolve any impacts with the highest priority.

  3. monitoring Mar 13, 2025, 04:19 PM UTC

    A fix has been deployed as of 9:15 AM PST. We are monitoring closely to confirm full resolution at this time.

  4. resolved Mar 13, 2025, 04:47 PM UTC

    At this time we have confirmed there should be no further customer impact after 9:15 AM PST. Thank you for your patience as we worked to resolve this issue and we apologize for any impact it may have had on your operations. Customers who reported impact will receive an RFO as soon as it is completed.

Read the full incident report →

Critical February 20, 2025

Customers may experience trouble accessing Convoso

Detected by Pingoru
Feb 20, 2025, 05:00 PM UTC
Resolved
Feb 20, 2025, 10:12 PM UTC
Duration
5h 12m
Affected: DialerCampaigns and HopperScriptsAPIWorkflow AutomationLeadsReports and Dashboards
Timeline · 4 updates
  1. identified Feb 20, 2025, 05:25 PM UTC

    We are urgently investigating an issue where customers are unable to access the Convoso platform. We have identified the issue and working urgently to resolve this.

  2. monitoring Feb 20, 2025, 05:36 PM UTC

    At this time, a fix has been rolled out and users should no longer see major impacts. We are closely monitoring to verify full resolution.

  3. monitoring Feb 20, 2025, 05:56 PM UTC

    Customers should no longer see any further impact. We will continue to monitor throughout the day to verify complete platform recovery. We apologize for the impact this may have had on your operations. We will send an RFO to customers who reported the impact and we thank you for your patience as we worked to address this issue.

  4. resolved Feb 20, 2025, 10:12 PM UTC

    At this time we have confirmed no further widespread issues. Thank you once again for your patience as we worked to resolve this issue earlier. Customers who reported impact will receive an RFO as soon as one is available.

Read the full incident report →

Major February 18, 2025

Customers may experience trouble accessing Convoso Admin portal

Detected by Pingoru
Feb 18, 2025, 09:04 PM UTC
Resolved
Feb 19, 2025, 12:55 AM UTC
Duration
3h 51m
Affected: DialerCampaigns and HopperAPIWorkflow AutomationLeadsReports and Dashboards
Timeline · 6 updates
  1. investigating Feb 18, 2025, 09:33 PM UTC

    At this time, our team is investigating issues accessing Convoso for a group of our customers. This is a priority 1 issue and we are urgently working to resolve this.

  2. investigating Feb 18, 2025, 09:34 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 18, 2025, 09:47 PM UTC

    We are still investigating this issue.

  4. identified Feb 18, 2025, 10:10 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Feb 18, 2025, 10:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Feb 19, 2025, 12:55 AM UTC

    We have confirmed that this incident is now resolved. We apologize for the inconvenience and we appreciate your patience as we worked to resolve this issue and apologize for any impact on your day-to-day operations. Customers who reached out to our support team will receive an RFO about this issue as soon as possible.

Read the full incident report →