История сбоев Proemion

1. 22 октября 2026 г. в 09:35 UTCresolved

   Что касается двух широко рекламируемых уязвимостей PHP CVE-2026-109618 и CVE-2026-109619, мы уточняем, что Proemion не использует затронутую технологию ни в одной части своей DataPlatform или вспомогательных систем. Мы узнали об уязвимостях 21 октября 13:05 CEST и сразу же скоординировали внутренние действия для оценки риска, который был ограничен веб-сайтом Proemion. Мы настроили статическую копию веб-сайта, а затем отключили услуги до тех пор, пока не будет предоставлен и установлен патч. Кроме того, мы ждали 12 часов, прежде чем вернуть сайт в интернет. Нет никаких доказательств того, что уязвимости были успешно использованы против сайта. Сайт Proemion работает на отдельной инфраструктуре без какого-либо подключения к другим нашим сервисам. Мы публикуем это заявление всем клиентам, которые могут нуждаться в нем для своих целей.

Автоматический перевод официального обновления инцидента.

1. 15 октября 2026 г. в 10:17 UTCmonitoring

   Между 12oct2026 и 15oct2026 DataPlatform не отправляла никаких электронных писем.

2. 15 октября 2026 г. в 10:18 UTCmonitoring

   Мы продолжаем отслеживать любые дополнительные проблемы.

3. 15 октября 2026 г. в 10:21 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 15 октября 2026 г. в 10:14 UTCresolved

   Между 12oct2026 и 15oct2026 DataPlatform не отправляла никаких электронных писем. Мы определили и устранили первопричину.

Автоматический перевод официального обновления инцидента.

1. 29 сентября 2026 г. в 11:47 UTCinvestigating

   Мы знаем, что REST API в настоящее время недоступны. Мы активно работаем над этим вопросом.

2. 29 сентября 2026 г. в 11:49 UTCmonitoring

   Мы определили и развернули исправление. Мы следим за услугами.

3. 29 сентября 2026 г. в 14:29 UTCresolved

   Этот инцидент был урегулирован.

Автоматический перевод официального обновления инцидента.

1. 2 февраля 2026 г. в 12:25 UTCidentified

   Accessing Statuspage via the API is failing currently which is causing system metrics not to be updated. We are monitoring the issue currently while Statuspage is actively working on the fix.

2. 2 февраля 2026 г. в 15:39 UTCmonitoring

   We have created new Statuspage API keys and updated our integrations and system metrics are now showing correctly in our statuspage. We will continue to monitor the incident while Statuspage continues working on a permanent fix.

3. 3 февраля 2026 г. в 08:11 UTCidentified

   Statuspage has identified an issue affecting Statuspage System Metrics charts and for the time has disabled the System Metrics functionality.

4. 4 февраля 2026 г. в 09:01 UTCmonitoring

   Issue is still ongoing. Statuspage System Metrics remain disabled. We will continue to monitor the incident while Statuspage continues working on a permanent fix.

5. 5 февраля 2026 г. в 14:19 UTCmonitoring

   Issue is still ongoing. Statuspage System Metrics remain disabled. Statuspage will provide further updates by early next week.

6. 10 февраля 2026 г. в 11:54 UTCresolved

   Statuspage has disabled System Metrics indefinitely and as such they have been removed from our page. If Statuspage enables them in the future, we will show them again.

1. 5 ноября 2025 г. в 09:11 UTCinvestigating

   We are experiencing a local outage of the system linked to DataPlatform that serves for device activation processes like GoLive, Tariff Change, Contract Renewal and the hosting contract overview. The device activation functions (Go Live, Tariff Change, Renewals, Cancellation) on DataPortal and REST API are currently not possible. Also the hosting contract overview on Data Portal and REST API may not show all details. Our engineers are working on restoring the functionality.

2. 5 ноября 2025 г. в 12:14 UTCmonitoring

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

3. 5 ноября 2025 г. в 15:30 UTCresolved

   This incident has been resolved.

1. 12 сентября 2025 г. в 04:23 UTCinvestigating

   The services importing data from 3rd party platforms including AEMP imports are down, we are investigating the root cause.

2. 12 сентября 2025 г. в 06:32 UTCidentified

   Root cause identified. Our engineers are working on fixing it.

3. 12 сентября 2025 г. в 07:35 UTCmonitoring

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

4. 12 сентября 2025 г. в 08:15 UTCresolved

   This incident has been resolved.

1. 26 июня 2025 г. в 14:45 UTCidentified

   New device activation (go-live) currently has a problem, we are recovering the services.

2. 26 июня 2025 г. в 16:27 UTCmonitoring

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

3. 26 июня 2025 г. в 17:14 UTCresolved

   This incident has been resolved.

1. 8 апреля 2025 г. в 08:14 UTCinvestigating

   New device activations (go-live) currently has a problem, we are recovering the services.

2. 8 апреля 2025 г. в 08:33 UTCmonitoring

   We have identified the root case and deployed a work-around. We are monitoring the situation.

3. 8 апреля 2025 г. в 10:22 UTCresolved

   This incident has been resolved.

1. 19 марта 2025 г. в 13:14 UTCidentified

   We are experiencing delays during the Go Live on DataPortal and REST API. We still have a record of all the requests and we will make sure that all of them are addressed. But due to a problem with one of our partners we are experiencing delays.

2. 20 марта 2025 г. в 06:55 UTCmonitoring

   A work-around has been implemented, we are monitoring the go live requests.

3. 20 марта 2025 г. в 15:39 UTCresolved

   The work-around is active. Go Live requests are being handled normally again. Previously incomplete requests will be completed manually by the Proemion team.

1. 19 марта 2025 г. в 13:13 UTCresolved

   We are experiencing delays during the Go Live on DataPortal and REST API. We still have a record of all the requests and we will make sure that all of them are addressed. But due to a problem with one of our partners we are experiencing delays.

1. 19 февраля 2025 г. в 13:11 UTCinvestigating

   We have noticed a problem with one of our SIM providers. We are monitoring the new telematic unit activation requests from our customers and are working with the SIM provider to activate them as soon as possible. Already activated telematics units are fully operational.

2. 19 февраля 2025 г. в 13:23 UTCidentified

   The SIM provider has identified the problem and is working on fixing it.

3. 20 февраля 2025 г. в 04:58 UTCidentified

   The third-party acknowledged the issue and suggested a workaround which we are considering.

4. 21 февраля 2025 г. в 07:11 UTCmonitoring

   The work-around has been active since yesterday night, we are monitoring the SIM card activations.

5. 21 февраля 2025 г. в 09:00 UTCresolved

   This incident has been resolved.

1. 31 января 2025 г. в 08:38 UTCidentified

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

2. 31 января 2025 г. в 10:10 UTCmonitoring

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

3. 31 января 2025 г. в 12:26 UTCresolved

   This incident has been resolved.

1. 14 ноября 2024 г. в 14:22 UTCinvestigating

   We're experiencing an elevated level of API errors and are currently looking into the issue.

2. 14 ноября 2024 г. в 14:24 UTCinvestigating

   We are continuing to investigate this issue.

3. 14 ноября 2024 г. в 14:41 UTCmonitoring

   We have restored service, it's fully operational. We are monitoring for any more adverse impact.

4. 14 ноября 2024 г. в 15:11 UTCresolved

   The incident has been resolved, we have identified the root cause.

1. 30 июля 2024 г. в 08:01 UTCidentified

   At 00:41 CEST Digicert notified us of the following incident: https://www.digicert.com/support/certificate-revocation-incident We promptly verified that we were affected and are taking the necessary steps as instructed by Digicert to reissue and deploy new certificates. Based on previous experience with certificate renewals and rollouts we are confident that we can deploy new certificates before the revocation goes into effect. We expect no interruptions to services. We will post regular updates on this incident during the day.

2. 30 июля 2024 г. в 09:15 UTCmonitoring

   Certificates have been renewed and are being deployed and we continue to monitor all systems for any issues.

3. 30 июля 2024 г. в 11:11 UTCresolved

   This incident has been resolved.

1. 6 мая 2024 г. в 10:50 UTCinvestigating

   We are currently investigating this issue.

2. 6 мая 2024 г. в 10:50 UTCidentified

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

3. 6 мая 2024 г. в 10:58 UTCmonitoring

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

4. 6 мая 2024 г. в 13:57 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 7 мая 2024 г. в 07:27 UTCresolved

   This incident has been resolved.

1. 11 октября 2023 г. в 10:23 UTCidentified

   Due to a power outage the new TCU activation functionality is currently not working. We have identified the root cause and are actively working to restore service.

2. 11 октября 2023 г. в 10:31 UTCidentified

   We found that the power outage also affects the availability of our real-time connectivity solution. We are continuing our work to restore service.

3. 11 октября 2023 г. в 11:00 UTCmonitoring

   All services should now be operational. We are closely monitoring them.

4. 11 октября 2023 г. в 13:19 UTCresolved

   This incident has been resolved.

1. 21 февраля 2023 г. в 07:21 UTCinvestigating

   We are experiencing a full system outage of the DataPlatform after our deployment today. Our engineers are working on a solution. We will update this notification as soon as we have more information.

2. 21 февраля 2023 г. в 07:22 UTCinvestigating

   We are continuing to investigate this issue.

3. 21 февраля 2023 г. в 07:33 UTCmonitoring

   DataPlatform is back online. We are monitoring the situation.

4. 21 февраля 2023 г. в 09:44 UTCresolved

   The metrics are stable and back at normal levels. The incident is resolved.

1. 20 июля 2022 г. в 07:48 UTCinvestigating

   We are suffering packet loss in our connectivity in one of our data centers which might affect or slow down realtime connections. Data import from third party systems may be delayed, too. We are working on it and give feedback as soon as possible.

2. 20 июля 2022 г. в 09:34 UTCidentified

   One of our internet provider is currently affected by a large-scale disturbance. We continue to work together with them to resolve the issue and to minimize the impact.

3. 20 июля 2022 г. в 11:31 UTCidentified

   Issue is still ongoing. We continue to work with our internet providers to resolve the issue while monitoring the health of our services.

4. 20 июля 2022 г. в 20:33 UTCmonitoring

   We are no longer suffering packet loss when accessing our services. We are still monitoring the situation and will continue to work to minimize any issues that may surface.

5. 21 июля 2022 г. в 10:51 UTCresolved

   There have been no issues since yesterday afternoon. We also have confirmation from our internet providers that they are no longer experiencing any issues. In total we experienced a bit under 12 hours of degraded performance which may have caused slowness accessing our Data Portal and the RealTime Dashboard. No data was lost at any time during the incident.

1. 5 марта 2021 г. в 11:47 UTCinvestigating

   We are experiencing our Standard Portal is not accessible. Our engineers are investigating the issue.

2. 5 марта 2021 г. в 11:49 UTCmonitoring

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

3. 5 марта 2021 г. в 11:49 UTCmonitoring

   Our engineers implemented a fix. We are constantly monitoring availability.

4. 5 марта 2021 г. в 13:24 UTCresolved

   This incident has been resolved.