Historial de interrupciones de Plecto

1. 12 de octubre de 2026 a las 12:36 UTCidentified

   Estamos experimentando un rendimiento degradado. Algunas características pueden ser más lentas de lo habitual. Nuestro equipo está investigando, y las actualizaciones seguirán en nuestra página de estado.

2. 13 de octubre de 2026 a las 6:05 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 22 de julio de 2026 a las 9:17 UTCresolved

   La solicitud se redujo entre las 00:00 y las 01:30 debido a nuestro incidente del proveedor de infraestructura relacionado con el servicio crítico: https://status.scaleway.com/incidents/9m3kjv6w4371

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de julio de 2026 a las 9:12 UTCmonitoring

   Somos conscientes de un problema que afecta a la nueva creación del tablero. Hemos identificado la causa y estamos trabajando en una solución. Te actualizaremos en cuanto se resuelva.

2. 16 de julio de 2026 a las 9:24 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de junio de 2026 a las 7: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 de junio de 2026 a las 6:34 UTCresolved

   This incident has been resolved.

1. 18 de junio de 2026 a las 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 de junio de 2026 a las 19:51 UTCresolved

   This incident has been resolved.

1. 17 de junio de 2026 a las 11:57 UTCidentified

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

2. 17 de junio de 2026 a las 11:58 UTCidentified

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

3. 17 de junio de 2026 a las 12:05 UTCidentified

   Maintenance of underlying infrastructure

4. 17 de junio de 2026 a las 12:40 UTCmonitoring

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

5. 17 de junio de 2026 a las 13:04 UTCresolved

   This incident has been resolved.

1. 22 de mayo de 2026 a las 9:24 UTCidentified

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

2. 22 de mayo de 2026 a las 9:48 UTCresolved

   This incident has been resolved.

1. 8 de mayo de 2026 a las 7:21 UTCidentified

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

2. 8 de mayo de 2026 a las 10:06 UTCmonitoring

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

3. 8 de mayo de 2026 a las 11:45 UTCresolved

   This incident has been resolved.

1. 28 de abril de 2026 a las 14:11 UTCinvestigating

   We are currently investigating this issue.

2. 28 de abril de 2026 a las 14:11 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 de abril de 2026 a las 15:38 UTCresolved

   This incident has been resolved.

1. 9 de abril de 2026 a las 10:15 UTCidentified

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

2. 9 de abril de 2026 a las 10:30 UTCmonitoring

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

3. 9 de abril de 2026 a las 10:53 UTCresolved

   This incident has been resolved.

1. 26 de marzo de 2026 a las 14:04 UTCinvestigating

   We are currently investigating this issue.

2. 26 de marzo de 2026 a las 14:52 UTCresolved

   This incident has been resolved.

1. 25 de marzo de 2026 a las 8: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 de marzo de 2026 a las 9:40 UTCmonitoring

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

3. 25 de marzo de 2026 a las 10:04 UTCresolved

   This incident has been resolved.

1. 1 de diciembre de 2025 a las 8:09 UTCinvestigating

   We are currently investigating this issue.

2. 1 de diciembre de 2025 a las 8:20 UTCresolved

   This incident has been resolved.

1. 28 de noviembre de 2025 a las 10:46 UTCidentified

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

2. 28 de noviembre de 2025 a las 13:03 UTCresolved

   This incident has been resolved.

1. 28 de noviembre de 2025 a las 10:06 UTCidentified

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

2. 28 de noviembre de 2025 a las 13:20 UTCresolved

   This incident has been resolved.

1. 26 de noviembre de 2025 a las 17:31 UTCidentified

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

2. 26 de noviembre de 2025 a las 17:38 UTCidentified

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

3. 26 de noviembre de 2025 a las 18:03 UTCresolved

   This incident has been resolved.

1. 26 de noviembre de 2025 a las 12:45 UTCidentified

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

2. 26 de noviembre de 2025 a las 13:19 UTCresolved

   This incident has been resolved.

1. 26 de noviembre de 2025 a las 8:19 UTCinvestigating

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

2. 26 de noviembre de 2025 a las 9:21 UTCresolved

   This incident has been resolved.

1. 5 de noviembre de 2025 a las 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 de noviembre de 2025 a las 15:16 UTCmonitoring

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

3. 5 de noviembre de 2025 a las 15:18 UTCresolved

   This incident has been resolved.

1. 28 de octubre de 2025 a las 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 de octubre de 2025 a las 9: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 de octubre de 2025 a las 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 de octubre de 2025 a las 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 de octubre de 2025 a las 13:44 UTCresolved

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