История сбоев Plecto

1. 12 октября 2026 г. в 12:36 UTCidentified

   Мы переживаем ухудшение производительности. Некоторые функции могут быть медленнее, чем обычно. Наша команда проводит расследование, и обновления будут следовать на нашей странице статуса.

2. 13 октября 2026 г. в 06:05 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 22 июля 2026 г. в 09:17 UTCresolved

   Заявка была отключена между 00:00 и 01:30 из-за инцидента с нашим поставщиком инфраструктуры, связанного с критическим обслуживанием: https: / /status.scaleway.com / инциденты / 9m3kjv6w4371

Автоматический перевод официального обновления инцидента.

1. 16 июля 2026 г. в 09:12 UTCmonitoring

   Мы знаем о проблеме, затрагивающей создание новой приборной панели. Мы определили причину и работаем над исправлением. Мы обновим вас, как только это будет решено.

2. 16 июля 2026 г. в 09:24 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 19 июня 2026 г. в 07:04 UTCidentified

   We're aware of an issue affecting data imports from HubSpot into Plecto. HubSpot has incorrectly blocked the IP address Plecto connects from, which is preventing HubSpot-connected dashboards from importing and refreshing data. This is a network-level block on HubSpot's side and is not related to your Plecto account, your HubSpot account, or your credentials, no action is needed from you. We're in direct contact with HubSpot to have access restored as quickly as possible, and your HubSpot data will resume updating automatically once it is. All other integrations and dashboards are unaffected. We'll post another update as soon as we have more news.

2. 24 июня 2026 г. в 06:34 UTCresolved

   This incident has been resolved.

1. 18 июня 2026 г. в 10:55 UTCidentified

   We're aware of an issue affecting data imports from HubSpot into Plecto. HubSpot has incorrectly blocked the IP address Plecto connects from, which is preventing HubSpot-connected dashboards from importing and refreshing data. This is a network-level block on HubSpot's side and is not related to your Plecto account, your HubSpot account, or your credentials, no action is needed from you. We're in direct contact with HubSpot to have access restored as quickly as possible, and your HubSpot data will resume updating automatically once it is. All other integrations and dashboards are unaffected. We'll post another update as soon as we have more news.

2. 18 июня 2026 г. в 19:51 UTCresolved

   This incident has been resolved.

1. 17 июня 2026 г. в 11:57 UTCidentified

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

2. 17 июня 2026 г. в 11:58 UTCidentified

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

3. 17 июня 2026 г. в 12:05 UTCidentified

   Maintenance of underlying infrastructure

4. 17 июня 2026 г. в 12:40 UTCmonitoring

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

5. 17 июня 2026 г. в 13:04 UTCresolved

   This incident has been resolved.

1. 22 мая 2026 г. в 09:24 UTCidentified

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

2. 22 мая 2026 г. в 09:48 UTCresolved

   This incident has been resolved.

1. 8 мая 2026 г. в 07:21 UTCidentified

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

2. 8 мая 2026 г. в 10:06 UTCmonitoring

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

3. 8 мая 2026 г. в 11:45 UTCresolved

   This incident has been resolved.

1. 28 апреля 2026 г. в 14:11 UTCinvestigating

   We are currently investigating this issue.

2. 28 апреля 2026 г. в 14:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 апреля 2026 г. в 15:38 UTCresolved

   This incident has been resolved.

1. 9 апреля 2026 г. в 10:15 UTCidentified

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

2. 9 апреля 2026 г. в 10:30 UTCmonitoring

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

3. 9 апреля 2026 г. в 10:53 UTCresolved

   This incident has been resolved.

1. 26 марта 2026 г. в 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 26 марта 2026 г. в 14:52 UTCresolved

   This incident has been resolved.

1. 25 марта 2026 г. в 08:18 UTCidentified

   Affected integrations: - Accelo - ActiveCampaign - Asana V2 - Calendly - CallTools - CallTrackingMetrics - Capturi - Capsule CRM - Chargebee - Clio - Clockify - Close - CloudTalk - Copper CRM - Creatio - Delighted - Dialfire - Dialpad - Dinero - Dynamics 365 Business Central - Dynamics 365 Sales - EasyProject - EasyTableBooking - Etrack1 - Fenerum Dynamic - Fiken - FlexyBox - Follow Up Boss - Freshworks CRM - GetAccept - GoHighlevel - Google My Business - Gravity Forms - Guesty V2 - Harvest V2 - HubStaff - InfusionSoft - JustCall - Keatech - Kiflo - Klaviyo V2 - Lime CRM - Linear - Mailchimp - OnlinePOS - Outreach - PagerDuty - Pipeliner CRM - Pirate Weather - QuickBooks Online - Rackbeat - Recruit CRM - Recruitee - ReePay - RingCentral - Salesmate - Scoro - Serio Verify V2 - ServicePOS - SharpSpring - Shopify PI V2 - Shopware - Spotify - Startdeliver - SuperOffice - Teamleader - Teamwork - Telavox - Toggl Track - TOPdesk - TrackingTime - Tripletex - Trustpilot - TypeForm - Uniconta - Vitally - weclapp - WooCommerce - Younium - Zendesk Sell - Zoho Books - Zoho Desk - Zoho Projects - Zoho SalesIQ - ZoneSoft - Zoom - Zoom Phone

2. 25 марта 2026 г. в 09:40 UTCmonitoring

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

3. 25 марта 2026 г. в 10:04 UTCresolved

   This incident has been resolved.

1. 1 декабря 2025 г. в 08:09 UTCinvestigating

   We are currently investigating this issue.

2. 1 декабря 2025 г. в 08:20 UTCresolved

   This incident has been resolved.

1. 28 ноября 2025 г. в 10:46 UTCidentified

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

2. 28 ноября 2025 г. в 13:03 UTCresolved

   This incident has been resolved.

1. 28 ноября 2025 г. в 10:06 UTCidentified

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

2. 28 ноября 2025 г. в 13:20 UTCresolved

   This incident has been resolved.

1. 26 ноября 2025 г. в 17:31 UTCidentified

   We're expriencing connectivity issues caused by our hosting provider which cause delays in data processing.

2. 26 ноября 2025 г. в 17:38 UTCidentified

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

3. 26 ноября 2025 г. в 18:03 UTCresolved

   This incident has been resolved.

1. 26 ноября 2025 г. в 12:45 UTCidentified

   We're observing connectivity issues across entire platform that are affecting response times and cause delays in data processing.

2. 26 ноября 2025 г. в 13:19 UTCresolved

   This incident has been resolved.

1. 26 ноября 2025 г. в 08:19 UTCinvestigating

   We're seeing an increased amount of 502 errors across the platform, we're investigating the issue

2. 26 ноября 2025 г. в 09:21 UTCresolved

   This incident has been resolved.

1. 5 ноября 2025 г. в 15:10 UTCidentified

   We're seeing a large amount of 500 errors across the platform, we identified the reason and the fix is on the way

2. 5 ноября 2025 г. в 15:16 UTCmonitoring

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

3. 5 ноября 2025 г. в 15:18 UTCresolved

   This incident has been resolved.

1. 28 октября 2025 г. в 19:10 UTCmonitoring

   We're experiencing interruption of integration data imports due to external hosting component failure. We're awaiting the component to recover.

2. 29 октября 2025 г. в 09:05 UTCidentified

   We’re still awaiting recovery of the external hosting component causing interruptions to integration data imports. In parallel, we’re investigating alternative ways to resolve or work around the issue.

3. 29 октября 2025 г. в 11:55 UTCmonitoring

   We’ve implemented a workaround for the external hosting issue, and data imports are now resuming. We’re currently processing the backlog to catch up with the delay.

4. 29 октября 2025 г. в 13:27 UTCmonitoring

   Data imports are progressing normally, and we expect to be fully caught up with the delay within the next 15 minutes.

5. 29 октября 2025 г. в 13:44 UTCresolved

   Data imports have fully caught up, everything is operating normally. We apologize for the inconvenience caused.