Störungsverlauf von Phonecheck

1. 1. September 2026 um 14:32 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit Phonecheck

2. 1. September 2026 um 15:02 UTCidentified

   Das Problem wurde identifiziert und es wurde behoben, Phonecheck sollte zu diesem Zeitpunkt in Betrieb sein.

3. 1. September 2026 um 15:10 UTCmonitoring

   Wir überwachen alle Dienste, um sicherzustellen, dass sie stabil sind

4. 1. September 2026 um 18:05 UTCresolved

   Alle dienste waren in den letzten 3 stunden stabil, als gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 17. August 2026 um 21:18 UTCinvestigating

   Wir untersuchen derzeit das Problem, bitte stehen Sie zu, wie wir bieten eine Lösung ASAP

2. 17. August 2026 um 21:40 UTCmonitoring

   Der Phonecheck-Dienst sollte nun wieder funktionsfähig sein. Wir überwachen das System jedoch weiterhin genau, da es einige Zeit dauern kann, bis sich alle Dienste vollständig stabilisiert haben.

3. 17. August 2026 um 22:14 UTCresolved

   Dieser Vorfall wurde behoben, wir werden sicher sein, dieses Problem zu berücksichtigen und eine Lösung zu finden, um zu verhindern, dass sich dieser Vorfall wiederholt.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 22. Juli 2026 um 16:02 UTCidentified

   Wir haben bestätigt, dass der Finanzcheck von Verizon derzeit ausfällt. Wir warten darauf, von verizon für eine eta zu hören, wann dies wieder online gehen wird.

2. 22. Juli 2026 um 16:46 UTCmonitoring

   Verizon hat bestätigt, dass der Finanzcheck wieder online sein sollte. Wir überwachen derzeit, um sicherzustellen, dass es funktioniert.

3. 22. Juli 2026 um 18:01 UTCresolved

   Verizon Finance ESN Server ist wieder online

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 21. Juli 2026 um 20:45 UTCidentified

   Bitte beachten Sie, dass bei APIs für CarrierLock und SimLock intermittierende Probleme auf dem Desktop auftreten und die Verwendung auf dem IMEI-Checker Single/Bulk nicht möglich ist.

2. 29. Juli 2026 um 19:13 UTCresolved

   Dieser Vorfall wurde behoben; Die SIM-Lock- und Carrier-Lock-Server sollten wieder normal funktionieren.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 11. März 2026 um 20:22 UTCidentified

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

2. 11. März 2026 um 20:49 UTCmonitoring

   This should be fixed. Please confirm and provide feedback.

3. 11. März 2026 um 20:59 UTCresolved

   This incident is being reported as resolved by all clients.

1. 20. November 2025 um 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. November 2025 um 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. November 2025 um 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. November 2025 um 14:29 UTCresolved

   This incident has been resolved.

1. 11. November 2025 um 21:53 UTCinvestigating

   We are currently investigating the issue

2. 12. November 2025 um 02:33 UTCresolved

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

1. 15. August 2025 um 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. August 2025 um 19:54 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 18. August 2025 um 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. August 2025 um 20:41 UTCinvestigating

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

2. 13. August 2025 um 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. August 2025 um 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. Juli 2025 um 16:27 UTCinvestigating

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

2. 20. Juli 2025 um 17:19 UTCresolved

   The issue should be resolved at this time

1. 15. Juli 2025 um 20:05 UTCinvestigating

   We are currently investigating the issue

2. 15. Juli 2025 um 20:52 UTCmonitoring

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

3. 15. Juli 2025 um 21:05 UTCresolved

   Issue has been confirmed to be resolved

1. 29. Mai 2025 um 12:20 UTCinvestigating

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

2. 29. Mai 2025 um 12:55 UTCresolved

   This incident has been resolved.

1. 15. April 2025 um 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. April 2025 um 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. April 2025 um 21:43 UTCresolved

   The iOS app is fully operational

1. 3. April 2025 um 16:56 UTCinvestigating

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

2. 3. April 2025 um 17:42 UTCmonitoring

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

3. 3. April 2025 um 18:05 UTCresolved

   Phonecheck performance issue has been resolved

1. 3. April 2025 um 15:13 UTCinvestigating

   We are currently investigating an issue with performance reported on Phonecheck

2. 3. April 2025 um 15:14 UTCinvestigating

   We are continuing to investigate this issue.

3. 3. April 2025 um 15:34 UTCmonitoring

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

4. 3. April 2025 um 15:50 UTCresolved

   Phonecheck performance issue has been resolved

1. 27. Februar 2025 um 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. Februar 2025 um 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. Februar 2025 um 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. Februar 2025 um 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. März 2025 um 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. Februar 2025 um 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. Februar 2025 um 02:03 UTCresolved

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

1. 31. Januar 2025 um 16:20 UTCinvestigating

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

2. 31. Januar 2025 um 16:27 UTCmonitoring

   We are receiving reports that Phonecheck is operational at this time

3. 31. Januar 2025 um 21:31 UTCresolved

   This incident has been resolved.

1. 21. Januar 2025 um 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. Januar 2025 um 22:29 UTCresolved

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

1. 24. Oktober 2024 um 21:39 UTCinvestigating

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

2. 24. Oktober 2024 um 22:00 UTCinvestigating

   We are continuing to investigate this issue.

3. 24. Oktober 2024 um 22:03 UTCresolved

   This incident has been resolved.