Ιστορικό διακοπών του Proemion

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.

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.

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

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

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

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.

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.

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

This incident has been resolved.

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

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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.

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

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

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.

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.

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

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

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

This incident has been resolved.

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

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

This incident has been resolved.

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

We are continuing to investigate this issue.

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

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

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.

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

This incident has been resolved.

We are currently investigating this issue.

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

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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.

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

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

This incident has been resolved.

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.

We are continuing to investigate this issue.

DataPlatform is back online. We are monitoring the situation.

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

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.

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.

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

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.

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.

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

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

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

This incident has been resolved.

We are currently investigating this issue.

We have fixed the problem and are now monitoring our backlogs.

Backlogs have cleared, all functionality is now restored.

We're experiencing an elevated level of API errors and are currently looking into the issue. As a consequence of the REST API errors, users might experience issues loading https://dataportal.proemion.com.

The issue has been identified and a fix deployed half an hour ago. We apologize for the lack of updates since opening the incident and we will try to do better next time.

We have detected an issue in our backend systems that is impacting device activation process and contract overview. We are working to resolve it.

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

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

This incident has been resolved.

We had a physical server failure, which impacted our data ingestion and realtime feature. We don't expect data loss, we are investigating.

Backlog is processed, the realtime feature is operational.

This incident has been resolved.