Histórico de interrupções do Phonecheck

1. 1 Gwengolo 2026 da 14:32 UTCinvestigating

   Atualmente estamos investigando um problema com o Phonecheck

2. 1 Gwengolo 2026 da 15:02 UTCidentified

   O problema foi identificado e foi resolvido, a verificação telefônica deve estar operacional neste momento.

3. 1 Gwengolo 2026 da 15:10 UTCmonitoring

   Estamos a monitorizar todos os serviços para garantir a sua estabilidade

4. 1 Gwengolo 2026 da 18:05 UTCresolved

   Todos os serviços estão estáveis nas últimas 3 horas, considerados resolvidos.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Eost 2026 da 21:18 UTCinvestigating

   Estamos a investigar a questão, por favor aguardem enquanto fornecemos uma solução o mais rapidamente possível

2. 17 Eost 2026 da 21:40 UTCmonitoring

   O serviço de verificação de telefone deve estar operacional novamente. No entanto, continuamos a acompanhar de perto o sistema, pois pode levar algum tempo para que todos os serviços se estabilizem plenamente.

3. 17 Eost 2026 da 22:14 UTCresolved

   Este incidente foi resolvido, teremos a certeza de prestar contas desta questão e fornecer uma solução para evitar que este incidente volte a acontecer.

Traduzido automaticamente da atualização oficial do incidente.

1. 22 Gouere 2026 da 16:02 UTCidentified

   Confirmamos que o controlo financeiro da Verizon está em baixo. Estamos à espera de resposta da Verizon para uma ETA sobre quando isto vai voltar online.

2. 22 Gouere 2026 da 16:46 UTCmonitoring

   A Verizon confirmou que o cheque das Finanças deveria estar online. Estamos a monitorizar para garantir que está a funcionar.

3. 22 Gouere 2026 da 18:01 UTCresolved

   Verizon Finance ESN server está de volta online

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 20:45 UTCidentified

   Por favor, note que APIs para CarrierLock e SimLock estão experimentando problemas intermitentes no Desktop e são completamente incapazes de serem usadas no verificador IMEI Single/Bulk.

2. 29 Gouere 2026 da 19:13 UTCresolved

   Este incidente foi resolvido; os servidores de bloqueio SIM e porta-aviões devem estar funcionando normalmente novamente.

Traduzido automaticamente da atualização oficial do incidente.

1. 11 Meurzh 2026 da 20:22 UTCidentified

   Our dev team is working on resolving the issue with the Remote App

2. 11 Meurzh 2026 da 20:49 UTCmonitoring

   This should be fixed. Please confirm and provide feedback.

3. 11 Meurzh 2026 da 20:59 UTCresolved

   This incident is being reported as resolved by all clients.

1. 20 Du 2025 da 12:17 UTCidentified

   We’re currently experiencing an issue where Apple server disruptions are causing inaccurate carrier and activation policy results worldwide. To ensure accuracy and protect your experience, we’ve temporarily paused the affected services. Our team is actively monitoring Apple’s recovery progress and running internal tests. Services will resume as soon as we confirm that everything is fully stable again. Thank you for your patience and understanding. If you have any urgent concerns, please feel free to reach out to our support team.

2. 20 Du 2025 da 14:50 UTCidentified

   Please note: Desktop Simlock checks remain fully operational and are not affected for users running version 3.12.8 or later. This disruption currently affects only the API services. We are confirming with our providers which specific services are recovering and will share updates as soon as those details are available. Our team is actively monitoring Apple’s recovery and performing internal validation. Services will resume as soon as we confirm full stability. Thank you for your patience and understanding. If you have any urgent concerns, please get in touch with our support team.

3. 20 Du 2025 da 17:58 UTCidentified

   Apple’s carrier information service has recovered, and Carrier Information lookups are now back online. However, SIMLock-only checks remain paused due to continued instability with Apple’s SIMLock service. Desktop Simlock checks for users on version 3.12.8f and above remain fully operational and are not impacted. We’re continuing to monitor Apple’s recovery progress and will reopen SIMLock-only API services as soon as stability is confirmed. Thank you for your patience. Please reach out to our support team if you have any urgent needs.

4. 24 Du 2025 da 14:29 UTCresolved

   This incident has been resolved.

1. 11 Du 2025 da 21:53 UTCinvestigating

   We are currently investigating the issue

2. 12 Du 2025 da 02:33 UTCresolved

   This incident has been resolved. Recently processed devices are now appearing correctly in the Cloud Database.

1. 15 Eost 2025 da 19:53 UTCmonitoring

   We’re currently experiencing an issue where the Phonecheck iOS app may not open for some users. This is due to recent changes made by Apple that place new limits on certain connection requests our app relies on. These limits can temporarily disrupt access. Our development team is already implementing an update to ensure our app fully adapts to Apple’s new requirements. This update will be released on Monday as an over-the-air (OTA) update. Until then, we’re making temporary adjustments on our systems throughout the day to keep the app accessible. If the app becomes unresponsive, restarting Phonecheck after we’ve applied these changes should allow you to continue processing. We truly appreciate your understanding as we work to quickly bring you a permanent solution.

2. 15 Eost 2025 da 19:54 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 18 Eost 2025 da 17:25 UTCresolved

   Hello team, A mandatory update for Phonecheck3 has been pushed (3.12.6batch2) and must be accepted on all stations. This update is required in order to continue processing iOS devices. Due to recent changes from Apple, older versions of Phonecheck3 will no longer function reliably. Updating ensures the iOS app remains operational and prevents processing disruptions. Please ensure you update all stations as soon as possible. Our team will continue to monitor and assist with any issues that may arise. Thank you for your cooperation.

1. 13 Eost 2025 da 20:41 UTCinvestigating

   We are currently investigating an issue that is stemming from Apple's Servers experiencing an outage.

2. 13 Eost 2025 da 22:07 UTCidentified

   We’re aware that the Phonecheck iOS app is currently not opening. This issue is not on our side — it’s being caused by a problem with Apple’s servers. Apple Business Manager experienced outages yesterday and today, which has created a backlog of requests in their API. Unfortunately, this backlog is affecting the ability for our iOS app to launch properly. We’re closely monitoring Apple’s status and expect the issue to resolve once their systems finish processing the queued requests.

3. 14 Eost 2025 da 17:56 UTCresolved

   Good News -- We’re starting to receive reports that the iOS app is operational again. Please restart Phonecheck, select "Clear Cache" from the options at login, and then try processing your iOS devices. Let us know if everything is working on your end.

1. 20 Gouere 2025 da 16:27 UTCinvestigating

   Our development team is working to resolve an issue affecting the cloud portal and mobile processing.

2. 20 Gouere 2025 da 17:19 UTCresolved

   The issue should be resolved at this time

1. 15 Gouere 2025 da 20:05 UTCinvestigating

   We are currently investigating the issue

2. 15 Gouere 2025 da 20:52 UTCmonitoring

   The issue should be resolved. Please restart Phonecheck if needed.

3. 15 Gouere 2025 da 21:05 UTCresolved

   Issue has been confirmed to be resolved

1. 29 Mae 2025 da 12:20 UTCinvestigating

   We are currently investigating an outage that is causing issues with device processing on Phonecheck.

2. 29 Mae 2025 da 12:55 UTCresolved

   This incident has been resolved.

1. 15 Ebrel 2025 da 19:02 UTCinvestigating

   Apple is currently experiencing an issue on its end, which is preventing Phonecheck from accessing the mobile application for iOS. Please note that Androids can be processed at this time, while we wait to hear back from Apple.

2. 15 Ebrel 2025 da 21:26 UTCmonitoring

   Apple has resolved the issue on their end; we are getting reports of users able to open the iOS app once again. Please restart Phonecheck and try again.

3. 15 Ebrel 2025 da 21:43 UTCresolved

   The iOS app is fully operational

1. 3 Ebrel 2025 da 16:56 UTCinvestigating

   We are currently investigating an issue with performance degraded reported on Phonecheck

2. 3 Ebrel 2025 da 17:42 UTCmonitoring

   Phonecheck performance has improved and should be operational; some users may still experience random device delays.

3. 3 Ebrel 2025 da 18:05 UTCresolved

   Phonecheck performance issue has been resolved

1. 3 Ebrel 2025 da 15:13 UTCinvestigating

   We are currently investigating an issue with performance reported on Phonecheck

2. 3 Ebrel 2025 da 15:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 3 Ebrel 2025 da 15:34 UTCmonitoring

   Please restart Phonecheck; performance should be back to normal. We are currently monitoring the situation.

4. 3 Ebrel 2025 da 15:50 UTCresolved

   Phonecheck performance issue has been resolved

1. 27 Cʼhwevrer 2025 da 10:27 UTCinvestigating

   Our iOS app is currently being affected by Apple's current server issue, we are waiting on Apple to fix the issue.

2. 27 Cʼhwevrer 2025 da 14:22 UTCinvestigating

   Important Notice: Apple Server Issues Affecting Device Processing: We're experiencing intermittent problems processing Apple devices due to ongoing Apple server issues. While Apple's status page indicates this issue has been resolved, we're continuing to see inconsistent connectivity affecting the ability to process some Apple devices. What you need to know: This is an Apple server-side issue, not a problem with our systems Android devices can be processed without any issues For Apple devices: Some devices will process normally For devices that won't open/process, please close the app, wait a few minutes, and try again You may need to retry several times for successful processing We're actively working with Apple to ensure complete resolution of this issue. We apologize for any inconvenience and appreciate your patience while Apple addresses these server problems. https://www.apple.com/support/systemstatus/

3. 27 Cʼhwevrer 2025 da 16:44 UTCinvestigating

   We've escalated this to Apple Senior Tech Support, who have reported the issue to Apple Engineering for investigation. Apple's status page has confirmed this outage, noting "some users are affected" and "users may be experiencing intermittent issues with this service." https://www.apple.com/support/systemstatus/ Impact: Apple device processing may fail or be delayed to open the app. Android devices remain unaffected. Workaround: If experiencing issues with Apple devices, please close the application, wait a few minutes, and try processing again. We're monitoring the situation closely and will update you as Apple resolves the server issue. Thank you for your patience.

4. 28 Cʼhwevrer 2025 da 13:32 UTCmonitoring

   Service Status Update: Apple Server Performance Issues We have an important update regarding the Apple server issue. Apple's status page has now changed this to a performance issue rather than an outage, indicating: "Performance: Yesterday, 10:00 AM - ongoing. Some users are affected. This service may be slow or unavailable." https://www.apple.com/support/systemstatus/ Our team confirms that Apple devices are processing, but server slowness is causing delays. This is an improvement from the previous complete outage situation. Impact: Apple device processing is working but may be slower than normal. You might experience longer wait times when processing Apple devices. Android devices continue to function normally. Recommendation: Please allow extra time for Apple device processing. If a device seems stuck, the previous workaround of closing the application, waiting a few minutes, and trying again may still help. We continue to monitor the situation and are in contact with Apple regarding the full resolution of these performance issues. We appreciate your patience.

5. 3 Meurzh 2025 da 14:51 UTCresolved

   We're pleased to inform you that the Apple server performance issues have been resolved. According to Apple's status page, the issue that affected some users from February 27th at 10:00 AM until March 1st at 3:00 PM has been addressed. https://www.apple.com/support/systemstatus/ Our support team has been monitoring the situation overnight and confirms that the iOS app is now performing well with normal processing speeds for all Apple devices. You should now be able to process all devices, both Apple and Android, without experiencing any delays or connectivity issues. Thank you for your patience and understanding during this service disruption. As always, if you encounter any issues with our service, please contact our support team.

1. 26 Cʼhwevrer 2025 da 22:52 UTCinvestigating

   Our iOS app is currently being affected by Apple's current server issue, we are waiting on Apple to fix the issue.

2. 27 Cʼhwevrer 2025 da 02:03 UTCresolved

   Apple resolved their server issue - https://www.apple.com/support/systemstatus/

1. 31 Genver 2025 da 16:20 UTCinvestigating

   We are currently receiving reports of users unable to sign in or process devices.

2. 31 Genver 2025 da 16:27 UTCmonitoring

   We are receiving reports that Phonecheck is operational at this time

3. 31 Genver 2025 da 21:31 UTCresolved

   This incident has been resolved.

1. 21 Genver 2025 da 21:39 UTCmonitoring

   We were experiencing degraded performance causing issues with users' processing devices; this should be resolved by restarting Phonecheck. We are monitoring the situation should anything change.

2. 21 Genver 2025 da 22:29 UTCresolved

   Degraded Performance has been resolved; Cloud should be operating at full speed.

1. 24 Here 2024 da 21:39 UTCinvestigating

   We are currently investigating an outage that is causing issues with device processing on Phonecheck.

2. 24 Here 2024 da 22:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 24 Here 2024 da 22:03 UTCresolved

   This incident has been resolved.