Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Beamery

    15 incidentes de Beamery registrados desde septiembre de 2025, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Datos obsoletos en los informes

    Comenzó 23 de septiembre de 2026 a las 9:34 UTC · 7d 2h

    IssuesIncidente menor
    1. 23 de septiembre de 2026 a las 9:34 UTCinvestigating

      Actualmente estamos investigando algunas imprecisiones (datos actualizados) en informes dentro de nuestra función de presentación de informes. No se han perdido datos y proporcionaremos una actualización tan pronto como podamos. Nuestras disculpas por cualquier inconveniente causado, Beamery Engineering

    2. 24 de septiembre de 2026 a las 8:21 UTCidentified

      Hemos identificado la cuestión y hemos iniciado una actualización de datos en todos los entornos de producción para remediar las imprecisiones dentro de los informes. Esta semana proporcionaremos más información sobre los plazos para su finalización. Nuestras disculpas por cualquier inconveniente causado, Beamery Engineering

    3. 24 de septiembre de 2026 a las 13:50 UTCidentified

      Los informes de los arrendatarios privados y de la UE dentro de la CRM deben ser fijados y contener datos precisos. Los informes de los inquilinos de EE.UU. siguen en curso y una actualización se proporcionará lo antes posible. Nuestras disculpas por cualquier inconveniente causado, Beamery Engineering

    4. 28 de septiembre de 2026 a las 13:27 UTCmonitoring

      Todos los informes de los arrendatarios deben fijarse ahora con datos precisos. Nuestras disculpas por cualquier inconveniente causado, Beamery Engineering

    5. 30 de septiembre de 2026 a las 12:18 UTCresolved

      Esta cuestión se resuelve ahora. Gracias por su paciencia, Beamery Engineering

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

    Beamery Login Page Issues when visiting from https://beamery.eu

    Comenzó 1 de septiembre de 2026 a las 14:27 UTC · 51m

    Pending
    1. 1 de septiembre de 2026 a las 14:27 UTCinvestigating

      Estamos investigando los informes de usuarios de la UE que están siendo redirigidos a las páginas de inicio de sesión de los Estados Unidos al acceder a la página web de [Beamery](https://beamery.eu/ "Beamery homepage"). Si está experimentando este problema, utilice este enlace para iniciar sesión: [https://login.beamery.eu/sso](https://login.beamery.eu/sso "https://login.beamery.eu/sso")

    2. 1 de septiembre de 2026 a las 15:18 UTCresolved

      Hemos identificado y arreglado una cuestión que causó que algunos usuarios de la UE fueran redirigidos a [beamery.com](http://beamery.com "beamery.com") página de inicio de sesión en lugar de [beamery.eu](http://beamery.eu "beamery.eu"). La solución es ahora en vivo y no se necesita ninguna acción para la mayoría de los usuarios. Si usted todavía está siendo enviado a la página de inicio de sesión incorrecta, esto es una red de caché sostenida en su navegador en lugar de una falla en curso. Para resolverlo, despeje el caché de su navegador o vaya directamente a su página de inicio de sesión regional: • UE: [https://login.beamery.eu/sso](https://login.beamery.eu/sso "https://login.beamery.eu/sso") • US: [https://login.beamery.com/sso](https://login.beamery.com/sso "https://login.beamery.com/sso") Abrir la página en una ventana privada o incognito también evitará la red de caché si prefiere no limpiar su caché.

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

    El análisis de muestras no está disponible

    Comenzó 20 de agosto de 2026 a las 8:08 UTC · 10h 5m

    OutageIncidente mayor
    1. 20 de agosto de 2026 a las 8:08 UTCinvestigating

      Estamos experimentando problemas analizando curriculum vitae, nuestro equipo está investigando actualmente. No se pierde CV y lo volveremos a procesar todo lo antes posible. Gracias por su paciencia, Beamery Engineering

    2. 20 de agosto de 2026 a las 14:45 UTCmonitoring

      CV parsing se ha reanudado. Estamos re-procesando pares fallidos y no esperamos ninguna pérdida de datos. Gracias por entender, Beamery Engineering

    3. 20 de agosto de 2026 a las 18:14 UTCresolved

      CV parsing ha estado operativo desde 14:21 UTC. Todos los CV que habían fallado parándose entre las 18:30 UTC el 19 de agosto y luego se han vuelto a procesar. Nuestras disculpas por cualquier inconveniente causado, Beamery Engineering

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

    Reduced Email Deliverability for CRM-Generated Emails

    Comenzó 18 de junio de 2026 a las 10:46 UTC · 2h 9m

    IssuesIncidente menor
    1. 18 de junio de 2026 a las 10:46 UTCinvestigating

      We are investigating reports that some CRM system-generated emails may be delivered to recipients' spam or junk folders rather than their inboxes. This does not affect outbound candidate-facing emails, which are sending and delivering as normal. We will provide an update as soon as we have more information.

    2. 18 de junio de 2026 a las 11:01 UTCmonitoring

      We have implemented a fix for the affected CRM system-generated emails and are now monitoring deliverability to confirm messages are reaching inboxes as expected. As a precaution, we are also carrying out a final sweep to check for any other areas that may have been impacted. Outbound candidate-facing emails remain unaffected throughout. We will confirm once the fix is fully verified.

    3. 18 de junio de 2026 a las 12:55 UTCresolved

      The issue affecting deliverability of some CRM system-generated emails has been resolved. Our final sweep confirmed no other areas were impacted, and outbound candidate-facing emails were unaffected throughout. Deliverability has returned to normal. Thank you for your patience.

    (US Sandbox only) - Delays in Search and Automation

    Comenzó 6 de mayo de 2026 a las 20:39 UTC · 12h 23m

    IssuesIncidente menor
    1. 6 de mayo de 2026 a las 20:39 UTCidentified

      We're currently experiencing a delay in data synchronization in our Sandbox (US) environment due to an issue with one of our database nodes provided by our cloud infrastructure provider. **What this means for you** Features that rely on search indexing — including People Grid, recipes, and related functionality — may temporarily display or operate on outdated data. **Impact** • No data loss is expected. • Updates made during this period are not lost; they will be processed once synchronization resumes. • Other Sandbox functionality remains available and production environments are not impacted. We are actively monitoring the recovery of the affected node, after which data synchronization will automatically resume and catch up on any pending updates. We'll post further updates as the situation progresses. Thank you for your patience.

    2. 6 de mayo de 2026 a las 21:13 UTCmonitoring

      Data synchronization in our Sandbox (US) environment has been restored and is now processing normally. Any backlog has been fully caught up, and there is no longer any customer impact. Features that rely on search indexing — including People Grid, recipes, and related functionality — are once again operating on up-to-date data. We are continuing to monitor the environment closely while the underlying infrastructure recovery completes in the background. This work is not expected to affect service. Thank you for your patience.

    3. 7 de mayo de 2026 a las 9:02 UTCresolved

      The earlier data synchronization issue in our Sandbox (US) environment has been fully resolved. All services are operating normally, and features relying on search indexing, including People Grid, recipes, and related functionality, are running on up-to-date data. No data was lost during the incident, and all delayed updates have been successfully processed. Thank you for your patience while we worked through this.

    Increased latency on Search

    Comenzó 17 de marzo de 2026 a las 16:15 UTC · 17h 20m

    IssuesIncidente menor
    1. 17 de marzo de 2026 a las 16:15 UTCinvestigating

      Beamery Engineering team has been alerted to an increase in CPU usage in our ElasticSearch cluster, the issue is being investigated. Search results may respond slower than normal.

    2. 17 de marzo de 2026 a las 16:59 UTCidentified

      The team have identified a spike in Recipe usage as the root cause to the increased CPU. Additional resource is being deployed to support the increased load.

    3. 17 de marzo de 2026 a las 19:26 UTCidentified

      CPU usage on the ElasticSearch cluster continues to be high despite remediations, the Beamery Engineering team have made further adjustments to bring this down. Recipe process time is expected to be reduced.

    4. 17 de marzo de 2026 a las 23:17 UTCmonitoring

      Load is coming down following updates and normal service is expected to resume soon. The Beamery Engineering team are continuing to monitor the performance.

    5. 18 de marzo de 2026 a las 9:35 UTCresolved

      Elastic CPU returned to normal following mitigations, normal service resumed.

    Access to Events UI Unavailable

    Comenzó 19 de febrero de 2026 a las 16:25 UTC · 29m

    IssuesIncidente menor
    1. 19 de febrero de 2026 a las 16:25 UTCinvestigating

      Individual Events cannot be accessed via the Events Tab in the Beamery UI at this time. Beamery engineering is actively investigating a resolution to this issue.

    2. 19 de febrero de 2026 a las 16:54 UTCresolved

      Beamery Engineering team has now released a fix for this issue, and access to events UI is now restored as expected.

    Workday Outages causing Degraded Performance

    Comenzó 13 de febrero de 2026 a las 17:18 UTC · 2d 16h

    IssuesIncidente menor
    1. 13 de febrero de 2026 a las 17:18 UTCinvestigating

      We are currently experiencing disruptions across our Workday Integration caused by service outages to Workday, specifically affecting the WD3 and WD3 Non-Prod hosts. Our engineering team is actively investigating this issue and monitoring the situation.

    2. 16 de febrero de 2026 a las 9:37 UTCresolved

      As of 03:00 UTC on 14th February, the service outage experienced by Workday is no longer occurring. The Beamery<>Workday Integration is functioning as expected. Please reach out to [email protected] if you have any queries.

    Candidate Portal Login Issues

    Comenzó 14 de enero de 2026 a las 22:00 UTC · 1h 23m

    Pending
    1. 14 de enero de 2026 a las 22:00 UTCinvestigating

      We are aware of issues, with candidates being unable to login to the Candidate Portal, we are currently investigating.

    2. 14 de enero de 2026 a las 23:23 UTCresolved

      We have identified a fix, this has been deployed and tested and we can confirm that the issue has been resolved.

    Cloudflare outage causing impact for Beamery Sandbox US

    Comenzó 5 de diciembre de 2025 a las 10:00 UTC · 0m

    IssuesIncidente menor
    1. 8 de diciembre de 2025 a las 11:14 UTCresolved

      The Cloudflare outage has been restored and Beamery Sandbox US is back online.

    2. 8 de diciembre de 2025 a las 11:14 UTCmonitoring

      Cloudflare have implemented a fix which has restored Beamery Sandbox, we're continuing to monitor the situation.

    3. 8 de diciembre de 2025 a las 11:14 UTCinvestigating

      Beamery is investigating issues with our Sandbox US tenant relating to a Cloudflare outage following scheduled maintenance.   https://www.cloudflarestatus.com/

    Cloudflare Global Network Outage

    Comenzó 18 de noviembre de 2025 a las 16:02 UTC · 0m

    IssuesIncidente menor
    1. 2 de diciembre de 2025 a las 21:14 UTCresolved

      All services are operating normally

    2. 2 de diciembre de 2025 a las 21:14 UTCidentified

      Cloudflare service causing access issues to Beamery

    3. 2 de diciembre de 2025 a las 21:14 UTCmonitoring

      Cloudflare service outage is continuing to cause intermittent access issues to Beamery services. We are closely monitoring the situation.

    Elevated failure rates on Beamery systems due to outage of Cloud Provider

    Comenzó 20 de octubre de 2025 a las 22:57 UTC · 0m

    IssuesIncidente menor
    1. 2 de diciembre de 2025 a las 21:20 UTCinvestigating

      We are investigating an increase in errors using Beamery. This is related to the major AWS outage causing a major incident on one of our third-party providers.

    2. 2 de diciembre de 2025 a las 21:20 UTCresolved

      All services are operating normally.

    3. 2 de diciembre de 2025 a las 21:20 UTCmonitoring

      All services are operating normally. Some customers based in the US may still experience loading issues on the Beamery application until the third-party fully resolves their issue. We have observed improvements and expect full resolution soon.

    LinkedIn CRM Connect Sync Delays

    Comenzó 7 de octubre de 2025 a las 14:35 UTC · 0m

    IssuesIncidente menor
    1. 2 de diciembre de 2025 a las 21:28 UTCinvestigating

      LinkedIn CRM Connect sync is delayed

    2. 2 de diciembre de 2025 a las 21:28 UTCresolved

      Errors are back down and normal operations have resumed

    Degraded performance across various modules

    Comenzó 16 de septiembre de 2025 a las 11:09 UTC · 0m

    IssuesIncidente menor
    1. 2 de diciembre de 2025 a las 21:32 UTCinvestigating

      Across all environments, several modules within Beamery CRM are not functioning as expected, including: • Extension - Generate Email • Candidate Portals • Job Description Generation • Job Description Parsing • Recipes AI Search Beamery Engineering is currently investigating, and further updates will be provided. We thank you for your patience.

    2. 2 de diciembre de 2025 a las 21:32 UTCresolved

      All services are operating normally

    Some customers cannot access Beamery via SSO

    Comenzó 15 de septiembre de 2025 a las 16:25 UTC · 0m

    OutageIncidente mayor
    1. 2 de diciembre de 2025 a las 21:39 UTCinvestigating

      Some customers are unable to access Beamery via SSO

    2. 2 de diciembre de 2025 a las 21:39 UTCresolved

      All affected customers have been contacted with resolution steps and we have confirmed the issue is no longer present for all who have completed the steps.