Is Evalink down?

Product match: components.

Read the provider’s incident report

1. 2026-05-20T14:01:20.668+02:00 · resolved

   No further anomalies have been observed in the evalink API Gateway. The situation is therefore considered resolved.

2. 2026-05-20T12:56:07.803+02:00 · monitoring

   The previously observed API request issues have been resolved. Based on our investigation, the issue was likely related to the scheduled maintenance performed earlier. We are continuing to monitor the situation to ensure ongoing stability.

3. 2026-05-20T12:42:34.116+02:00 · investigating

   We are currently observing some API requests that are not completing successfully and are investigating further. Alarm transmission is not affected.

Product match: components.

Read the provider’s incident report

1. 2026-05-11T15:51:14.203+02:00 · resolved

   This incident has been resolved.

2. 2026-05-11T15:32:32.067+02:00 · identified

   There was a high load of UI requests failing from 15:08 to 15:13 - after manual intervention after our internal alerts triggered the system recovered quickly and seems to be stable - we're investigating what caused the component to start failing in this timeframe and have it deactivated for the time being.

3. 2026-05-11T15:19:39.373+02:00 · investigating

   We're currently investigating an elevated amount of failing requests in our EU region

Product match: components.

Read the provider’s incident report

1. 2026-05-06T00:45:18.131+02:00 · resolved

   This incident has been resolved.

2. 2026-05-05T23:51:52.697+02:00 · monitoring

   We're seeing infrastructure issues on some Farwest hosts and and working with them to get the service fully back up and running with full redundancy. Its currently affecting one of the two receiver sites and alarm transmission of dual path devices is still functional.

Product match: components.

Read the provider’s incident report

1. 2026-04-27T16:43:14.539+02:00 · resolved

   This incident has been resolved - all past and realtime data is now correctly reflected in evalink analytics again.

2. 2026-04-27T16:15:24.349+02:00 · monitoring

   We've successfully repaired the data pipeline so that realtime replication is working nominal again - so the tables are all up-to-date with the latest data. We'll initiate a reload of the now missing data and give another update if the data is entirely correct again.

3. 2026-04-27T12:08:08.100+02:00 · identified

   We're aware of alarm + eventlog + workflow data currently being delayed in analytics and are working to repair the data and continue replication.

Product match: components.

Read the provider’s incident report

1. 2026-04-22T22:08:05.724+02:00 · resolved

   This incident has been resolved.

2. 2026-04-22T21:02:08.000+02:00 · monitoring

   The issue was caused by a DNS problem at the underlying platform provider, emergency login via https://talos.evalink.io/en/login2, remains possible. From what we can see the DNS started recovering around 10mins ago, and seems fully operation again by now. Only certain regions seemed to be affected. We're monitoring the situation to confirm that the system stays healthy.

3. 2026-04-22T20:53:37.889+02:00 · identified

   We're aware of login issues at our auth provider: Use the emergency login at https://talos.evalink.io/en/login2 to login via email code.

Product match: components.

Read the provider’s incident report

1. 2026-04-08T00:00:00.250+02:00 · resolved

   This incident has been resolved.

2. 2026-04-07T23:56:02.323+02:00 · identified

   We're seeing infrastructure issues on some Farwest hosts and and working with them to get the service fully back up and running with full redundancy. Its currently affecting one of the two receiver sites and alarm transmission of dual path devices is still functional.

Product match: components.

Read the provider’s incident report

1. 2026-04-06T18:27:34.959+02:00 · resolved

   The degraded performance affecting evalink talos in the EU region has been resolved. Our team has confirmed that service performance is operating normally, and this incident is now closed.

2. 2026-04-06T17:36:26.072+02:00 · monitoring

   We have identified the cause of the degraded performance affecting the device-service in Europe and have implemented mitigation measures. Platform performance has stabilized, and our team is continuing to monitor the service closely. Alarm transmission is not affected. We will provide a further update if necessary.

3. 2026-04-06T17:25:29.902+02:00 · investigating

   We are currently investigating platform performance issues affecting services in Europe. Our team is actively working to identify the cause and restore normal performance. Alarm transmission is not affected. We will provide another update as soon as more information is available.

Product match: components.

Read the provider’s incident report

1. 2026-03-31T18:23:57.669+02:00 · resolved

   This incident has been resolved.

2. 2026-03-31T17:44:07.571+02:00 · identified

   The issue has been tracked down to a network component on the underlying infrastructure and is being worked on. Dual path alarm systems should stay connected via at least 1 path.

3. 2026-03-31T17:38:10.887+02:00 · investigating

   We're seeing infrastructure issues on some Farwest hosts and and working with them to get the service fully back up and running with full redundancy. From what we can tell its currently affecting one of the two receiver sites.

Provider reports service problems. The official provider feed identifies an active incident or affected component. This page was assembled at 2026-10-22T00:13:14.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-21T00:10:00.000Z to 2026-10-22T00:10:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Evalink feature.

The latest status observation was 2026-10-22T00:01:02.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Evalink in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.