Get email notifications whenever agrirouter system creates, updates or resolves an incident.
Visit our support site.
All Systems Operational
Uptime over the past 90 days. View historical uptime.
agrirouter
?
Operational
90 days ago
95.38
% uptime
Today
agrirouter IO Tool
?
Operational
agrirouter Marketplace
?
Operational
agrirouter Quality Assurance Environment
?
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Jan 31, 2023
No incidents reported today.
Jan 30, 2023
No incidents reported.
Jan 29, 2023
Resolved -
This incident has been resolved.
Jan 29, 02:30 CET
Jan 29, 02:30 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 23:53 CET
Jan 28, 23:53 CET
Resolved -
This incident has been resolved.
Jan 29, 02:18 CET
Jan 29, 02:18 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 29, 00:13 CET
Jan 29, 00:13 CET
Jan 28, 2023
Resolved -
This incident has been resolved.
Jan 28, 23:04 CET
Jan 28, 23:04 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 22:58 CET
Jan 28, 22:58 CET
Resolved -
This incident has been resolved.
Jan 28, 22:16 CET
Jan 28, 22:16 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 21:43 CET
Jan 28, 21:43 CET
Resolved -
This incident has been resolved.
Jan 28, 22:03 CET
Jan 28, 22:03 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 21:53 CET
Jan 28, 21:53 CET
Resolved -
NOTE! This was not a real outage, SAP monitoring systems failed!
Jan 28, 11:33 CET
Jan 28, 11:33 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 10:33 CET
Jan 28, 10:33 CET
Resolved -
NOTE! This was not a real outage, SAP monitoring systems failed!
Jan 28, 11:33 CET
Jan 28, 11:33 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 28, 10:33 CET
Jan 28, 10:33 CET
Jan 27, 2023
Resolved -
This incident has been resolved.
Jan 27, 04:43 CET
Jan 27, 04:43 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 27, 04:33 CET
Jan 27, 04:33 CET
Jan 26, 2023
No incidents reported.
Jan 25, 2023
No incidents reported.
Jan 24, 2023
No incidents reported.
Jan 23, 2023
No incidents reported.
Jan 22, 2023
No incidents reported.
Jan 21, 2023
No incidents reported.
Jan 20, 2023
Completed -
The scheduled maintenance has been completed.
Jan 20, 11:48 CET
Jan 20, 11:48 CET
Scheduled -
The IO-Tool will be updated with a complete rewrite of its backend. During maintenance, the IO-Tool will be unavailable, any running simulations will be stopped.
We have reworked certain aspects of the way things work internally, mostly notable through redesigned log messages and some minor quality-of-life improvements.
The general function scope of the IO Tool is unchanged.
Additionally, we have implemented the following backlog items:
- IO-2 change data type of uploaded files for debugging purposes
- IO-44 update endpoint list automatically after certain events
- IO-51 disallow simulation for files that contain the same device multiple times
- IO-37 simulations that are running without being logged on now display their status after relogin/reload of the page
Jan 19, 10:04 CET
We have reworked certain aspects of the way things work internally, mostly notable through redesigned log messages and some minor quality-of-life improvements.
The general function scope of the IO Tool is unchanged.
Additionally, we have implemented the following backlog items:
- IO-2 change data type of uploaded files for debugging purposes
- IO-44 update endpoint list automatically after certain events
- IO-51 disallow simulation for files that contain the same device multiple times
- IO-37 simulations that are running without being logged on now display their status after relogin/reload of the page
Jan 19, 10:04 CET
Resolved -
This notification was caused by a monitoring issue. The system was NOT affected.
Jan 20, 07:42 CET
Jan 20, 07:42 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 20, 07:38 CET
Jan 20, 07:38 CET
Resolved -
This notification was caused by a monitoring issue. The system was NOT affected.
Jan 20, 07:42 CET
Jan 20, 07:42 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 20, 06:18 CET
Jan 20, 06:18 CET
Jan 19, 2023
No incidents reported.
Jan 18, 2023
Resolved -
This incident has been resolved.
Jan 18, 21:38 CET
Jan 18, 21:38 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 18, 21:28 CET
Jan 18, 21:28 CET
Resolved -
This incident has been resolved.
Jan 18, 16:43 CET
Jan 18, 16:43 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 18, 16:38 CET
Jan 18, 16:38 CET
Resolved -
This incident has been resolved.
Jan 18, 16:30 CET
Jan 18, 16:30 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 18, 16:26 CET
Jan 18, 16:26 CET
Resolved -
This incident has been resolved.
Jan 18, 16:23 CET
Jan 18, 16:23 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 18, 16:18 CET
Jan 18, 16:18 CET
Jan 17, 2023
Resolved -
This incident has been resolved.
Jan 17, 11:23 CET
Jan 17, 11:23 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 17, 11:13 CET
Jan 17, 11:13 CET
Resolved -
This incident has been resolved.
Jan 17, 11:23 CET
Jan 17, 11:23 CET
Identified -
The issue has been identified and a fix is being implemented.
Jan 17, 11:13 CET
Jan 17, 11:13 CET
Completed -
The scheduled maintenance has been completed.
Jan 17, 05:32 CET
Jan 17, 05:32 CET
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 05:00 CET
Jan 17, 05:00 CET
Scheduled -
Component:
IoT service – MQTT performance improvement and vulnerability fixes - Production (Prod) Environment
Period:
• 17th Dec 2022 – from 05:00 to 05:30 UTC.
Trigger:
IoTs platform release version 4.81
Impact:
This may cause some downtime / service disruption between the mentioned period. All types of message processing will be impacted.
Jan 5, 15:07 CET
IoT service – MQTT performance improvement and vulnerability fixes - Production (Prod) Environment
Period:
• 17th Dec 2022 – from 05:00 to 05:30 UTC.
Trigger:
IoTs platform release version 4.81
Impact:
This may cause some downtime / service disruption between the mentioned period. All types of message processing will be impacted.
Jan 5, 15:07 CET