Histórico de interrupções do Vantiv

1. 2 Gwengolo 2026 da 13:00 UTCinvestigating

   Estamos a investigar um atraso no acordo. Alguns clientes podem estar passando por um atraso no financiamento como resultado. Nossos engenheiros estão trabalhando para investigar e resolver o problema.

2. 2 Gwengolo 2026 da 13:21 UTCidentified

   Identificámos a questão que afecta o atraso na liquidação. Nossa equipe está trabalhando ativamente para uma resolução o mais rápido possível. Agradecemos a sua paciência.

3. 2 Gwengolo 2026 da 14:27 UTCidentified

   Estamos a trabalhar activamente no sentido de uma resolução sobre esta questão.

4. 2 Gwengolo 2026 da 19:10 UTCmonitoring

   Estamos monitorando uma correção que foi empurrada para re-submissão e aguardando uma resposta do processador.

5. 2 Gwengolo 2026 da 20:32 UTCresolved

   Os acordos foram reapresentados com sucesso e resolvidos.

Traduzido automaticamente da atualização oficial do incidente.

1. 28 Eost 2026 da 03:36 UTCinvestigating

   Engenheiros estão monitorando problemas de conectividade para o gateway. Erros e maiores tempos de transação ocorreram de 22:05 - 22:30 CDT

2. 28 Eost 2026 da 04:20 UTCmonitoring

   Engenheiros estão monitorando problemas de conectividade para o gateway. Erros e tempos de transação mais longos ocorreram entre 22:05 - 23:00 CDT

3. 28 Eost 2026 da 04:55 UTCresolved

   Não vimos mais problemas de conectividade para o portal. Erros e tempos de transação mais longos ocorreram de 22:20-23:15 CDT.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Eost 2026 da 03:52 UTCmonitoring

   Engenheiros estão monitorando problemas de conectividade para o gateway. Erros e tempos de transação mais longos ocorreram de 22:05 - 22:20 CDT.

2. 26 Eost 2026 da 04:32 UTCresolved

   Não vimos mais problemas de conectividade para o portal. Erros e tempos de transação mais longos ocorreram de 22:05 - 22:20 CDT.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Eost 2026 da 07:21 UTCinvestigating

   Devido a uma interrupção de serviço no Primeiro Data Rapid Connect, os comerciantes podem esperar um atraso no financiamento.

2. 23 Eost 2026 da 08:03 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

3. 23 Eost 2026 da 08:29 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Eost 2026 da 22:59 UTCinvestigating

   We are currently investigating increased latency and connectivity issues affecting API requests to the Query API. Some users may experience slower-than-normal response time.

2. 12 Eost 2026 da 23:30 UTCidentified

   We have identified the issue affecting the Query API. Our engineering team is actively implementing a fix and mitigating the impact to restore normal service as quickly as possible.

3. 12 Eost 2026 da 23:34 UTCmonitoring

   We have identified and resolved the issue affecting the Query API. Our engineers are closely monitoring the service to confirm that all systems remain stable and fully operational.

4. 12 Eost 2026 da 23:55 UTCresolved

   Engineers have resolved and confirmed the impacted services are operational and stable.

1. 7 Eost 2026 da 20:29 UTCinvestigating

   We have identified issues relating to Query API. Our Engineers are working to resolve the issue as soon as possible.

2. 7 Eost 2026 da 20:56 UTCmonitoring

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

3. 7 Eost 2026 da 22:22 UTCresolved

   Engineers have resolved and confirmed the services are operational and stable.

1. 5 Eost 2026 da 14:26 UTCresolved

   Due to a service interruption on the TSYS settler, merchants may expect a delay in funding. This issue is now resolved.

1. 9 Gouere 2026 da 14:46 UTCinvestigating

   Atualmente estamos investigando problemas com o checkout de coleta. Os usuários podem experimentar ver "este carrinho não é válido" erro ao usar coletar links de checkout. A nossa equipa está a investigar a causa e a trabalhar numa resolução o mais rapidamente possível.

2. 9 Gouere 2026 da 15:14 UTCinvestigating

   Os nossos engenheiros continuam a investigar a questão. Agradecemos a sua paciência neste momento, enquanto encontramos uma solução.

3. 9 Gouere 2026 da 15:14 UTCidentified

   Identificámos a causa das questões. Nossa equipe de engenharia está implementando uma correção e trabalhando para restaurar o serviço normal o mais rápido possível.

4. 9 Gouere 2026 da 15:15 UTCmonitoring

   Nossa equipe de engenharia continua engajada e continua monitorando de perto o ambiente para garantir estabilidade e confirmar que a questão foi totalmente resolvida. Os serviços estão actualmente a funcionar como esperado.

5. 9 Gouere 2026 da 19:11 UTCresolved

   A questão foi resolvida e os serviços voltaram à operação normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Gouere 2026 da 13:42 UTCinvestigating

   Atualmente estamos investigando relatos de latência elevada. Alguns utilizadores podem experimentar tempos de resposta mais lentos do que os normais. A nossa equipa está a investigar a causa e a trabalhar numa resolução o mais rapidamente possível.

2. 6 Gouere 2026 da 14:45 UTCinvestigating

   Os nossos engenheiros continuam a mitigar o problema. Agradecemos a sua paciência neste momento, enquanto encontramos uma solução.

3. 6 Gouere 2026 da 15:00 UTCidentified

   Identificamos a causa dos problemas de conectividade. Nossa equipe de engenharia está implementando uma correção e trabalhando para restaurar o serviço normal o mais rápido possível.

4. 6 Gouere 2026 da 16:08 UTCmonitoring

   Nossa equipe de engenharia continua engajada e continua monitorando de perto o ambiente para garantir estabilidade e confirmar que a questão foi totalmente resolvida. Os serviços estão actualmente a funcionar como esperado.

5. 6 Gouere 2026 da 16:11 UTCresolved

   A questão foi resolvida e os serviços voltaram à operação normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Mezheven 2026 da 03:11 UTCinvestigating

   Os engenheiros estão a investigar falhas na entrega dos ganchos.

2. 24 Mezheven 2026 da 03:29 UTCresolved

   A entrega dos Webhooks foi retomada. A entrega foi interrompida das 9h48 às 10h17 CDT.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Mezheven 2026 da 11:38 UTCmonitoring

   Engineers are investigating settlements delayed from approximately 10:40 PM CDT. The delayed batches are submitting as of 6:35 AM CDT.

2. 22 Mezheven 2026 da 12:20 UTCresolved

   Delayed batches have been submitted to processors for settlement. Some batches may take additional time for their current status to be reflected in reports.

1. 22 Mezheven 2026 da 03:25 UTCinvestigating

   Engineers are investigating increased errors on the gateway platform.

2. 22 Mezheven 2026 da 03:46 UTCmonitoring

   Engineers are monitoring errors on the gateway. Transactions are currently processing normally.

3. 22 Mezheven 2026 da 04:01 UTCresolved

   No further issues have been observed. Increased errors occurred from 10:14:12 PM CDT - 10:15:52 PM CDT.

1. 17 Mezheven 2026 da 04:10 UTCidentified

   We have identified issues relating to EMV Processors. Engineers are working to resolve the issue as soon as possible.

2. 17 Mezheven 2026 da 04:45 UTCmonitoring

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

3. 17 Mezheven 2026 da 05:07 UTCresolved

   This issue has been resolved and all services are operating normally. EMV Processors experienced degraded processing on 2026-06-16 between 22:31 and 23:45 CDT.

1. 11 Mezheven 2026 da 23:52 UTCidentified

   We have identified issues relating to Query API. Our Engineers are working to resolve the issue as soon as possible.

2. 12 Mezheven 2026 da 01:21 UTCmonitoring

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

3. 12 Mezheven 2026 da 02:24 UTCresolved

   Engineers have resolved and confirmed the services are operational and stable.

1. 7 Mezheven 2026 da 14:37 UTCinvestigating

   We are currently investigating a possible service incident that may be impacting one or more functions of the Gateway. Some customers may be experiencing service issues as a result. Our engineers are working to investigate and resolve the issue.

2. 7 Mezheven 2026 da 14:59 UTCmonitoring

   A fix has been implemented and we are actively monitoring the results. All sites are currently functional and operating normally. Our engineering team remains engaged and is continuing to closely monitor the situation to ensure stability.

3. 7 Mezheven 2026 da 16:44 UTCresolved

   This issue has been resolved and all services are operating normally.

1. 2 Mezheven 2026 da 15:29 UTCinvestigating

   Engineers are investigate settlement delays on the First Data Nashville North platform.

2. 2 Mezheven 2026 da 18:46 UTCidentified

   Engineers have identified the cause of the settlement delay. Many of the outstanding settlement batches have been submitted to First Data Nashville North as of 12:42 PM CDT. Engineers are working to process the remaining batches.

3. 2 Mezheven 2026 da 19:36 UTCmonitoring

   All of the outstanding First Data Nashville North batches have been submitted. Engineers are monitoring for responses from First Data.

4. 2 Mezheven 2026 da 22:27 UTCresolved

   Response files from First Data Nashville North have completed processing, and settlement is now up to date.

1. 16 Mae 2026 da 03:33 UTCinvestigating

   We have identified issues relating to Apple Pay. Engineers are working to resolve the issue as soon as possible.

2. 16 Mae 2026 da 03:51 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 18:02 UTCmonitoring

   We are currently seeing elevated email delivery failures to Microsoft-managed email domains, including outlook.com, hotmail.com, msn.com, and related services. Password reset emails, OTP codes, device codes, settlement reports, and transaction receipts sent to these domains may be impacted. The issue currently appears limited to Microsoft's consumer (free) email services, with Microsoft 365 (O365) accounts remaining unaffected, as are many other reputable senders. This is related to Microsoft-side filtering controls and is not specific to our email configuration. As a temporary workaround, we recommend using an alternate, non-Microsoft email provider where possible. We have opened a support case with Microsoft and are actively monitoring the situation. At this time, we do not have an estimated time frame for resolution, and will update when the issue has been resolved.

2. 3 Mezheven 2026 da 13:04 UTCresolved

   This incident is now resolved.

1. 6 Mae 2026 da 21:47 UTCinvestigating

   We are currently investigating increased latency and connectivity issues affecting API requests to the Query API. Some users may experience slower-than-normal response time.

2. 6 Mae 2026 da 22:12 UTCidentified

   We have identified the issue affecting the Query API. Our engineering team is actively implementing a fix and mitigating the impact to restore normal service as quickly as possible.

3. 6 Mae 2026 da 22:39 UTCmonitoring

   We have identified and resolved the issue affecting the Query API. Our engineers are closely monitoring the service to confirm that all systems remain stable and fully operational.

4. 7 Mae 2026 da 00:08 UTCresolved

   Engineers have resolved and confirmed the impacted services are operational and stable.

1. 3 Mae 2026 da 21:51 UTCinvestigating

   We are currently investigating increased latency affecting API requests. Some may experience slower-than-normal response times.

2. 3 Mae 2026 da 22:12 UTCidentified

   We have identified the issue. Our team is actively working on implementing a fix and mitigating the impact.

3. 3 Mae 2026 da 22:24 UTCmonitoring

   A fix has been implemented and we are monitoring to confirm all services are stable.

4. 3 Mae 2026 da 22:45 UTCresolved

   Engineers have resolved and confirmed the impacted services are operational and stable.